Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office. is anyone else experiencing an issue with level3 in LA? ATT MIS in los angeles: 4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms 2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms Zayo Fiber in Los Angeles 4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms 2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 ms
Colo'd at One Wilshire, dual homed Tinet and Hurricane. No issues. --- 4.2.2.2 ping statistics --- 77 packets transmitted, 77 received, 0% packet loss, time 76107ms rtt min/avg/max/mdev = 14.332/14.416/14.604/0.169 ms 2 laxcor1-pc1.o1.com (69.85.165.41) 0.182 ms 0.192 ms 0.188 ms 3 xe-2-3-1.lax21.ip4.tinet.net (199.229.229.113) 15.926 ms 15.933 ms 15.947 ms 4 89.149.182.194 (89.149.182.194) 14.294 ms 141.136.106.1 (141.136.106.1) 14.324 ms 89.149.182.194 (89.149.182.194) 14.291 ms 5 xe-11-3-0.edge1.LosAngeles6.level3.net (4.68.62.1) 12.779 ms 12.790 ms 12.785 ms 6 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 14.334 ms ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 22.335 ms * 7 b.resolvers.Level3.net (4.2.2.2) 31.537 ms 14.424 ms 32.485 ms -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of jd Sent: Tuesday, March 11, 2014 8:58 AM To: outages@outages.org Subject: [outages] level3 LA Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office. is anyone else experiencing an issue with level3 in LA? ATT MIS in los angeles: 4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms 2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms Zayo Fiber in Los Angeles 4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms 2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 ms _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Replied directly instead of to the list... Seems fine from Phoenix. *Cognet - PHX to Level 3 - LAX:* akosednar@web:~$ mtr --report 4.2.2.2 Start: Tue Mar 11 09:14:44 2014 HOST: web Loss% Snt Last Avg Best Wrst StDev 1.|-- PRIVATE 0.0% 10 0.3 0.3 0.3 0.5 0.0 2.|-- gi1-3.ccr01.phx05.atlas.c 10.0% 10 0.7 8.4 0.7 36.7 12.7 3.|-- 154.54.89.109 0.0% 10 2.3 3.1 2.3 6.5 1.1 4.|-- be2330.ccr21.lax01.atlas. 0.0% 10 14.1 14.2 14.0 14.8 0.0 5.|-- be2019.ccr21.lax04.atlas. 0.0% 10 13.9 14.1 13.6 15.1 0.3 6.|-- level3.lax04.atlas.cogent 0.0% 10 13.6 16.0 13.2 34.6 6.6 7.|-- ae-4-90.edge3.LosAngeles1 0.0% 10 14.0 14.4 13.9 16.4 0.7 8.|-- b.resolvers.Level3.net <http://b.resolvers.level3.net/> 0.0% 10 13.6 13.8 13.3 14.8 0.0 *Cognet - PHX to ATT:* akosednar@web:~$ mtr --report 12.122.104.14 Start: Tue Mar 11 09:15:31 2014 HOST: web Loss% Snt Last Avg Best Wrst StDev 1.|-- PRIVATE 0.0% 10 0.4 0.4 0.3 0.7 0.0 2.|-- gi1-3.ccr01.phx05.atlas.c 0.0% 10 0.7 0.7 0.7 0.8 0.0 3.|-- 154.54.89.109 0.0% 10 2.4 2.5 2.3 2.7 0.0 4.|-- be2330.ccr21.lax01.atlas. 0.0% 10 18.7 14.9 14.0 18.7 1.8 5.|-- be2160.ccr21.sjc01.atlas. 0.0% 10 26.4 26.7 26.0 28.3 0.7 6.|-- be2000.ccr21.sjc03.atlas. 0.0% 10 26.6 26.4 26.1 26.8 0.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 On Tue, Mar 11, 2014 at 9:30 AM, Blaine Reeve <breeve@o1.com> wrote:
Colo'd at One Wilshire, dual homed Tinet and Hurricane. No issues.
--- 4.2.2.2 ping statistics --- 77 packets transmitted, 77 received, 0% packet loss, time 76107ms rtt min/avg/max/mdev = 14.332/14.416/14.604/0.169 ms
2 laxcor1-pc1.o1.com (69.85.165.41) 0.182 ms 0.192 ms 0.188 ms 3 xe-2-3-1.lax21.ip4.tinet.net (199.229.229.113) 15.926 ms 15.933 ms 15.947 ms 4 89.149.182.194 (89.149.182.194) 14.294 ms 141.136.106.1 (141.136.106.1) 14.324 ms 89.149.182.194 (89.149.182.194) 14.291 ms 5 xe-11-3-0.edge1.LosAngeles6.level3.net (4.68.62.1) 12.779 ms 12.790 ms 12.785 ms 6 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 14.334 ms ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 22.335 ms * 7 b.resolvers.Level3.net (4.2.2.2) 31.537 ms 14.424 ms 32.485 ms
-----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of jd Sent: Tuesday, March 11, 2014 8:58 AM To: outages@outages.org Subject: [outages] level3 LA
Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office.
is anyone else experiencing an issue with level3 in LA?
ATT MIS in los angeles:
4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms
2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms
Zayo Fiber in Los Angeles
4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms
2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 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
Peer with Level3 @ 1 Wilshire no issues. Router#traceroute 4.2.2.2 Type escape sequence to abort. Tracing the route to b.resolvers.Level3.net (4.2.2.2) 1 xxxxxxx.car2.LosAngeles1.Level3.net (x.x.x.x) 0 msec 0 msec 4 msec 2 ae-27-27.edge6.LosAngeles1.Level3.net (4.69.201.17) [AS 3356] 0 msec 0 msec 0 msec 3 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) [AS 3356] 0 msec ae-1-60.edge3.LosAngeles1.Level3.net (4.69.144.9) [AS 3356] 0 msec ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) [AS 3356] 0 msec 4 b.resolvers.Level3.net (4.2.2.2) [AS 3356] 20 msec * 0 msec Router#ping Protocol [ip]: Target IP address: 4.2.2.2 Success rate is 100 percent (1000/1000), round-trip min/avg/max = 1/1/4 ms -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Blaine Reeve Sent: Tuesday, March 11, 2014 11:30 AM To: jd; outages@outages.org Subject: Re: [outages] level3 LA Colo'd at One Wilshire, dual homed Tinet and Hurricane. No issues. --- 4.2.2.2 ping statistics --- 77 packets transmitted, 77 received, 0% packet loss, time 76107ms rtt min/avg/max/mdev = 14.332/14.416/14.604/0.169 ms 2 laxcor1-pc1.o1.com (69.85.165.41) 0.182 ms 0.192 ms 0.188 ms 3 xe-2-3-1.lax21.ip4.tinet.net (199.229.229.113) 15.926 ms 15.933 ms 15.947 ms 4 89.149.182.194 (89.149.182.194) 14.294 ms 141.136.106.1 (141.136.106.1) 14.324 ms 89.149.182.194 (89.149.182.194) 14.291 ms 5 xe-11-3-0.edge1.LosAngeles6.level3.net (4.68.62.1) 12.779 ms 12.790 ms 12.785 ms 6 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 14.334 ms ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 22.335 ms * 7 b.resolvers.Level3.net (4.2.2.2) 31.537 ms 14.424 ms 32.485 ms -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of jd Sent: Tuesday, March 11, 2014 8:58 AM To: outages@outages.org Subject: [outages] level3 LA Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office. is anyone else experiencing an issue with level3 in LA? ATT MIS in los angeles: 4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms 2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms Zayo Fiber in Los Angeles 4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms 2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 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 ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.
Does L3's LG come in handy for reproducing the issue? It might not given how packets flow (e.g. the loss is across a specific interface), but you might spend 15 minutes or so poking at it: http://lookingglass.level3.net/ -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Tue, Mar 11, 2014 at 08:57:44AM -0700, jd wrote:
Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office.
is anyone else experiencing an issue with level3 in LA?
ATT MIS in los angeles:
4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms
2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms
Zayo Fiber in Los Angeles
4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms
2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 ms _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I had done this earlier, forgot to paste it, current results from Tustin, CA to 4.2.2.2 I also have presence in One Wilshire and 800 S Hope, I don't think we see the level3 issue there. I think the route has to do with Tustin > LA, every trace that has replied to this thread has been through an alternate route. Thanks. ---- statistics ---- 50 packets transmitted, 43 packets received, 14% packet loss rtt min/avg/median/max/mdev/stddev = 16/18.698/20/28/1.503/2.69 ms 50 packets transmitted, 44 packets received, 12% packet loss rtt min/avg/median/max/mdev/stddev = 16/20.727/20/44/1.933/6.283 ms On 3/11/2014 9:41 AM, Jeremy Chadwick wrote:
Does L3's LG come in handy for reproducing the issue? It might not given how packets flow (e.g. the loss is across a specific interface), but you might spend 15 minutes or so poking at it:
Your 1st traceroute shows loss happening within the Los Angeles region possibly within Level3 (hop #8 from the look of it, and it looks like multipathing is involved). Because traceroutes going only one direction are provided (due to the destination you chose and the nature of asymmetric routing), only half of the picture is shown, which is why I say "possibly". Your 2nd traceroute shows two things; - Loss showing up starting at hop #3 (possibly within Zayo/Abovenet space, again "possibly", re: asymmetric routing) - Loss showing up at hop #8 (could be an effect of something happening earlier in the path) For reference, here are your traceroutes: https://puck.nether.net/pipermail/outages/2014-March/006787.html So when you say "I think it's a problem with Tustin > LA", the 2nd traceroute you provided doesn't seem to support that theory, nor the statement "I am unable to reproduce it to any other network". Do you have any other tools available to you, like mtr? mtr won't narrow down where the issue is happening, but would make it more clear as to where the issue is happening, especially if you let it run for a while (say 10 minutes or so) from both places (you didn't provide source IPs for either traceroute, so that doesn't help either). -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Tue, Mar 11, 2014 at 10:00:59AM -0700, jd wrote:
I had done this earlier, forgot to paste it, current results from Tustin, CA to 4.2.2.2
I also have presence in One Wilshire and 800 S Hope, I don't think we see the level3 issue there.
I think the route has to do with Tustin > LA, every trace that has replied to this thread has been through an alternate route.
Thanks.
---- statistics ---- 50 packets transmitted, 43 packets received, 14% packet loss rtt min/avg/median/max/mdev/stddev = 16/18.698/20/28/1.503/2.69 ms
50 packets transmitted, 44 packets received, 12% packet loss rtt min/avg/median/max/mdev/stddev = 16/20.727/20/44/1.933/6.283 ms
On 3/11/2014 9:41 AM, Jeremy Chadwick wrote:
Does L3's LG come in handy for reproducing the issue? It might not given how packets flow (e.g. the loss is across a specific interface), but you might spend 15 minutes or so poking at it:
Nothing on L3 outage board On Tuesday, March 11, 2014, Jeremy Chadwick <jdc@koitsu.org> wrote:
Does L3's LG come in handy for reproducing the issue? It might not given how packets flow (e.g. the loss is across a specific interface), but you might spend 15 minutes or so poking at it:
http://lookingglass.level3.net/
-- | Jeremy Chadwick jdc@koitsu.org<javascript:;>| | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Tue, Mar 11, 2014 at 08:57:44AM -0700, jd wrote:
Got a complaint about slowness from my ATT MIS client's, I just looked around and noticed that this encountering packet loss and I am unable to reproduce it to any other network. Also tested from a Zayo fiber connection at another office.
is anyone else experiencing an issue with level3 in LA?
ATT MIS in los angeles:
4.2.2.2 159 packets transmitted, 119 received, 25% packet loss, time 158165ms
2 cr1.la2ca.ip.att.net (12.122.104.14) 9.932 ms 9.943 ms 9.930 ms 3 ggr2.la2ca.ip.att.net (12.122.128.101) 10.381 ms 10.370 ms 10.358 ms 4 192.205.37.146 (192.205.37.146) 10.836 ms 10.826 ms 10.815 ms 5 vl-3507-ve-121.ebr1.tustin1.level3.net (4.69.158.105) 11.793 ms 11.788 ms vl-3505-ve-119.ebr1.tustin1.level3.net (4.69.158.97) 13.748 ms 6 ae-6-6.ebr1.losangeles1.level3.net (4.69.153.221) 13.728 ms 13.741 ms 13.464 ms 7 ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 14.702 ms ae-71-71.csw2.losangeles1.level3.net (4.69.137.6) 12.919 ms ae-81-81.csw3.losangeles1.level3.net (4.69.137.10) 13.900 ms 8 ae-2-70.edge3.losangeles1.level3.net (4.69.144.73) 9.616 ms * ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 12.333 ms 9 b.resolvers.level3.net (4.2.2.2) 33.554 ms 26.671 ms 33.394 ms
Zayo Fiber in Los Angeles
4.2.2.2 50 packets transmitted, 36 received, 28% packet loss, time 49057ms
2 ae7.cr1.lax112.us.above.net (64.125.32.193) 2.762 ms 2.754 ms 2.744 ms 3 ae8.mpr1.lax12.us.above.net (64.125.31.189) 2.735 ms 80.914 ms * 4 ae7.edge2.LosAngles.Level3.net (4.68.70.33) 2.625 ms 80.835 ms 2.615 ms 5 ae-2-70.edge3.LosAngeles1.Level3.net (4.69.144.73) 2.708 ms * ae-4-90.edge3.LosAngeles1.Level3.net (4.69.144.201) 6.249 ms 6 b.resolvers.Level3.net (4.2.2.2) 2.904 ms 2.750 ms 2.721 ms _______________________________________________ Outages mailing list Outages@outages.org <javascript:;> https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org <javascript:;> https://puck.nether.net/mailman/listinfo/outages
-- ..................................... *Luke Rockwell* Systems and Support Analyst Information Technology ..................................... Cal Alumni Association | UC Berkeley 1 Alumni House, Berkeley, CA 94720 *T* 510.900.8196 *F* 510.642.6252 ..................................... *Commitment, Support, Passion* _____________________________________ *alumni.berkeley.edu <http://alumni.berkeley.edu/>* _____________________________________ *Facebook <https://www.facebook.com/CalAlumni> | LinkedIn <http://www.linkedin.com/groups?gid=70245>*
participants (6)
-
Anthony Kosednar -
Blaine Reeve -
Erik Sundberg -
jd -
Jeremy Chadwick -
Luke Rockwell