I'm OK to that IP as well, but when I query www.google.com, I get multiple IPs, but here are the ones that in in 147: DNS Server IP Route (for me) 205.234.170.217 (tiggee) 74.125.79.147 Amsterdam 208.67.222.222 (opendns) 64.233.183.147 Amsterdam 4.2.2.1 (verizon) 74.125.19.147 San Jose 198.6.1.3 (uu.net/verizon) 74.125.47.147 Washington DC (yay) That's a lot of different answers for the same question! So maybe the problem is that some DNS servers are smarter than others. I am on Verizon FIOS in Northern VA (DC), and use tiggee's free resolving service, http://www.resolvingnameserver.com/freerns.html (they are great for DNS hosting). I used to use 198.6.1.1, but it seems so did everyone else who used to work at UUnet, and they shut it off. Rather than using 198.6.1.3 everywhere (which I'm sure the network folk would appreciate), I found Tiggee's resolving name service, which is nicely anycasted. So what's the deal here? Caching? Beckman On Fri, 6 Feb 2009, Wallace Keith wrote:
Looks ok from Boston-
3 core2.po1-bbnet1.bsn.pnap.net (63.251.128.18) 2.590 ms 3.988 ms 3.181 ms 4 207.88.182.33.ptr.us.xo.net (207.88.182.33) 26.636 ms 7.651 ms 11.977 ms 5 207.88.182.18.ptr.us.xo.net (207.88.182.18) 7.603 ms 8.174 ms 7.405 ms 6 216.239.49.217 (216.239.49.217) 8.219 ms 8.388 ms 7.510 ms 7 72.14.236.213 (72.14.236.213) 8.468 ms 66.249.94.235 (66.249.94.235) 16.799 ms 72.14.236.213 (72.14.236.213) 9.196 ms 8 72.14.238.138 (72.14.238.138) 27.405 ms 209.85.248.216 (209.85.248.216) 16.352 ms 15.785 ms 9 72.14.238.235 (72.14.238.235) 15.691 ms 14.641 ms 15.628 ms 10 209.85.255.194 (209.85.255.194) 39.077 ms 72.14.239.136 (72.14.239.136) 31.206 ms 64.233.174.46 (64.233.174.46) 32.528 ms 11 209.85.254.247 (209.85.254.247) 28.897 ms 209.85.254.249 (209.85.254.249) 29.192 ms 29.649 ms 12 209.85.255.194 (209.85.255.194) 29.326 ms gw-in-f100.google.com (74.125.67.100) 28.393 ms 209.85.255.194 (209.85.255.194) 35.464 ms
-----Original Message----- From: Peter Beckman [mailto:beckman@angryox.com] Sent: Friday, February 06, 2009 11:01 AM To: nanog@nanog.org Subject: L3: Google from DC via the Netherlands?
Seems strange. Had a partial outage on Verizon network this morning around 9:50am EST, then when it came back around 10:05am, google routed via the Netherlands. My guess is that there's some sort of routing problem making my fastest or least cost route go to the Netherlands, but I wanted to find out if there was an ongoing issue, or if the Netherlands simply now serves the US East Coast for google.
Isn't there anything closer? Or is this just indicative of an ongoing L3 outage? I'm guessing it's cheaper/faster to get to Google somewhere in the US, but maybe someone on NANOG knows better than I do.
HOST: octal.angryox.com Loss% Snt Last Avg Best Wrst StDev 1. tomato.angryox.com 0.0% 20 0.6 0.6 0.5 0.7 0.0 2. 10.1.41.15 0.0% 20 2.1 4.2 1.9 42.8 9.1 3. p4-2.lcr-02.washdc.verizon-g 0.0% 20 1.5 1.5 1.3 2.3 0.2 4. 130.81.29.218 0.0% 20 2.0 7.3 2.0 45.0 11.9 5. 0.so-1-2-0.xl4.iad8.alter.ne 0.0% 20 2.4 2.4 2.3 3.3 0.2 6. 0.ge-3-3-0.br2.iad8.alter.ne 0.0% 20 2.4 2.4 2.3 2.5 0.1 7. te-11-3-0.edge1.washington4. 0.0% 20 2.4 12.2 2.3 151.2 33.6 8. vlan99.csw4.washington1.leve 0.0% 20 3.1 7.3 3.0 15.0 4.3 9. ae-92-92.ebr2.washington1.le 0.0% 20 3.2 3.3 3.1 3.6 0.1 10. ae-42-42.ebr2.frankfurt1.lev 0.0% 20 94.1 94.4 93.7 104.0 2.3 11. ae-2-2.ebr1.dusseldorf1.leve 0.0% 20 106.1 100.6 95.8 107.0 4.1 12. ae-46-106.ebr2.dusseldorf1.l 0.0% 20 100.4 103.1 98.0 111.0 4.3 13. ae-41.ebr1.amsterdam1.level3 0.0% 20 107.2 99.9 94.4 107.7 5.7 14. ae-11-53.car1.amsterdam1.lev 0.0% 20 94.5 95.0 94.1 102.6 2.0 15. 212.72.42.14 0.0% 20 94.9 98.8 94.5 133.9 12.0 16. 209.85.254.250 0.0% 20 95.4 95.4 94.8 97.0 0.5 17. 72.14.233.114 0.0% 20 100.9 107.2 100.7 140.6 9.7 18. 209.85.255.166 0.0% 20 108.9 109.1 107.5 117.3 2.1 19. 209.85.255.110 5.0% 20 109.5 112.4 106.3 119.9 4.7 20. ew-in-f147.google.com 5.0% 20 107.9 108.0 107.5 108.9 0.3
Fri Feb 6 10:56:09 2009 Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. tomato.angryox.com 0.0% 8 0.6 0.6 0.5 0.6 0.0 2. 10.1.41.15 0.0% 8 2.1 2.4 2.1 3.3 0.4 3. P4-2.LCR-02.WASHDC.verizon-gni.net 0.0% 8 1.4 1.4 1.3 1.5 0.1 4. 130.81.29.218 0.0% 8 2.1 9.1 1.9 59.0 20.2 5. 0.so-1-2-0.XL4.IAD8.ALTER.NET 0.0% 8 2.4 2.4 2.3 2.6 0.1 0.so-6-1-0.XL4.IAD8.ALTER.NET 6. 0.ge-7-1-0.BR2.IAD8.ALTER.NET 0.0% 8 2.5 2.5 2.4 2.6 0.1 0.ge-3-3-0.BR2.IAD8.ALTER.NET 0.ge-5-1-0.BR2.IAD8.ALTER.NET 0.ge-7-0-0.BR2.IAD8.ALTER.NET 7. te-11-3-0.edge1.Washington4.level3.net 0.0% 7 2.4 6.0 2.3 27.2 9.4 8. vlan79.csw2.Washington1.Level3.net 0.0% 7 3.2 8.3 3.2 13.5 4.2 9. ae-72-72.ebr2.Washington1.Level3.net 0.0% 7 3.7 3.5 3.1 4.0 0.3 10. ae-44-44.ebr2.Frankfurt1.Level3.net 0.0% 7 94.5 94.9 94.4 97.2 1.0 11. ae-2-2.ebr1.Dusseldorf1.Level3.net 0.0% 7 106.2 100.7 96.4 106.7 4.6 12. ae-46-106.ebr2.Dusseldorf1.Level3.net 0.0% 7 107.6 106.1 100.1 108.9 3.0 13. ae-41.ebr1.Amsterdam1.Level3.net 0.0% 7 95.5 100.6 95.4 108.3 5.9 14. ae-11-55.car1.Amsterdam1.Level3.net 0.0% 7 95.3 95.8 94.4 98.7 1.5 15. GOOGLE-INC.car1.Amsterdam1.Level3.net 0.0% 7 97.0 96.7 96.5 97.0 0.2 16. 209.85.254.250 0.0% 7 102.0 97.0 95.7 102.0 2.2 17. 72.14.233.114 0.0% 7 107.5 104.8 101.5 107.5 2.7 209.85.248.79 18. 209.85.255.70 0.0% 7 109.8 109.1 107.9 110.3 0.8 72.14.239.123 209.85.255.166 209.85.255.20 19. 209.85.255.98 0.0% 7 118.3 114.9 109.7 120.2 4.6 209.85.255.102 209.85.255.110 20. ew-in-f103.google.com 0.0% 7 110.0 109.4 108.0 110.6 1.1
------------------------------------------------------------------------ --- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ------------------------------------------------------------------------ ---
--------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------