Re: [outages] Level3 LAX latency - backhoe fever?
nothing on my l3 status board that I have access to . *Luke Rockwell* Systems Administrator Information Technology . On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] Level3 LAX latency - backhoe fever?
Seeing about the same latency out of the Chicago suburbs. From: Luke Rockwell via Outages outages@outages.org To: Andrew Losey and...@addthis.com Cc: outages outages@outages.org Sent: Monday, November 17, 2014 2:26:38 PM Subject: Re: [outages] Level3 LAX latency - backhoe fever? nothing on my l3 status board that I have access to . Luke Rockwell Systems Administrator Information Technology . On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Re: [outages] Level3 LAX latency - backhoe fever?
just had a chance to catch up on this email, i had a ticket open between LAX and VA, that had problems. their response was and i quote Called customer and spoke with *. I let him know that our Core engineers found that there was a backbone transport issue between DC and LAX that was causing traffic to shift onto a backup path which got saturated as we started hitting peak usage times. That trouble has now cleared and the main backbone link is now up. We will hold this ticket for 24 hours. If you have any further trouble, let us know and we will look back into the issue. hope that helps others :) On Mon, Nov 17, 2014 at 12:22 PM, Andrew Losey via Outages outages@outages.org wrote: Howdy, Seeing some heavy latency once I hit Level3’s LAX edge - anyone else experiencing latency out in LA? traceroute to xxx.x.com (xx.xx.xx.xx), 30 hops max, 60 byte packets 1 xxx.xxx.local.xx.xx.in-addr.arpa (xx.xx.xx.xx) 0.395 ms 0.379 ms 0.324 ms 2 xe-8-2-2.edge2.Washington4.Level3.net (4.53.114.221) 0.652 ms 0.694 ms 0.691 ms 3 * * * 4 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 107.206 ms ae-3-80.edge3.LosAngeles1.Level3.net (4.69.144.137) 108.328 ms 109.351 ms 5 .edge3.LosAngeles1.Level3.net (xx.xx.xx.xx) 94.529 ms 94.589 ms 91.664 ms 6 ..com (xx.xx.xx.xx) 66.823 ms 77.933 ms 76.571 ms ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
