Re: [outages] Packet loss - Washington Level 3 - 4.2.2.2
We hit Atlanta, And last week I saw both 4.2.2.1 and 4.2.2.2 show about 45% loss from both our network (AS36295) and my home cable connection (AS33363). Lasted till about friday. I figured they ratelimited ICMP because DNS resolution didn't seem to suffer at all. It seems to have cleared up however. Nick Olsen Network Operations (855) FLSPEED x106 ---------------------------------------- From: "Josh Luthman" <josh@imaginenetworksllc.com> Sent: Monday, November 05, 2012 11:43 AM To: "outages@outages.org" <outages@outages.org> Subject: [outages] Packet loss - Washington Level 3 - 4.2.2.2 Anyone else seeing this? Been like this since ~noon November 1 for me. No one else has said anything so I'm curious if it's something I did to upset them. 4. be22.clevohek-ccr01.mwrtn.rr.com 0.0% 273 16.2 13.1 6.1 21.6 2.5 5. ae10-0.cr0.dca20.tbone.rr.com 0.0% 273 24.6 20.8 16.9 29.2 2.3 6. ae-1-0.pr0.dca20.tbone.rr.com 0.0% 273 56.0 24.4 14.9 108.2 14.9 7. xe-4-0-0.edge2.Washington1.Level 0.0% 273 21.7 22.7 16.9 69.3 5.6 8. vlan90.csw4.Washington1.Level3.n 0.0% 273 27.2 25.0 21.6 37.8 4.0 9. ae-91-91.ebr1.Washington1.Level3 0.0% 273 23.3 22.0 20.7 24.0 0.4 10. ae-8-8.ebr1.Washington12.Level3. 0.0% 273 32.2 24.6 11.9 36.9 3.5 11. ae-1-51.edge2.Washington12.Level 14.3% 273 22.3 22.6 18.9 39.7 2.1 12. b.resolvers.Level3.net 28.6% 273 22.3 33.8 22.0 1419. 107.9 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
It's been well-established for many years that yes, ICMP is rate-limited to some degree (both on the router preceding the host as well as the host itself) for 4.2.2.1 and/or 4.2.2.2. Whether or not all the servers/all the routers are configured identically is anyone's guess, and it's even more difficult to determine given use of anycast. Just a reminder for folks: please do not use 4.2.2.1 and 4.2.2.2 indefinitely. Their intention is to be used for temporary situations, i.e. setting up a workstation or server where you've forgotten to write down the DNS servers, thus allowing you to have something that gets you resolution so that you can get online to look up proper DNS servers. I only state this because of lines like this:
Been like this since ~noon November 1 for me.
I'm under the impression that Google's 8.8.8.8 is more intended for "long-term" use, but pleas do not quote me on that. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Mon, Nov 05, 2012 at 12:20:58PM -0500, Nick Olsen wrote:
We hit Atlanta, And last week I saw both 4.2.2.1 and 4.2.2.2 show about 45% loss from both our network (AS36295) and my home cable connection (AS33363). Lasted till about friday. I figured they ratelimited ICMP because DNS resolution didn't seem to suffer at all. It seems to have cleared up however.
Nick Olsen Network Operations (855) FLSPEED x106
---------------------------------------- From: "Josh Luthman" <josh@imaginenetworksllc.com> Sent: Monday, November 05, 2012 11:43 AM To: "outages@outages.org" <outages@outages.org> Subject: [outages] Packet loss - Washington Level 3 - 4.2.2.2
Anyone else seeing this? Been like this since ~noon November 1 for me. No one else has said anything so I'm curious if it's something I did to upset them. 4. be22.clevohek-ccr01.mwrtn.rr.com 0.0% 273 16.2 13.1 6.1 21.6 2.5 5. ae10-0.cr0.dca20.tbone.rr.com 0.0% 273 24.6 20.8 16.9 29.2 2.3 6. ae-1-0.pr0.dca20.tbone.rr.com 0.0% 273 56.0 24.4 14.9 108.2 14.9 7. xe-4-0-0.edge2.Washington1.Level 0.0% 273 21.7 22.7 16.9 69.3 5.6 8. vlan90.csw4.Washington1.Level3.n 0.0% 273 27.2 25.0 21.6 37.8 4.0 9. ae-91-91.ebr1.Washington1.Level3 0.0% 273 23.3 22.0 20.7 24.0 0.4 10. ae-8-8.ebr1.Washington12.Level3. 0.0% 273 32.2 24.6 11.9 36.9 3.5 11. ae-1-51.edge2.Washington12.Level 14.3% 273 22.3 22.6 18.9 39.7 2.1 12. b.resolvers.Level3.net 28.6% 273 22.3 33.8 22.0 1419. 107.9 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I'm using 4.2.2.2 strictly as an ICMP test on Smokeping. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Mon, Nov 5, 2012 at 12:46 PM, Jeremy Chadwick <jdc@koitsu.org> wrote:
It's been well-established for many years that yes, ICMP is rate-limited to some degree (both on the router preceding the host as well as the host itself) for 4.2.2.1 and/or 4.2.2.2. Whether or not all the servers/all the routers are configured identically is anyone's guess, and it's even more difficult to determine given use of anycast.
Just a reminder for folks: please do not use 4.2.2.1 and 4.2.2.2 indefinitely. Their intention is to be used for temporary situations, i.e. setting up a workstation or server where you've forgotten to write down the DNS servers, thus allowing you to have something that gets you resolution so that you can get online to look up proper DNS servers.
I only state this because of lines like this:
Been like this since ~noon November 1 for me.
I'm under the impression that Google's 8.8.8.8 is more intended for "long-term" use, but pleas do not quote me on that.
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
We hit Atlanta, And last week I saw both 4.2.2.1 and 4.2.2.2 show about 45% loss from both our network (AS36295) and my home cable connection (AS33363). Lasted till about friday. I figured they ratelimited ICMP because DNS resolution didn't seem to suffer at all. It seems to have cleared up however.
Nick Olsen Network Operations (855) FLSPEED x106
---------------------------------------- From: "Josh Luthman" <josh@imaginenetworksllc.com> Sent: Monday, November 05, 2012 11:43 AM To: "outages@outages.org" <outages@outages.org> Subject: [outages] Packet loss - Washington Level 3 - 4.2.2.2
Anyone else seeing this? Been like this since ~noon November 1 for me. No one else has said anything so I'm curious if it's something I did to upset them. 4. be22.clevohek-ccr01.mwrtn.rr.com 0.0% 273 16.2 13.1 6.1 21.6 2.5 5. ae10-0.cr0.dca20.tbone.rr.com 0.0% 273 24.6 20.8 16.9 29.2 2.3 6. ae-1-0.pr0.dca20.tbone.rr.com 0.0% 273 56.0 24.4 14.9 108.2 14.9 7. xe-4-0-0.edge2.Washington1.Level 0.0% 273 21.7 22.7 16.9 69.3 5.6 8. vlan90.csw4.Washington1.Level3.n 0.0% 273 27.2 25.0 21.6 37.8 4.0 9. ae-91-91.ebr1.Washington1.Level3 0.0% 273 23.3 22.0 20.7 24.0 0.4 10. ae-8-8.ebr1.Washington12.Level3. 0.0% 273 32.2 24.6 11.9 36.9 3.5 11. ae-1-51.edge2.Washington12.Level 14.3% 273 22.3 22.6 18.9 39.7 2.1 12. b.resolvers.Level3.net 28.6% 273 22.3 33.8 22.0
On Mon, Nov 05, 2012 at 12:20:58PM -0500, Nick Olsen wrote: 1419.
107.9 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Jeremy Chadwick -
Josh Luthman -
Nick Olsen