Have a customer that does a lot of email to Korea and saw their mail backing up this morning due to 'host not found' errors to a domain they email frequently. Figured they let their domain expire, but in checking it out, I find I cannot query the name servers for their domain, which are ns[1234].whoisdomain.kr. Traffic to them dies on Level3 in LA: traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 ge-6-24-576.car1.Denver1.Level3.net (4.28.16.137) 85.727 ms 85.724 ms 85.799 ms 2 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 35.938 ms 35.952 ms 35.948 ms 3 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 36.016 ms 35.953 ms 35.963 ms 4 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 36.122 ms * 40.685 ms 5 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 36.202 ms 36.222 ms 36.203 ms 6 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 36.225 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 36.263 ms ae-92-92.csw4.LosAngeles1.Level3.net (4.69.137.30) 35.944 ms 7 ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 35.992 ms ae-3-80.edge2.LosAngeles9.Level3.net (4.69.144.143) 36.094 ms 36.105 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 gateway.tbie.net (10.10.100.1) 4.191 ms 4.195 ms 4.203 ms 2 hlrn-dsl-gw01.hlrn.qwest.net (207.225.112.1) 44.353 ms 45.995 ms 47.282 ms 3 hlrn-agw1.inet.qwest.net (71.217.188.1) 48.971 ms 49.917 ms 51.637 ms 4 dvr-brdr-02.inet.qwest.net (67.14.24.118) 53.619 ms 55.320 ms 56.269 ms 5 63.146.26.134 (63.146.26.134) 77.074 ms 78.090 ms 79.713 ms 6 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 99.612 ms 95.310 ms 95.268 ms 7 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 97.331 ms 75.825 ms 76.472 ms 8 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 80.746 ms 78.862 ms 76.726 ms 9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 76.382 ms 77.211 ms 76.548 ms 10 ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 76.767 ms ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 76.151 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 77.360 ms 11 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 75.848 ms ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 75.706 ms ae-4-90.edge2.LosAngeles9.Level3.net (4.69.144.207) 77.386 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Anyone aware of any issues on that path to Asia? Thanks Chris -- Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more **************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ****************************************************************
I'm seeing the same thing, but I go over the same path. # tcptraceroute ns1.whoisdomain.kr 53 Selected device eth0.3, address 96.31.0.5, port 58472 for outgoing packets Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.230 ms 0.253 ms 0.182 ms 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.203 ms 0.141 ms 0.128 ms 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.598 ms 1.581 ms 1.570 ms 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.416 ms 7.361 ms 7.494 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 7.378 ms 7.384 ms 7.365 ms 6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 13.561 ms 13.551 ms 13.551 ms 7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 54.700 ms 54.474 ms 54.506 ms 8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 54.169 ms 54.108 ms 54.204 ms 9 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 54.413 ms 65.177 ms 54.365 ms 10 ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 55.650 ms 54.521 ms 54.555 ms 11 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 54.265 ms 54.276 ms 54.284 ms 12 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 54.145 ms 54.101 ms 54.205 ms 13 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 54.439 ms 54.395 ms 54.450 ms 14 * * * <snip> 30 * * * Destination not reached # If I test from another host that prefers NTT, I'm also not getting there: $ traceroute ns1.whoisdomain.kr traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 60 byte packets 1 ge-0-7-0-22.r05.chcgil09.us.bb.gin.ntt.net (204.42.253.5) 0.675 ms 0.755 ms 0.807 ms 2 ae-6.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.26) 2.255 ms 2.317 ms 2.311 ms 3 * ae-5.r20.snjsca04.us.bb.gin.ntt.net (129.250.3.107) 52.257 ms 51.238 ms 4 ae-1.r06.snjsca04.us.bb.gin.ntt.net (129.250.5.13) 55.245 ms 52.766 ms 57.304 ms 5 ae-4.r05.plalca01.us.bb.gin.ntt.net (129.250.5.32) 53.979 ms 53.444 ms 54.170 ms 6 * * * <snip> 30 * * * $ Frank From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Wednesday, January 23, 2013 12:20 PM To: outages@outages.org Subject: [outages] Level3 from LA to Korea down? Have a customer that does a lot of email to Korea and saw their mail backing up this morning due to 'host not found' errors to a domain they email frequently. Figured they let their domain expire, but in checking it out, I find I cannot query the name servers for their domain, which are ns[1234].whoisdomain.kr. Traffic to them dies on Level3 in LA: traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 ge-6-24-576.car1.Denver1.Level3.net (4.28.16.137) 85.727 ms 85.724 ms 85.799 ms 2 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 35.938 ms 35.952 ms 35.948 ms 3 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 36.016 ms 35.953 ms 35.963 ms 4 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 36.122 ms * 40.685 ms 5 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 36.202 ms 36.222 ms 36.203 ms 6 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 36.225 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 36.263 ms ae-92-92.csw4.LosAngeles1.Level3.net (4.69.137.30) 35.944 ms 7 ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 35.992 ms ae-3-80.edge2.LosAngeles9.Level3.net (4.69.144.143) 36.094 ms 36.105 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 gateway.tbie.net (10.10.100.1) 4.191 ms 4.195 ms 4.203 ms 2 hlrn-dsl-gw01.hlrn.qwest.net (207.225.112.1) 44.353 ms 45.995 ms 47.282 ms 3 hlrn-agw1.inet.qwest.net (71.217.188.1) 48.971 ms 49.917 ms 51.637 ms 4 dvr-brdr-02.inet.qwest.net (67.14.24.118) 53.619 ms 55.320 ms 56.269 ms 5 63.146.26.134 (63.146.26.134) 77.074 ms 78.090 ms 79.713 ms 6 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 99.612 ms 95.310 ms 95.268 ms 7 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 97.331 ms 75.825 ms 76.472 ms 8 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 80.746 ms 78.862 ms 76.726 ms 9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 76.382 ms 77.211 ms 76.548 ms 10 ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 76.767 ms ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 76.151 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 77.360 ms 11 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 75.848 ms ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 75.706 ms ae-4-90.edge2.LosAngeles9.Level3.net (4.69.144.207) 77.386 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Anyone aware of any issues on that path to Asia? Thanks Chris -- Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more **************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ****************************************************************
same here from c4l to kr, stops at london link to KR $ /usr/sbin/traceroute ns1.whoisdomain.kr traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 1.627 ms 0.324 ms 0.198 ms 2 82.197.70.2 (82.197.70.2) 1.072 ms 1.135 ms 1.001 ms 3 non-zod.c4l.co.uk (84.45.110.29) 0.830 ms 1.553 ms 12.423 ms 4 non-wolverine.c4l.co.uk (84.45.90.70) 1.923 ms 1.584 ms 1.461 ms 5 wolverine-kraken.c4l.co.uk (84.45.90.150) 2.450 ms 2.422 ms 2.463 ms 6 kraken-kusanagi.c4l.co.uk (84.45.90.169) 4.982 ms 219.573 ms 2.626 ms 7 ae3-101.lon11.ip4.tinet.net (77.67.64.229) 12.842 ms 2.832 ms * 8 * * * 9 * * * 10 * * * 11 * * * Colin On 23 Jan 2013, at 18:31, "Frank Bulk" <frnkblk@iname.com> wrote:
I’m seeing the same thing, but I go over the same path. # tcptraceroute ns1.whoisdomain.kr 53 Selected device eth0.3, address 96.31.0.5, port 58472 for outgoing packets Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.230 ms 0.253 ms 0.182 ms 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.203 ms 0.141 ms 0.128 ms 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.598 ms 1.581 ms 1.570 ms 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.416 ms 7.361 ms 7.494 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 7.378 ms 7.384 ms 7.365 ms 6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 13.561 ms 13.551 ms 13.551 ms 7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 54.700 ms 54.474 ms 54.506 ms 8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 54.169 ms 54.108 ms 54.204 ms 9 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 54.413 ms 65.177 ms 54.365 ms 10 ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 55.650 ms 54.521 ms 54.555 ms 11 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 54.265 ms 54.276 ms 54.284 ms 12 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 54.145 ms 54.101 ms 54.205 ms 13 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 54.439 ms 54.395 ms 54.450 ms 14 * * * <snip> 30 * * * Destination not reached #
If I test from another host that prefers NTT, I’m also not getting there: $ traceroute ns1.whoisdomain.kr traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 60 byte packets 1 ge-0-7-0-22.r05.chcgil09.us.bb.gin.ntt.net (204.42.253.5) 0.675 ms 0.755 ms 0.807 ms 2 ae-6.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.26) 2.255 ms 2.317 ms 2.311 ms 3 * ae-5.r20.snjsca04.us.bb.gin.ntt.net (129.250.3.107) 52.257 ms 51.238 ms 4 ae-1.r06.snjsca04.us.bb.gin.ntt.net (129.250.5.13) 55.245 ms 52.766 ms 57.304 ms 5 ae-4.r05.plalca01.us.bb.gin.ntt.net (129.250.5.32) 53.979 ms 53.444 ms 54.170 ms 6 * * * <snip> 30 * * * $
Frank
From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Wednesday, January 23, 2013 12:20 PM To: outages@outages.org Subject: [outages] Level3 from LA to Korea down?
Have a customer that does a lot of email to Korea and saw their mail backing up this morning due to 'host not found' errors to a domain they email frequently. Figured they let their domain expire, but in checking it out, I find I cannot query the name servers for their domain, which are ns[1234].whoisdomain.kr. Traffic to them dies on Level3 in LA:
traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 ge-6-24-576.car1.Denver1.Level3.net (4.28.16.137) 85.727 ms 85.724 ms 85.799 ms 2 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 35.938 ms 35.952 ms 35.948 ms 3 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 36.016 ms 35.953 ms 35.963 ms 4 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 36.122 ms * 40.685 ms 5 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 36.202 ms 36.222 ms 36.203 ms 6 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 36.225 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 36.263 ms ae-92-92.csw4.LosAngeles1.Level3.net(4.69.137.30) 35.944 ms 7 ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 35.992 ms ae-3-80.edge2.LosAngeles9.Level3.net (4.69.144.143) 36.094 ms 36.105 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 gateway.tbie.net (10.10.100.1) 4.191 ms 4.195 ms 4.203 ms 2 hlrn-dsl-gw01.hlrn.qwest.net (207.225.112.1) 44.353 ms 45.995 ms 47.282 ms 3 hlrn-agw1.inet.qwest.net (71.217.188.1) 48.971 ms 49.917 ms 51.637 ms 4 dvr-brdr-02.inet.qwest.net (67.14.24.118) 53.619 ms 55.320 ms 56.269 ms 5 63.146.26.134 (63.146.26.134) 77.074 ms 78.090 ms 79.713 ms 6 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 99.612 ms 95.310 ms 95.268 ms 7 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 97.331 ms 75.825 ms 76.472 ms 8 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 80.746 ms 78.862 ms 76.726 ms 9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 76.382 ms 77.211 ms 76.548 ms 10 ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 76.767 ms ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 76.151 ms ae-82-82.csw3.LosAngeles1.Level3.net(4.69.137.26) 77.360 ms 11 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 75.848 ms ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 75.706 ms ae-4-90.edge2.LosAngeles9.Level3.net(4.69.144.207) 77.386 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
Anyone aware of any issues on that path to Asia?
Thanks
Chris
--
Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more
**************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ****************************************************************
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I'm taking a different path (Charter over to XO), and don't appear to be making it. # tcptraceroute ns1.whoisdomain.kr 53 Selected device eth0, address 10.1.0.176, port 60828 for outgoing packets Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max 1 10.1.0.12 1.272 ms 2.132 ms 12.435 ms 2 71-87-7-193.static.eucl.wi.charter.com (71.87.7.193) 0.720 ms 0.495 ms 0.429 ms 3 dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com (96.34.19.192) 0.974 ms 0.838 ms 0.814 ms 4 crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com (96.34.22.188) 6.757 ms 2.755 ms 3.903 ms 5 crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com (96.34.18.52) 5.362 ms 2.709 ms 11.957 ms 6 crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com (96.34.19.236) 7.313 ms 11.155 ms 11.940 ms 7 bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com (96.34.2.146) 11.766 ms 7.213 ms 7.975 ms 8 bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com (96.34.0.212) 7.758 ms 9.431 ms 7.898 ms 9 bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com (96.34.0.157) 23.567 ms 17.380 ms 23.932 ms 10 ip65-46-44-169.z44-46-65.customer.algx.net (65.46.44.169) 19.161 ms 19.153 ms 19.144 ms 11 ae1d0.mcr2.minneapolis-mn.us.xo.net (216.156.1.86) 61.090 ms 61.010 ms 69.836 ms 12 vb1711.rar3.denver-co.us.xo.net (216.156.0.173) 70.083 ms 71.105 ms 71.968 ms 13 te0-13-0-0.rar3.la-ca.us.xo.net (207.88.12.86) 63.320 ms 64.526 ms 71.848 ms 14 207.88.14.218.ptr.us.xo.net (207.88.14.218) 60.845 ms 60.836 ms 60.858 ms 15 * * * <SNIP> 30 * * * Destination not reached # On Wed, Jan 23, 2013 at 12:31 PM, Frank Bulk <frnkblk@iname.com> wrote:
I’m seeing the same thing, but I go over the same path.****
# tcptraceroute ns1.whoisdomain.kr 53****
Selected device eth0.3, address 96.31.0.5, port 58472 for outgoing packets ****
Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max****
1 router-core-inside.mtcnet.net (96.31.0.254) 0.230 ms 0.253 ms 0.182 ms****
2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.203 ms 0.141 ms 0.128 ms*** *
3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.598 ms 1.581 ms 1.570 ms****
4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.416 ms 7.361 ms 7.494 ms****
5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 7.378 ms 7.384 ms 7.365 ms****
6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 13.561 ms 13.551 ms 13.551 ms****
7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 54.700 ms 54.474 ms 54.506 ms****
8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 54.169 ms 54.108 ms 54.204 ms****
9 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 54.413 ms 65.177 ms 54.365 ms****
10 ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 55.650 ms 54.521 ms 54.555 ms****
11 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 54.265 ms 54.276 ms 54.284 ms****
12 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 54.145 ms 54.101 ms 54.205 ms****
13 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 54.439 ms 54.395 ms 54.450 ms****
14 * * *****
<snip>****
30 * * *****
Destination not reached****
#****
** **
If I test from another host that prefers NTT, I’m also not getting there:* ***
$ traceroute ns1.whoisdomain.kr****
traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 60 byte packets****
1 ge-0-7-0-22.r05.chcgil09.us.bb.gin.ntt.net (204.42.253.5) 0.675 ms 0.755 ms 0.807 ms****
2 ae-6.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.26) 2.255 ms 2.317 ms 2.311 ms****
3 * ae-5.r20.snjsca04.us.bb.gin.ntt.net (129.250.3.107) 52.257 ms 51.238 ms****
4 ae-1.r06.snjsca04.us.bb.gin.ntt.net (129.250.5.13) 55.245 ms 52.766 ms 57.304 ms****
5 ae-4.r05.plalca01.us.bb.gin.ntt.net (129.250.5.32) 53.979 ms 53.444 ms 54.170 ms****
6 * * *****
<snip>****
30 * * *****
$****
** **
Frank****
** **
*From:* outages-bounces@outages.org [mailto:outages-bounces@outages.org] *On Behalf Of *Chris Stone *Sent:* Wednesday, January 23, 2013 12:20 PM *To:* outages@outages.org *Subject:* [outages] Level3 from LA to Korea down?****
** **
Have a customer that does a lot of email to Korea and saw their mail backing up this morning due to 'host not found' errors to a domain they email frequently. Figured they let their domain expire, but in checking it out, I find I cannot query the name servers for their domain, which are ns[1234].whoisdomain.kr. Traffic to them dies on Level3 in LA:
traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 ge-6-24-576.car1.Denver1.Level3.net (4.28.16.137) 85.727 ms 85.724 ms 85.799 ms 2 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 35.938 ms 35.952 ms 35.948 ms 3 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 36.016 ms 35.953 ms 35.963 ms 4 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 36.122 ms * 40.685 ms 5 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 36.202 ms 36.222 ms 36.203 ms 6 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 36.225 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 36.263 ms ae-92-92.csw4.LosAngeles1.Level3.net (4.69.137.30) 35.944 ms 7 ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 35.992 ms ae-3-80.edge2.LosAngeles9.Level3.net (4.69.144.143) 36.094 ms 36.105 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 60 byte packets 1 gateway.tbie.net (10.10.100.1) 4.191 ms 4.195 ms 4.203 ms 2 hlrn-dsl-gw01.hlrn.qwest.net (207.225.112.1) 44.353 ms 45.995 ms 47.282 ms 3 hlrn-agw1.inet.qwest.net (71.217.188.1) 48.971 ms 49.917 ms 51.637 ms 4 dvr-brdr-02.inet.qwest.net (67.14.24.118) 53.619 ms 55.320 ms 56.269 ms 5 63.146.26.134 (63.146.26.134) 77.074 ms 78.090 ms 79.713 ms 6 vlan51.ebr1.Denver1.Level3.net (4.69.147.94) 99.612 ms 95.310 ms 95.268 ms 7 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 97.331 ms 75.825 ms 76.472 ms 8 ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 80.746 ms 78.862 ms 76.726 ms 9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 76.382 ms 77.211 ms 76.548 ms 10 ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 76.767 ms ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 76.151 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 77.360 ms 11 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 75.848 ms ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 75.706 ms ae-4-90.edge2.LosAngeles9.Level3.net (4.69.144.207) 77.386 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
Anyone aware of any issues on that path to Asia?
Thanks
Chris****
--
Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more
**************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ********************************************************************
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- - Anthony Hook
On 01/23/2013 11:56 AM, Anthony Hook wrote:
I'm taking a different path (Charter over to XO), and don't appear to be making it.
# tcptraceroute ns1.whoisdomain.kr <http://ns1.whoisdomain.kr> 53 Selected device eth0, address 10.1.0.176, port 60828 for outgoing packets Tracing the path to ns1.whoisdomain.kr <http://ns1.whoisdomain.kr> (211.206.125.155) on TCP port 53 (domain), 30 hops max  1  10.1.0.12  1.272 ms  2.132 ms  12.435 ms  2  71-87-7-193.static.eucl.wi.charter.com <http://71-87-7-193.static.eucl.wi.charter.com> (71.87.7.193)  0.720 ms  0.495 ms  0.429 ms  3  dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com <http://dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com> (96.34.19.192)  0.974 ms  0.838 ms  0.814 ms  4  crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com <http://crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com> (96.34.22.188)  6.757 ms  2.755 ms  3.903 ms  5  crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com <http://crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com> (96.34.18.52)  5.362 ms  2.709 ms  11.957 ms  6  crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com <http://crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com> (96.34.19.236)  7.313 ms  11.155 ms  11.940 ms  7  bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com <http://bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com> (96.34.2.146)  11.766 ms  7.213 ms  7.975 ms  8  bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com <http://bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com> (96.34.0.212)  7.758 ms  9.431 ms  7.898 ms  9  bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com <http://bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com> (96.34.0.157)  23.567 ms  17.380 ms  23.932 ms 10  ip65-46-44-169.z44-46-65.customer.algx.net <http://ip65-46-44-169.z44-46-65.customer.algx.net> (65.46.44.169)  19.161 ms  19.153 ms  19.144 ms 11  ae1d0.mcr2.minneapolis-mn.us.xo.net <http://ae1d0.mcr2.minneapolis-mn.us.xo.net> (216.156.1.86)  61.090 ms  61.010 ms  69.836 ms 12  vb1711.rar3.denver-co.us.xo.net <http://vb1711.rar3.denver-co.us.xo.net> (216.156.0.173)  70.083 ms  71.105 ms  71.968 ms 13  te0-13-0-0.rar3.la-ca.us.xo.net <http://te0-13-0-0.rar3.la-ca.us.xo.net> (207.88.12.86)  63.320 ms  64.526 ms  71.848 ms 14  207.88.14.218.ptr.us.xo.net <http://207.88.14.218.ptr.us.xo.net> (207.88.14.218)  60.845 ms  60.836 ms  60.858 ms 15  * * * <SNIP> 30  * * * Destination not reached
Thanks - would seem from this and other posts, that they are not reachable from anywhere through anyone. Sounds like a major outage on their end, or with someone big between them and everyone else. Chris -- Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more **************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) **************************************************************** Only by avoiding the beginning of things can we escape their end. -- Cyril Connolly
According to http://host.robtex.com/ns1.whoisdomain.kr.html#shared, 98 domains use ns1.whoisdomain.kr. For ns2, ns3, and ns4, they all host 100 domains, each (likely the same ones). Frank From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Chris Stone Sent: Wednesday, January 23, 2013 1:42 PM To: OUTAGES Mailing List Subject: Re: [outages] Level3 from LA to Korea down? On 01/23/2013 11:56 AM, Anthony Hook wrote: I'm taking a different path (Charter over to XO), and don't appear to be making it. # tcptraceroute ns1.whoisdomain.kr 53 Selected device eth0, address 10.1.0.176, port 60828 for outgoing packets Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max  1  10.1.0.12  1.272 ms  2.132 ms  12.435 ms  2  71-87-7-193.static.eucl.wi.charter.com (71.87.7.193)  0.720 ms  0.495 ms  0.429 ms  3  dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com (96.34.19.192)  0.974 ms  0.838 ms  0.814 ms  4  crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com (96.34.22.188)  6.757 ms  2.755 ms  3.903 ms  5  crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com (96.34.18.52)  5.362 ms  2.709 ms  11.957 ms  6  crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com (96.34.19.236)  7.313 ms  11.155 ms  11.940 ms  7  bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com (96.34.2.146)  11.766 ms  7.213 ms  7.975 ms  8  bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com (96.34.0.212)  7.758 ms  9.431 ms  7.898 ms  9  bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com (96.34.0.157)  23.567 ms  17.380 ms  23.932 ms 10  ip65-46-44-169.z44-46-65.customer.algx.net (65.46.44.169)  19.161 ms  19.153 ms  19.144 ms 11  ae1d0.mcr2.minneapolis-mn.us.xo.net (216.156.1.86)  61.090 ms  61.010 ms  69.836 ms 12  vb1711.rar3.denver-co.us.xo.net (216.156.0.173)  70.083 ms  71.105 ms  71.968 ms 13  te0-13-0-0.rar3.la-ca.us.xo.net (207.88.12.86)  63.320 ms  64.526 ms  71.848 ms 14  207.88.14.218.ptr.us.xo.net (207.88.14.218)  60.845 ms  60.836 ms  60.858 ms 15  * * * <SNIP> 30  * * * Destination not reached Thanks - would seem from this and other posts, that they are not reachable from anywhere through anyone. Sounds like a major outage on their end, or with someone big between them and everyone else. Chris -- Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more **************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) **************************************************************** Only by avoiding the beginning of things can we escape their end. -- Cyril Connolly
This is probably a global outage... Cant access that host from within Asia even.
From Thailand (Using True ISP - An ADSL provider in thailand)
traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 1.114 ms 1.734 ms 2.472 ms 2 * * * 3 10.169.212.173 (10.169.212.173) 26.797 ms 28.974 ms 32.118 ms 4 119-46-176-133.static.asianet.co.th (119.46.176.133) 33.846 ms 34.289 ms 36.736 ms 5 61-91-210-50.static.asianet.co.th (61.91.210.50) 39.942 ms 42.583 ms 42.896 ms 6 * 61-91-213-36.static.asianet.co.th (61.91.213.36) 20.848 ms 21.274 ms 7 61-91-213-130.static.asianet.co.th (61.91.213.130) 23.416 ms 26.291 ms 29.046 ms 8 tig-net242-53.trueintergateway.com (113.21.242.53) 30.977 ms 34.826 ms tig-net242-41.trueintergateway.com (113.21.242.41) 35.725 ms 9 sg-icr-gs2-26-214.trueintergateway.com (122.144.26.214) 98.822 ms 99.218 ms 99.478 ms 10 tig-net241-198.trueintergateway.com (113.21.241.198) 104.861 ms 85.150 ms 85.027 ms 11 * * * <snip> 30 * * * The trace dies at True's POP in Hong Kong. -Sajal On Thu, Jan 24, 2013 at 3:23 AM, Frank Bulk <frnkblk@iname.com> wrote:
According to http://host.robtex.com/ns1.whoisdomain.kr.html#shared, 98 domains use ns1.whoisdomain.kr. For ns2, ns3, and ns4, they all host 100 domains, each (likely the same ones).****
** **
Frank****
** **
*From:* outages-bounces@outages.org [mailto:outages-bounces@outages.org] *On Behalf Of *Chris Stone *Sent:* Wednesday, January 23, 2013 1:42 PM *To:* OUTAGES Mailing List *Subject:* Re: [outages] Level3 from LA to Korea down?****
** **
On 01/23/2013 11:56 AM, Anthony Hook wrote:****
I'm taking a different path (Charter over to XO), and don't appear to be making it.****
** **
# tcptraceroute ns1.whoisdomain.kr 53****
Selected device eth0, address 10.1.0.176, port 60828 for outgoing packets* ***
Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max****
 1  10.1.0.12  1.272 ms  2.132 ms  12.435 ms****
 2  71-87-7-193.static.eucl.wi.charter.com (71.87.7.193)  0.720 ms  0.495 ms  0.429 ms****
 3  dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com (96.34.19.192)  0.974 ms  0.838 ms  0.814 ms****
 4  crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com (96.34.22.188)  6.757 ms  2.755 ms  3.903 ms****
 5  crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com (96.34.18.52)  5.362 ms  2.709 ms  11.957 ms****
 6  crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com (96.34.19.236)  7.313 ms  11.155 ms  11.940 ms****
 7  bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com (96.34.2.146)  11.766 ms  7.213 ms  7.975 ms****
 8  bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com (96.34.0.212)  7.758 ms  9.431 ms  7.898 ms****
 9  bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com (96.34.0.157)  23.567 ms  17.380 ms  23.932 ms****
10  ip65-46-44-169.z44-46-65.customer.algx.net (65.46.44.169)  19.161 ms  19.153 ms  19.144 ms****
11  ae1d0.mcr2.minneapolis-mn.us.xo.net (216.156.1.86)  61.090 ms  61.010 ms  69.836 ms****
12  vb1711.rar3.denver-co.us.xo.net (216.156.0.173)  70.083 ms  71.105 ms  71.968 ms****
13  te0-13-0-0.rar3.la-ca.us.xo.net (207.88.12.86)  63.320 ms  64.526 ms  71.848 ms****
14  207.88.14.218.ptr.us.xo.net (207.88.14.218)  60.845 ms  60.836 ms  60.858 ms****
15 Â * * *****
<SNIP>****
30 Â * * *****
Destination not reached****
** **
Thanks - would seem from this and other posts, that they are not reachable from anywhere through anyone. Sounds like a major outage on their end, or with someone big between them and everyone else.
Chris
****
--
Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more
**************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ****************************************************************
Only by avoiding the beginning of things can we escape their end. -- Cyril Connolly****
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
How is this a "global outage"? From my perspective you should be asking your Thai ISP why they don't have peering with other providers for redundancy (or if they do, why they haven't properly configured route failover, or even manually reconfigured to use an alternate peer). -- | 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 Thu, Jan 24, 2013 at 04:46:13AM +0700, Sajal Kayan wrote:
This is probably a global outage... Cant access that host from within Asia even.
From Thailand (Using True ISP - An ADSL provider in thailand)
traceroute to ns1.whoisdomain.kr (211.206.125.155), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 1.114 ms 1.734 ms 2.472 ms 2 * * * 3 10.169.212.173 (10.169.212.173) 26.797 ms 28.974 ms 32.118 ms 4 119-46-176-133.static.asianet.co.th (119.46.176.133) 33.846 ms 34.289 ms 36.736 ms 5 61-91-210-50.static.asianet.co.th (61.91.210.50) 39.942 ms 42.583 ms 42.896 ms 6 * 61-91-213-36.static.asianet.co.th (61.91.213.36) 20.848 ms 21.274 ms 7 61-91-213-130.static.asianet.co.th (61.91.213.130) 23.416 ms 26.291 ms 29.046 ms 8 tig-net242-53.trueintergateway.com (113.21.242.53) 30.977 ms 34.826 ms tig-net242-41.trueintergateway.com (113.21.242.41) 35.725 ms 9 sg-icr-gs2-26-214.trueintergateway.com (122.144.26.214) 98.822 ms 99.218 ms 99.478 ms 10 tig-net241-198.trueintergateway.com (113.21.241.198) 104.861 ms 85.150 ms 85.027 ms 11 * * * <snip> 30 * * *
The trace dies at True's POP in Hong Kong.
-Sajal
On Thu, Jan 24, 2013 at 3:23 AM, Frank Bulk <frnkblk@iname.com> wrote:
According to http://host.robtex.com/ns1.whoisdomain.kr.html#shared, 98 domains use ns1.whoisdomain.kr. For ns2, ns3, and ns4, they all host 100 domains, each (likely the same ones).****
** **
Frank****
** **
*From:* outages-bounces@outages.org [mailto:outages-bounces@outages.org] *On Behalf Of *Chris Stone *Sent:* Wednesday, January 23, 2013 1:42 PM *To:* OUTAGES Mailing List *Subject:* Re: [outages] Level3 from LA to Korea down?****
** **
On 01/23/2013 11:56 AM, Anthony Hook wrote:****
I'm taking a different path (Charter over to XO), and don't appear to be making it.****
** **
# tcptraceroute ns1.whoisdomain.kr 53****
Selected device eth0, address 10.1.0.176, port 60828 for outgoing packets* ***
Tracing the path to ns1.whoisdomain.kr (211.206.125.155) on TCP port 53 (domain), 30 hops max****
? 1 ? 10.1.0.12 ? 1.272 ms ? 2.132 ms ? 12.435 ms****
? 2 ? 71-87-7-193.static.eucl.wi.charter.com (71.87.7.193) ? 0.720 ms ? 0.495 ms ? 0.429 ms****
? 3 ? dtr02wautwi-tge-0-3-1-2.waut.wi.charter.com (96.34.19.192) ? 0.974 ms ? 0.838 ms ? 0.814 ms****
? 4 ? crr02stptwi-tge-0-0-0-7.stpt.wi.charter.com (96.34.22.188) ? 6.757 ms ? 2.755 ms ? 3.903 ms****
? 5 ? crr01stptwi-tge-0-4-0-12.stpt.wi.charter.com (96.34.18.52) ? 5.362 ms ? 2.709 ms ? 11.957 ms****
? 6 ? crr02euclwi-tge-0-6-0-8.eucl.wi.charter.com (96.34.19.236) ? 7.313 ms ? 11.155 ms ? 11.940 ms****
? 7 ? bbr02euclwi-tge-0-1-0-0.eucl.wi.charter.com (96.34.2.146) ? 11.766 ms ? 7.213 ms ? 7.975 ms****
? 8 ? bbr01euclwi-tge-0-2-0-4.eucl.wi.charter.com (96.34.0.212) ? 7.758 ms ? 9.431 ms ? 7.898 ms****
? 9 ? bbr01stcdmn-tge-0-0-0-7.stcd.mn.charter.com (96.34.0.157) ? 23.567 ms ? 17.380 ms ? 23.932 ms****
10 ? ip65-46-44-169.z44-46-65.customer.algx.net (65.46.44.169) ? 19.161 ms ? 19.153 ms ? 19.144 ms****
11 ? ae1d0.mcr2.minneapolis-mn.us.xo.net (216.156.1.86) ? 61.090 ms ? 61.010 ms ? 69.836 ms****
12 ? vb1711.rar3.denver-co.us.xo.net (216.156.0.173) ? 70.083 ms ? 71.105 ms ? 71.968 ms****
13 ? te0-13-0-0.rar3.la-ca.us.xo.net (207.88.12.86) ? 63.320 ms ? 64.526 ms ? 71.848 ms****
14 ? 207.88.14.218.ptr.us.xo.net (207.88.14.218) ? 60.845 ms ? 60.836 ms ? 60.858 ms****
15 ? * * *****
<SNIP>****
30 ? * * *****
Destination not reached****
** **
Thanks - would seem from this and other posts, that they are not reachable from anywhere through anyone. Sounds like a major outage on their end, or with someone big between them and everyone else.
Chris
****
--
Chris Stone, MCSE Vice President, CTO AxisInternet, Inc. http://www.axint.net DSL, VoIP, hosting, email filtering, co-location, online backup & more
**************************************************************** Authorized ScopTel IP PBX US Reseller - www.scopserv.com The most complete and comprehensive GUI on the market for telephony server management interface based on Voice over Internet Protocol (VoIP) ****************************************************************
Only by avoiding the beginning of things can we escape their end. -- Cyril Connolly****
_______________________________________________ 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
----- Original Message -----
From: "Frank Bulk" <frnkblk@iname.com>
I'm seeing the same thing, but I go over the same path.
# tcptraceroute ns1.whoisdomain.kr 53
For me, from Road Runner Tampa Bay, I can't even resolve the name of the name server; mtr to the IP (211.206.125.155) dies hard and reliably at ae-3-80.edge2.losangeles9.level3.net , 12 hops from here. The path to that point seems relatively clean. 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 #natog +1 727 647 1274
Different route than others but same results, though I think this is dying at the HE.net to Level3 connection in LA. traceroute 211.206.125.155 traceroute to 211.206.125.155 (211.206.125.155), 30 hops max, 40 byte packets 1 ge4-1.core.mpls.gippy.net (216.243.170.254) 1.385 ms 1.610 ms 1.736 ms 2 gw-uplink-1.gippy.net (209.240.78.33) 1.941 ms 1.676 ms 2.140 ms 3 ge0-2-0.m20-2.mpls.iphouse.net (216.250.189.189) 1.371 ms 1.429 ms 1.415 ms 4 ge0-2-0.m20-1.mpls.iphouse.net (216.250.189.190) 1.542 ms 1.361 ms 1.317 ms 5 gige-g3-6.core1.msp1.he.net (216.66.78.109) 1.230 ms 1.264 ms 1.235 ms 6 10gigabitethernet5-3.core1.den1.he.net (184.105.222.41) 22.855 ms 29.832 ms 22.887 ms 7 10gigabitethernet1-4.core1.lax2.he.net (72.52.92.38) 54.540 ms 55.175 ms 54.901 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * -- Nevin Lyne -- Founder / Director of Technology -- Gippy's Internet Solutions, LLC. / EngineHosting.com
participants (8)
-
Anthony Hook -
Chris Stone -
Colin Johnston -
Frank Bulk -
Jay Ashworth -
Jeremy Chadwick -
nevin＠enginehosting.com -
Sajal Kayan