[108028] in North American Network Operators' Group
Re: XO Outage
daemon@ATHENA.MIT.EDU (mike newton)
Mon Sep 22 17:41:22 2008
Date: Mon, 22 Sep 2008 14:40:39 -0700
From: mike newton <mike@digg.com>
To: Justin Sharp <sharp@sharpone.net>
In-Reply-To: <48D80FBA.50506@sharpone.net>
Cc: Nanog Mailing list <nanog@merit.edu>
Errors-To: nanog-bounces@nanog.org
yeah, we noticed it as well. looks like they're back now. i noticed
their routes drop off at about 14:16 PT and come back just after 14:30 PT=
=2E
+m
Justin Sharp wrote:
> We are seeing some issues w/ XO/Savvis peering..
>
> Trace from XO to Savvis IP space (64.75.10.151)
>
> Keys: Help Display mode Restart statistics Order of fields qui=
t
> =
=20
> Packets Pings
> Host =
=20
> Loss% Snt Last Avg Best Wrst StDev
> 1. scrubbed
> =20
> 0.0% 6 0.6 0.5 0.4 0.6 0.1
> 2.
> ip65-44-114-97.z114-44-65.customer.algx.net =
=20
> 0.0% 6 1.3 1.3 1.2 1.4 0.1
> 3. ???
>
>
> Trace from Savvis to XO IP space (65.44.114.97)
>
> 1. scrubbed
> =
=20
> 0.0% 38 0.4 0.4 0.3 0.5 0.1
> 2.
> 64.41.199.129 =
=20
> 0.0% 37 1.0 24.0 0.6 330.2 80.4
> 3.
> hr1-ge-7-47.santaclarasc5.savvis.net =
=20
> 0.0% 37 0.7 1.4 0.6 27.3 4.4
> 4.
> er1-te-1-0-0.sanjose3equinix.savvis.net =
=20
> 0.0% 37 0.7 5.2 0.6 140.3 23.2
> 5.
> cr1-tenge-0-7-5-0.sanfrancisco.savvis.net =
=20
> 2.7% 37 2.9 4.0 2.6 16.6 2.5
> 6.
> cr2-pos-0-0-3-3.dallas.savvis.net =
=20
> 0.0% 37 42.6 43.1 42.3 51.4 1.4
> 7.
> dpr1-ge-4-0-0.dallasequinix.savvis.net =
=20
> 0.0% 37 43.1 44.8 42.9 76.9 6.7
> 8.
> er1-te-2-1.dallasequinix.savvis.net =
=20
> 0.0% 37 43.3 49.2 42.8 233.6 31.6
> 9.
> 208.175.175.90 =
=20
> 0.0% 37 43.0 42.8 42.6 43.6 0.2
> 10.
> 65.106.1.102 =
=20
> 75.0% 37 43.5 46.5 43.4 62.9 6.3
> 11.
> 65.106.1.101 =
=20
> 0.0% 37 43.4 47.8 43.2 112.3 12.5
> 12.
> 65.106.0.41 =
=20
> 0.0% 37 57.5 65.1 57.1 177.3 21.0
> 13.
> 65.106.1.73 =
=20
> 0.0% 37 57.4 66.5 57.1 162.1 24.2
> 14. ???
>
> Trying to call into XO and they aren't even taking calls, they mention
> something about network issues in Spokane. Any ideas as to what is
> going on/ETA to fix?
>
> --Justin
>
>
