When I traceroute from an IP on NTT's network I have no issues, but what's interesting is that the second hop is Cogent, so perhaps that's not a real test. $ traceroute dreamhost.com traceroute to dreamhost.com (208.97.187.204), 30 hops max, 60 byte packets 1 x.y.ntt.net (204.42.x.y) 0.517 ms 0.703 ms 0.837 ms 2 te0-3-0-6.ccr21.ord03.atlas.cogentco.com (154.54.12.81) 0.410 ms te0-2-0-6.ccr21.ord03.atlas.cogentco.com (154.54.10.29) 0.320 ms te0-3-0-6.ccr21.ord03.atlas.cogentco.com (154.54.12.81) 0.658 ms 3 te0-4-0-1.mpd21.ord01.atlas.cogentco.com (154.54.6.205) 0.656 ms te0-5-0-1.mpd22.ord01.atlas.cogentco.com (154.54.44.177) 0.746 ms te0-4-0-1.mpd22.ord01.atlas.cogentco.com (154.54.25.69) 0.656 ms 4 te0-4-0-5.mpd22.mci01.atlas.cogentco.com (154.54.45.157) 29.337 ms te0-3-0-1.mpd21.mci01.atlas.cogentco.com (154.54.7.138) 29.074 ms te0-3-0-1.mpd22.mci01.atlas.cogentco.com (154.54.7.165) 25.130 ms 5 te0-4-0-5.ccr21.dfw01.atlas.cogentco.com (154.54.46.198) 24.863 ms te0-3-0-6.ccr22.dfw01.atlas.cogentco.com (154.54.46.206) 30.186 ms te0-0-0-5.ccr21.dfw01.atlas.cogentco.com (154.54.5.217) 25.045 ms 6 te0-0-0-3.ccr21.iah01.atlas.cogentco.com (154.54.5.205) 30.362 ms te0-0-0-2.ccr22.iah01.atlas.cogentco.com (154.54.3.178) 30.168 ms te0-0-0-3.ccr21.iah01.atlas.cogentco.com (154.54.5.205) 30.385 ms 7 te0-0-0-5.ccr22.lax01.atlas.cogentco.com (154.54.5.194) 71.438 ms te0-2-0-3.ccr21.lax01.atlas.cogentco.com (154.54.44.242) 76.181 ms te0-1-0-6.ccr21.lax01.atlas.cogentco.com (154.54.0.225) 74.547 ms 8 te7-1.mag01.lax01.atlas.cogentco.com (154.54.28.142) 76.270 ms te8-1.mag01.lax01.atlas.cogentco.com (154.54.28.146) 71.655 ms 71.588 ms 9 38.122.20.218 (38.122.20.218) 74.635 ms 74.667 ms 74.787 ms 10 ip-66-33-201-114.dreamhost.com (66.33.201.114) 224.115 ms 224.248 ms 224.179 ms -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Andy Ringsmuth Sent: Friday, January 13, 2012 12:19 PM To: outages Subject: [outages] Problems at NTT? Anyone aware of issues with NTT.com? I'm not able to reach dreamhost.com located in southern California, which is a problem as they are our e-mail host. However, I can reach them from my home computer (different ISP) and a couple other ISPs. But some of my employees located across the United States working from home are not able to reach dreamhost.com either and thus no e-mail. A traceroute appears to show it dying at ntt.com: 618-Andy:~ andyring$ traceroute dreamhost.com traceroute to dreamhost.com (208.97.187.204), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.607 ms 0.288 ms 0.215 ms 2 upnllc.com (208.82.104.193) 0.672 ms 0.750 ms 0.620 ms 3 omh-edge-08.inet.qwest.net (65.116.176.185) 2.069 ms 4.529 ms 2.184 ms 4 omh-core-02.inet.qwest.net (205.171.132.57) 2.063 ms 2.018 ms 1.975 ms 5 chp-brdr-04.inet.qwest.net (67.14.8.234) 22.870 ms 19.210 ms 19.151 ms 6 63.146.26.230 (63.146.26.230) 19.612 ms 19.469 ms 19.503 ms 7 ae-6.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.26) 20.991 ms 19.648 ms 19.475 ms 8 ae-4.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.200) 53.644 ms 54.803 ms 48.801 ms 9 ae-0.r20.dllstx09.us.bb.gin.ntt.net (129.250.2.58) 53.730 ms 51.283 ms 51.848 ms 10 ae-5.r20.lsanca03.us.bb.gin.ntt.net (129.250.2.168) 73.374 ms 96.647 ms 66.866 ms 11 ae-1.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.2) 66.552 ms 68.726 ms 71.101 ms 12 * * * 13 * * * 14 * * * 15 * * *
From other locations, a traceroute goes right through. downforeveryoneorjustme.com reports dreamhost as alive.
--- Andy Ringsmuth 7215 Dorchester Court Lincoln, NE 68521 (402) 304-0083 andyring@inebraska.com _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages