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
On Fri, Jan 13, 2012 at 13:19, Andy Ringsmuth <andyring@inebraska.com> wrote:
Anyone aware of issues with NTT.com? I'm not able to reach dreamhost.com
I have the same issue reaching dreamhost over NTT. darius@djmachine:~$ lft -d 80 dreamhost.com Tracing ........********** TTL LFT trace to dreamhost.com (208.97.187.204):80/tcp 2 gi4-2.cr1.phoenix.codero.com (69.64.66.29) 0.4ms 3 gi4-18.cr2.phoenix.codero.com (69.64.66.18) 0.3ms 4 ge-11-2-3.mpr3.phx2.us.above.net (64.125.192.193) 9.8ms 5 xe-2-2-0.cr1.lax112.us.above.net (64.125.28.70) 9.8ms 6 xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189) 9.8ms 7 ge-0-7-0-1.r05.lsanca03.us.bb.gin.ntt.net (129.250.9.157) 10.4ms 8 ae-5.r04.lsanca03.us.bb.gin.ntt.net (129.250.2.220) 9.6ms ** [80/tcp no reply from target] Try advanced options (use -VV to see packets). But over comcast it works fine: $ lft -d 80 dreamhost.comTracing ..........*.TTTL LFT trace to dreamhost.com (208.97.187.204):80/tcp 4 COMCAST-IP.edge3.Denver1.Level3.net (4.28.20.6) 1.9ms 5 pos-2-12-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.87.34) 15.2ms 6 pos-0-12-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.117) 41.5ms 7 as26347.losangeles.ca.ibone.comcast.net (75.149.228.206) 42.2ms 8 ip-66-33-201-114.dreamhost.com (66.33.201.114) 46.6ms 9 [target open] dreamhost.com (208.97.187.204):80 36.3ms The issue is probably at dreamhost's edge with NTT if I had to guess though. -- Darius Jahandarie
Likewise I am able to reach dreamhost.com via Comcast peering without issue. Tracing the path to www.dreamhost.com (208.97.187.204) on TCP port 80, 30 hops max 1 vlan31.colo3.tdc.nwt.dellservices.net (69.39.183.177) 9.312 ms 9.368 ms 9.954 ms 2 ge1-6.core2.tdc.nwt.dellservices.net (66.97.0.13) 9.945 ms 9.476 ms 9.932 ms 3 ge1-9.core1.ccs.phl.dellservices.net (216.182.7.58) 9.978 ms 9.475 ms 9.974 ms 4 * * * 5 te-2-1-0-2-cr01.ashburn.va.ibone.comcast.net (68.86.84.177) 9.375 ms 9.929 ms 9.979 ms 6 pos-4-3-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.87.70) 42.972 ms 42.362 ms 42.009 ms 7 pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.129) 41.953 ms 41.881 ms 41.714 ms 8 pos-0-12-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.117) 74.322 ms 74.553 ms 74.636 ms 9 as26347.losangeles.ca.ibone.comcast.net (75.149.228.206) 74.893 ms 74.728 ms 74.621 ms 10 ip-66-33-201-114.dreamhost.com (66.33.201.114) 75.651 ms 79.555 ms 75.968 ms 11 dreamhost.com (208.97.187.204) [open] 76.948 ms 74.091 ms 74.214 ms -Vinny -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Darius Jahandarie Sent: Friday, January 13, 2012 1:28 PM To: Andy Ringsmuth Cc: outages Subject: Re: [outages] Problems at NTT? On Fri, Jan 13, 2012 at 13:19, Andy Ringsmuth <andyring@inebraska.com> wrote:
Anyone aware of issues with NTT.com? I'm not able to reach dreamhost.com
I have the same issue reaching dreamhost over NTT. darius@djmachine:~$ lft -d 80 dreamhost.com Tracing ........********** TTL LFT trace to dreamhost.com (208.97.187.204):80/tcp 2 gi4-2.cr1.phoenix.codero.com (69.64.66.29) 0.4ms 3 gi4-18.cr2.phoenix.codero.com (69.64.66.18) 0.3ms 4 ge-11-2-3.mpr3.phx2.us.above.net (64.125.192.193) 9.8ms 5 xe-2-2-0.cr1.lax112.us.above.net (64.125.28.70) 9.8ms 6 xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189) 9.8ms 7 ge-0-7-0-1.r05.lsanca03.us.bb.gin.ntt.net (129.250.9.157) 10.4ms 8 ae-5.r04.lsanca03.us.bb.gin.ntt.net (129.250.2.220) 9.6ms ** [80/tcp no reply from target] Try advanced options (use -VV to see packets). But over comcast it works fine: $ lft -d 80 dreamhost.comTracing ..........*.TTTL LFT trace to dreamhost.com (208.97.187.204):80/tcp 4 COMCAST-IP.edge3.Denver1.Level3.net (4.28.20.6) 1.9ms 5 pos-2-12-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.87.34) 15.2ms 6 pos-0-12-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.117) 41.5ms 7 as26347.losangeles.ca.ibone.comcast.net (75.149.228.206) 42.2ms 8 ip-66-33-201-114.dreamhost.com (66.33.201.114) 46.6ms 9 [target open] dreamhost.com (208.97.187.204):80 36.3ms The issue is probably at dreamhost's edge with NTT if I had to guess though. -- Darius Jahandarie _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Working OK from Denver, CO out through Cogent... Tracing the path to dreamhost.com (208.97.187.204) on TCP port 80 (http), 30 hops max 1 10.10.100.254 2.052 ms 0.961 ms 0.919 ms 2 * * * 3 dsl-denver-gateway-01.axint.net (38.116.136.1) 56.847 ms 56.320 ms 55.346 ms 4 fa0-2.na01.b009854-0.den01.atlas.cogentco.com (38.112.6.145) 55.947 ms 56.480 ms 58.795 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 te0-0-0-5.ccr21.sfo01.atlas.cogentco.com (154.54.25.201) 83.373 ms 83.106 ms 82.652 ms 10 te0-3-0-4.ccr21.lax01.atlas.cogentco.com (154.54.45.93) 96.100 ms 96.811 ms 96.599 ms 11 * * * 12 38.122.20.218 96.617 ms 97.021 ms 96.535 ms 13 ip-66-33-201-114.dreamhost.com (66.33.201.114) 96.607 ms 96.476 ms 100.430 ms 14 dreamhost.com (208.97.187.204) [open] 98.192 ms 96.202 ms * Chris
works via cogent from uk traceroute wwmx5:~ colinj$ traceroute dreamhost.com traceroute to dreamhost.com (208.97.187.204), 64 hops max, 40 byte packets 1 192.168.1.2 (192.168.1.2) 3.179 ms 0.946 ms 0.888 ms 2 par8.the1.hso.uk.com (217.196.224.63) 16.422 ms 20.966 ms 15.885 ms 3 89.248.31.242 (89.248.31.242) 25.836 ms 70.455 ms 23.752 ms 4 eth-1-2-pcr2.the1.hso.uk.com (89.248.31.66) 15.234 ms 15.894 ms 15.112 ms 5 ge-0-0-0.643.pgr1.the1.hso.uk.com (89.248.31.90) 16.365 ms 42.333 ms 15.918 ms 6 10.0.10.253 (10.0.10.253) 15.813 ms 17.849 ms 56.462 ms 7 vl443.mpd01.lon01.atlas.cogentco.com (149.6.184.93) 16.113 ms 27.691 ms 19.884 ms 8 te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73) 17.215 ms te1-7.mpd02.lon01.atlas.cogentco.com (130.117.2.17) 54.133 ms te8-8.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 15.939 ms 9 te0-2-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.114) 91.793 ms te0-1-0-4.ccr22.lon13.atlas.cogentco.com (154.54.57.177) 98.119 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.114) 90.760 ms 10 te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225) 157.386 ms te0-1-0-4.ccr22.bos01.atlas.cogentco.com (130.117.0.185) 95.097 ms te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225) 91.561 ms 11 te0-4-0-5.ccr21.jfk02.atlas.cogentco.com (154.54.44.49) 94.773 ms te0-5-0-3.ccr22.jfk02.atlas.cogentco.com (154.54.44.65) 98.426 ms te0-1-0-7.ccr21.dca01.atlas.cogentco.com (154.54.26.6) 97.310 ms 12 te0-2-0-3.ccr22.atl01.atlas.cogentco.com (154.54.1.33) 144.399 ms te0-2-0-6.ccr21.atl01.atlas.cogentco.com (154.54.2.45) 196.274 ms te0-2-0-3.ccr21.atl01.atlas.cogentco.com (154.54.24.10) 223.306 ms 13 te0-0-0-6.ccr22.atl01.atlas.cogentco.com (154.54.28.222) 144.085 ms te0-3-0-2.ccr22.iah01.atlas.cogentco.com (66.28.4.90) 216.244 ms te0-0-0-6.ccr21.iah01.atlas.cogentco.com (154.54.29.2) 121.492 ms 14 te0-0-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.221) 281.385 ms te0-2-0-5.ccr22.lax01.atlas.cogentco.com (154.54.27.17) 169.916 ms te0-2-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.233) 159.912 ms 15 te8-1.mag01.lax01.atlas.cogentco.com (154.54.28.146) 164.784 ms 159.807 ms te7-1.mag01.lax01.atlas.cogentco.com (154.54.28.142) 157.725 ms 16 38.122.20.218 (38.122.20.218) 164.619 ms 158.597 ms 158.227 ms 17 ip-66-33-201-114.dreamhost.com (66.33.201.114) 178.666 ms 160.483 ms 165.028 ms 18 ip-66-33-201-114.dreamhost.com (66.33.201.114) 161.889 ms^C mx5:~ colinj$ On 13 Jan 2012, at 18:19, Andy Ringsmuth wrote:
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
Just checked from my home connectivity as well and likewise saw a path via Cogent was successful. It does seem to be isolated to NTT based on our collective data. -Vinny -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colin Johnston Sent: Friday, January 13, 2012 1:38 PM To: Andy Ringsmuth Cc: outages Subject: Re: [outages] Problems at NTT? works via cogent from uk traceroute wwmx5:~ colinj$ traceroute dreamhost.com traceroute to dreamhost.com (208.97.187.204), 64 hops max, 40 byte packets 1 192.168.1.2 (192.168.1.2) 3.179 ms 0.946 ms 0.888 ms 2 par8.the1.hso.uk.com (217.196.224.63) 16.422 ms 20.966 ms 15.885 ms 3 89.248.31.242 (89.248.31.242) 25.836 ms 70.455 ms 23.752 ms 4 eth-1-2-pcr2.the1.hso.uk.com (89.248.31.66) 15.234 ms 15.894 ms 15.112 ms 5 ge-0-0-0.643.pgr1.the1.hso.uk.com (89.248.31.90) 16.365 ms 42.333 ms 15.918 ms 6 10.0.10.253 (10.0.10.253) 15.813 ms 17.849 ms 56.462 ms 7 vl443.mpd01.lon01.atlas.cogentco.com (149.6.184.93) 16.113 ms 27.691 ms 19.884 ms 8 te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73) 17.215 ms te1-7.mpd02.lon01.atlas.cogentco.com (130.117.2.17) 54.133 ms te8-8.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 15.939 ms 9 te0-2-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.114) 91.793 ms te0-1-0-4.ccr22.lon13.atlas.cogentco.com (154.54.57.177) 98.119 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.114) 90.760 ms 10 te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225) 157.386 ms te0-1-0-4.ccr22.bos01.atlas.cogentco.com (130.117.0.185) 95.097 ms te0-0-0-1.ccr21.jfk02.atlas.cogentco.com (154.54.44.225) 91.561 ms 11 te0-4-0-5.ccr21.jfk02.atlas.cogentco.com (154.54.44.49) 94.773 ms te0-5-0-3.ccr22.jfk02.atlas.cogentco.com (154.54.44.65) 98.426 ms te0-1-0-7.ccr21.dca01.atlas.cogentco.com (154.54.26.6) 97.310 ms 12 te0-2-0-3.ccr22.atl01.atlas.cogentco.com (154.54.1.33) 144.399 ms te0-2-0-6.ccr21.atl01.atlas.cogentco.com (154.54.2.45) 196.274 ms te0-2-0-3.ccr21.atl01.atlas.cogentco.com (154.54.24.10) 223.306 ms 13 te0-0-0-6.ccr22.atl01.atlas.cogentco.com (154.54.28.222) 144.085 ms te0-3-0-2.ccr22.iah01.atlas.cogentco.com (66.28.4.90) 216.244 ms te0-0-0-6.ccr21.iah01.atlas.cogentco.com (154.54.29.2) 121.492 ms 14 te0-0-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.221) 281.385 ms te0-2-0-5.ccr22.lax01.atlas.cogentco.com (154.54.27.17) 169.916 ms te0-2-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.233) 159.912 ms 15 te8-1.mag01.lax01.atlas.cogentco.com (154.54.28.146) 164.784 ms 159.807 ms te7-1.mag01.lax01.atlas.cogentco.com (154.54.28.142) 157.725 ms 16 38.122.20.218 (38.122.20.218) 164.619 ms 158.597 ms 158.227 ms 17 ip-66-33-201-114.dreamhost.com (66.33.201.114) 178.666 ms 160.483 ms 165.028 ms 18 ip-66-33-201-114.dreamhost.com (66.33.201.114) 161.889 ms^C mx5:~ colinj$ On 13 Jan 2012, at 18:19, Andy Ringsmuth wrote:
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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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
On Fri, Jan 13, 2012 at 14:30, Frank Bulk <frnkblk@iname.com> wrote:
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.
It seems like all traffic to dreamhost has shifted from NTT to Cogent. darius@djmachine:~$ lft -d 80 dreamhost.com Tracing .........***.T TTL LFT trace to dreamhost.com (208.97.187.204):80/tcp 2 gi4-2.cr1.phoenix.codero.com (69.64.66.29) 0.3ms 3 gi4-18.cr2.phoenix.codero.com (69.64.66.18) 0.5ms 4 ge-11-2-3.mpr3.phx2.us.above.net (64.125.192.193) 9.8ms 5 xe-2-2-0.cr1.lax112.us.above.net (64.125.28.70) 44.7ms 6 xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189) 9.8ms ** [neglected] no reply packets received from TTL 7 8 te0-0-0-2.ccr22.lax01.atlas.cogentco.com (154.54.30.193) 10.7ms ** [neglected] no reply packets received from TTL 9 10 38.122.20.218 10.2ms 11 ip-66-33-201-114.dreamhost.com (66.33.201.114) 10.9ms 12 [target open] dreamhost.com (208.97.187.204):80 10.5ms -- Darius Jahandarie
----- Original Message -----
From: "Andy Ringsmuth" <andyring@inebraska.com>
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:
Ok from Tampa: HOST: www100 Snt: 10 Loss% Last Avg Best Wrst StDev 173.241.205.130 0.0% 0.7 0.6 0.5 0.7 0.1 gi2-3.border3.esnet.com 0.0% 1.9 0.7 0.5 1.9 0.4 gi1-47.202.ccr01.tpa01.atlas.cogentco.com 0.0% 22.3 6.9 0.6 22.3 8.7 te0-0-0-7.ccr22.iah01.atlas.cogentco.com 0.0% 21.9 21.9 21.8 22.2 0.1 te0-2-0-5.ccr22.lax01.atlas.cogentco.com 0.0% 57.8 57.9 57.8 58.2 0.1 te8-1.mag01.lax01.atlas.cogentco.com 0.0% 57.7 101.9 57.7 235.9 72.3 38.122.20.218 0.0% 58.1 58.5 57.9 62.4 1.4 ip-66-33-201-114.dreamhost.com 20.0% 58.3 71.0 58.1 144.2 29.8 dreamhost.com 0.0% 57.9 58.0 57.8 58.6 0.3 And also from St Pete RoadRunner: HOST: hades Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.1 0.0% 10 0.6 0.7 0.6 1.2 0.2 2.|-- smc-cablemodem 0.0% 10 1.1 1.1 1.1 1.2 0.0 3.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 4.|-- gig12-0-0-2011.tampfledc- 0.0% 10 30.0 15.8 10.9 30.0 7.3 5.|-- ge2-2-0.tampfledc-rtr3.ta 0.0% 10 13.4 17.4 11.3 48.6 11.3 6.|-- 72-31-208-1.net.bhntampa. 0.0% 10 12.5 18.3 10.7 68.2 17.6 7.|-- ae-11-11.cr0.dfw10.tbone. 0.0% 10 36.8 37.9 34.9 51.5 4.9 | `|-- 66.109.6.106 8.|-- ae-3-0.pr0.dfw10.tbone.rr 0.0% 10 37.6 38.3 35.9 42.7 2.5 | `|-- 66.109.9.105 9.|-- be-10-202-pe01.1950stemmo 0.0% 10 43.4 41.6 37.4 46.5 3.2 10.|-- pos-2-6-0-0-cr01.dallas.t 0.0% 10 37.9 39.2 35.4 50.7 5.3 11.|-- pos-0-7-0-0-cr01.losangel 0.0% 10 70.4 69.2 67.2 71.1 1.4 12.|-- as26347.losangeles.ca.ibo 0.0% 10 67.9 68.4 66.4 71.5 1.6 13.|-- ip-66-33-201-114.dreamhos 60.0% 10 80.9 76.5 73.6 80.9 3.1 14.|-- dreamhost.com 10.0% 10 77.5 73.7 71.5 77.5 1.7 Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
participants (7)
-
Andy Ringsmuth -
Chris Stone -
Colin Johnston -
Darius Jahandarie -
Frank Bulk -
Jay Ashworth -
Vinny_Abello＠Dell.com