[outages] Level3 from LA to Korea down?

Jeremy Chadwick jdc at koitsu.org
Wed Jan 23 16:59:12 EST 2013


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 at 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 at 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 at outages.org [mailto:outages-bounces at 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 at outages.org
> > https://puck.nether.net/mailman/listinfo/outages
> >
> >

> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages




More information about the Outages mailing list