[outages] Level3 from LA to Korea down?

Chris Stone cstone at axint.net
Wed Jan 23 14:41:53 EST 2013


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130123/8df106b3/attachment.htm>


More information about the Outages mailing list