[outages] Level3 from LA to Korea down?
Colin Johnston
colinj at mx5.org.uk
Wed Jan 23 13:49:02 EST 2013
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 at 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 at outages.org [mailto:outages-bounces at outages.org] On Behalf Of Chris Stone
> Sent: Wednesday, January 23, 2013 12:20 PM
> To: outages at 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 at outages.org
> https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130123/3ac40416/attachment.htm>
More information about the Outages
mailing list