90% packet loss @ los angeles ibone connection

here is the other 1/2 of the route.  consistant packet loss the entire way, but no clear problems like a 90% loss.

 2. 24.5.40.1                                             2.4%  5359   13.8 100.2   5.2 8544. 452.3

 3. te-5-5-ur01.sf19th.ca.sfba.comcast.net                2.7%  5359   17.3  99.1   4.4 8489. 443.4

 4. te-1-14-0-1-ar01.sfsutro.ca.sfba.comcast.net          2.4%  5359   14.0 100.7   4.9 8450. 445.7

 5. te-0-2-0-0-cr01.chicago.il.ibone.comcast.net          2.9%  5359   19.3 101.6   8.6 8397. 444.2

 6. pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net       2.6%  5359   23.6 101.1   7.6 8344. 435.9

 7. te0-7-0-0.ccr21.sjc04.atlas.cogentco.com              2.4%  5359   12.9 121.1   7.3 12307 576.6

 8. be2015.ccr21.sfo01.atlas.cogentco.com                 3.0%  5359   12.8 121.5   8.0 12253 564.0

 9. be2132.ccr21.mci01.atlas.cogentco.com                 2.6%  5359   59.6 162.9  53.0 12417 562.4

10. be2156.ccr41.ord01.atlas.cogentco.com                 2.8%  5359   64.1 167.8  56.7 12364 562.0

11. be2079.ccr21.yyz02.atlas.cogentco.com                 2.7%  5359  101.1 193.1  80.3 13025 570.1

12. be2090.ccr21.ymq02.atlas.cogentco.com                 2.6%  5359  100.4 198.7  82.6 12971 594.5

13. be2384.ccr21.lpl01.atlas.cogentco.com                 2.6%  5359  160.1 264.0 152.9 12917 568.9

14. be2182.ccr41.ams03.atlas.cogentco.com                 2.6%  5359  164.1 270.7 159.0 12863 568.5

15. be2434.mag21.ams03.atlas.cogentco.com                 2.5%  5359  162.5 275.1 159.0 12810 572.6

16. te0-0-0-1.nr12.b021908-0.ams03.atlas.cogentco.com     2.4%  5359  173.7 272.6 161.1 12755 565.3

17. 149.11.64.214                                         3.4%  5359  170.8 277.7 161.1 12701 577.2

    149.11.64.210

What's the inbound route look like? You should also contact your provider and see if they can pressure the outbound path a bit. It's not too likely, since in my experience Comcast like to dominate the inbound/outbound route for business class customers, but it's worth a try. I'd also call Comcast and ask that they send a request to level 2 about this, but you'll need to find a way to get your information listed in the request with them. Once you get it listed in the request, write down your ticket number and wait a few days. If you don't hear back call back and ask that you speak to the tier agent for your ticket number. 

Omigitsu,

Traceroute results are always interesting.  Traceroute uses tailored pings with increasing hop count for each query. Intermidiate responses come from routers along the path where the hop count expires. The last response comes from the target system. The significant conclusions from the results you posted include:

The .losangeles.ca.ibone.comcast.net data most likely indicates that the router queried was too busy forwarding data packets to handle ICMP Echo requests. 

Since there is stable and consitent performance to c-24-5-42-80.hsd1.ca.comcast.net, there is no reason to consider ping packet loss on an intermediate node as unacceptable or even significant of anything.