Comments on: When OpenDNS is unreachable http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable A permanent record for what's interesting today - this is my live journal Fri, 25 Jul 2008 03:11:01 +0000 http://wordpress.org/?v=2.6 By: byte http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131958 byte Thu, 28 Feb 2008 01:25:08 +0000 http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131958 @wahlau: who knows. Maybe it was a provider thing? @david: a traceroute that should have worked, but didn't: [-(~)> traceroute 208.67.219.60 traceroute to 208.67.219.60 (208.67.219.60), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 1.838 ms 3.553 ms 3.597 ms 2 r124-19-0-1.gwy.unwired.net.au (124.19.0.1) 91.918 ms 121.643 ms 141.543 ms 3 v2227-cr2.glb.mel.bbn.unwired.net.au (125.63.254.74) 181.648 ms 231.463 ms 251.492 ms 4 125.63.254.206 (125.63.254.206) 261.543 ms 321.827 ms 331.265 ms 5 203.94.152.85 (203.94.152.85) 342.128 ms 341.360 ms 342.026 ms 6 3821.Gi0.br1.cit190.uecomm.net.au (218.185.31.158) 342.249 ms 69.781 ms 139.717 ms 7 VLAN323.o3mlc76f05.optus.net.au (61.88.143.197) 179.970 ms 279.557 ms 309.477 ms 8 61.88.221.73 (61.88.221.73) 339.445 ms 360.216 ms 379.313 ms 9 203.208.192.201 (203.208.192.201) 409.340 ms 429.219 ms 449.179 ms 10 203.208.145.154 (203.208.145.154) 469.175 ms gi1-7.ccr01.lax04.atlas.cogentco.com (154.54.12.221) 489.148 ms 203.208.145.154 (203.208.145.154) 538.985 ms 11 te4-3.ccr02.lax01.atlas.cogentco.com (154.54.6.241) 508.973 ms te3-3.mpd01.lax01.atlas.cogentco.com (154.54.24.61) 558.896 ms te4-3.ccr02.lax01.atlas.cogentco.com (154.54.6.241) 578.756 ms 12 te3-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.185) 459.818 ms te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.181) 259.899 ms te4-1.mpd01.sjc01.atlas.cogentco.com (154.54.6.30) 299.956 ms 13 te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 349.710 ms te3-3.mpd01.sfo01.atlas.cogentco.com (154.54.6.133) 369.796 ms te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 409.500 ms 14 te4-4.mpd01.sjc04.atlas.cogentco.com (154.54.7.174) 659.608 ms vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 639.628 ms 649.370 ms 15 38.104.140.46 (38.104.140.46) 429.308 ms 449.190 ms 469.133 ms 16 208.67.219.60 (208.67.219.60) 499.270 ms 528.946 ms 559.058 ms And from the machine that worked (elsewhere, different route): traceroute to 208.67.219.60 (208.67.219.60), 30 hops max, 40 byte packets 1 202.190.174.2 (202.190.174.2) 7.176 ms 7.111 ms 7.078 ms 2 ge5-0.bkj90.jaring.my (161.142.173.90) 7.216 ms 7.304 ms 7.278 ms 3 POS3-0-2.gw3.KUL1.asianetcom.net (203.192.154.153) 7.252 ms 7.225 ms 7.266 ms 4 ip-202-147-48-214.asianetcom.net (202.147.48.214) 12.557 ms 12.531 ms 12.504 ms 5 po15-0-1.cr2.nrt1.asianetcom.net (202.147.32.94) 95.057 ms 95.036 ms 95.075 ms 6 ip-202-147-0-166.asianetcom.net (202.147.0.166) 232.267 ms 231.412 ms 232.718 ms 7 gi1-20.mpd01.lax05.atlas.cogentco.com (154.54.13.53) 234.511 ms 226.900 ms 228.430 ms 8 vl3491.ccr02.lax01.atlas.cogentco.com (154.54.3.141) 220.168 ms vl3492.mpd01.lax01.atlas.cogentco.com (154.54.3.9) 228.323 ms vl3491.ccr02.lax01.atlas.cogentco.com (154.54.3.141) 220.194 ms 9 te4-1.mpd01.sjc01.atlas.cogentco.com (154.54.6.30) 221.176 ms te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 233.340 ms te3-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.185) 221.118 ms 10 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 222.604 ms te3-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.125) 217.566 ms te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 222.552 ms 11 vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 222.521 ms te4-4.mpd01.sjc04.atlas.cogentco.com (154.54.7.174) 221.970 ms vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 222.465 ms 12 38.104.140.46 (38.104.140.46) 230.831 ms 222.115 ms 225.672 ms 13 208.67.219.60 (208.67.219.60) 225.043 ms 225.017 ms 225.102 ms Hope this helps! @wahlau: who knows. Maybe it was a provider thing?

@david: a traceroute that should have worked, but didn’t:
[-(~)> traceroute 208.67.219.60
traceroute to 208.67.219.60 (208.67.219.60), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.838 ms 3.553 ms 3.597 ms
2 r124-19-0-1.gwy.unwired.net.au (124.19.0.1) 91.918 ms 121.643 ms 141.543 ms
3 v2227-cr2.glb.mel.bbn.unwired.net.au (125.63.254.74) 181.648 ms 231.463 ms 251.492 ms
4 125.63.254.206 (125.63.254.206) 261.543 ms 321.827 ms 331.265 ms
5 203.94.152.85 (203.94.152.85) 342.128 ms 341.360 ms 342.026 ms
6 3821.Gi0.br1.cit190.uecomm.net.au (218.185.31.158) 342.249 ms 69.781 ms 139.717 ms
7 VLAN323.o3mlc76f05.optus.net.au (61.88.143.197) 179.970 ms 279.557 ms 309.477 ms
8 61.88.221.73 (61.88.221.73) 339.445 ms 360.216 ms 379.313 ms
9 203.208.192.201 (203.208.192.201) 409.340 ms 429.219 ms 449.179 ms
10 203.208.145.154 (203.208.145.154) 469.175 ms gi1-7.ccr01.lax04.atlas.cogentco.com (154.54.12.221) 489.148 ms 203.208.145.154 (203.208.145.154) 538.985 ms
11 te4-3.ccr02.lax01.atlas.cogentco.com (154.54.6.241) 508.973 ms te3-3.mpd01.lax01.atlas.cogentco.com (154.54.24.61) 558.896 ms te4-3.ccr02.lax01.atlas.cogentco.com (154.54.6.241) 578.756 ms
12 te3-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.185) 459.818 ms te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.181) 259.899 ms te4-1.mpd01.sjc01.atlas.cogentco.com (154.54.6.30) 299.956 ms
13 te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 349.710 ms te3-3.mpd01.sfo01.atlas.cogentco.com (154.54.6.133) 369.796 ms te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 409.500 ms
14 te4-4.mpd01.sjc04.atlas.cogentco.com (154.54.7.174) 659.608 ms vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 639.628 ms 649.370 ms
15 38.104.140.46 (38.104.140.46) 429.308 ms 449.190 ms 469.133 ms
16 208.67.219.60 (208.67.219.60) 499.270 ms 528.946 ms 559.058 ms

And from the machine that worked (elsewhere, different route):
traceroute to 208.67.219.60 (208.67.219.60), 30 hops max, 40 byte packets
1 202.190.174.2 (202.190.174.2) 7.176 ms 7.111 ms 7.078 ms
2 ge5-0.bkj90.jaring.my (161.142.173.90) 7.216 ms 7.304 ms 7.278 ms
3 POS3-0-2.gw3.KUL1.asianetcom.net (203.192.154.153) 7.252 ms 7.225 ms 7.266 ms
4 ip-202-147-48-214.asianetcom.net (202.147.48.214) 12.557 ms 12.531 ms 12.504 ms
5 po15-0-1.cr2.nrt1.asianetcom.net (202.147.32.94) 95.057 ms 95.036 ms 95.075 ms
6 ip-202-147-0-166.asianetcom.net (202.147.0.166) 232.267 ms 231.412 ms 232.718 ms
7 gi1-20.mpd01.lax05.atlas.cogentco.com (154.54.13.53) 234.511 ms 226.900 ms 228.430 ms
8 vl3491.ccr02.lax01.atlas.cogentco.com (154.54.3.141) 220.168 ms vl3492.mpd01.lax01.atlas.cogentco.com (154.54.3.9) 228.323 ms vl3491.ccr02.lax01.atlas.cogentco.com (154.54.3.141) 220.194 ms
9 te4-1.mpd01.sjc01.atlas.cogentco.com (154.54.6.30) 221.176 ms te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 233.340 ms te3-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.185) 221.118 ms
10 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 222.604 ms te3-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.125) 217.566 ms te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 222.552 ms
11 vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 222.521 ms te4-4.mpd01.sjc04.atlas.cogentco.com (154.54.7.174) 221.970 ms vl3490.mpd01.sjc04.atlas.cogentco.com (154.54.2.166) 222.465 ms
12 38.104.140.46 (38.104.140.46) 230.831 ms 222.115 ms 225.672 ms
13 208.67.219.60 (208.67.219.60) 225.043 ms 225.017 ms 225.102 ms

Hope this helps!

]]> By: wahlau http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131957 wahlau Thu, 28 Feb 2008 01:03:08 +0000 http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131957 at my end i did not experience any problem so far... could it be your provider's issue then? at my end i did not experience any problem so far… could it be your provider’s issue then?

]]> By: David Ulevitch http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131945 David Ulevitch Wed, 27 Feb 2008 17:05:20 +0000 http://www.bytebot.net/blog/archives/2008/02/27/when-opendns-is-unreachable#comment-131945 Ugh! That's quite weird. Can you send us a full traceroute? We weren't offline last night anywhere -- though we've had a couple emails from folks near Seattle who had some issues. I'd love to figure out what went wrong... Ugh! That’s quite weird. Can you send us a full traceroute? We weren’t offline last night anywhere — though we’ve had a couple emails from folks near Seattle who had some issues.

I’d love to figure out what went wrong…

]]>