North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: XO Outage
- From: Zaid Ali
- Date: Mon Sep 22 17:53:19 2008
I am seeing it on my end also:
traceroute: Warning: www.cnn.com has multiple addresses; using
157.166.224.25
traceroute to www.cnn.com (157.166.224.25), 64 hops max, 40 byte packets
1 hq-rtr1.genius.local (64.244.66.1) 0.891 ms 0.429 ms 0.449 ms
2 ip65-46-253-157.z253-46-65.customer.algx.net (65.46.253.157) 1.856
ms 2.860 ms 1.881 ms
3 p3-0-0.mar2.fremont-ca.us.xo.net (207.88.80.181) 16.922 ms 2.041
ms 2.013 ms
4 p4-3-0.rar2.sanjose-ca.us.xo.net (65.106.5.161) 2.637 ms 2.192 ms
2.823 ms
5 p6-0-0.rar1.la-ca.us.xo.net (65.106.0.17) 10.308 ms 10.258 ms
10.386 ms
6 207.88.13.22.ptr.us.xo.net (207.88.13.22) 10.931 ms 10.535 ms
10.037 ms
7 *^C
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 quit
Packets Pings
Host
Loss% Snt Last Avg Best Wrst StDev
1. scrubbed
0.0% 6 0.6 0.5 0.4 0.6 0.1
2.
ip65-44-114-97.z114-44-65.customer.algx.net
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
0.0% 38 0.4 0.4 0.3 0.5 0.1
2.
64.41.199.129
0.0% 37 1.0 24.0 0.6 330.2 80.4
3.
hr1-ge-7-47.santaclarasc5.savvis.net
0.0% 37 0.7 1.4 0.6 27.3 4.4
4.
er1-te-1-0-0.sanjose3equinix.savvis.net
0.0% 37 0.7 5.2 0.6 140.3 23.2
5.
cr1-tenge-0-7-5-0.sanfrancisco.savvis.net
2.7% 37 2.9 4.0 2.6 16.6 2.5
6.
cr2-pos-0-0-3-3.dallas.savvis.net
0.0% 37 42.6 43.1 42.3 51.4 1.4
7.
dpr1-ge-4-0-0.dallasequinix.savvis.net
0.0% 37 43.1 44.8 42.9 76.9 6.7
8.
er1-te-2-1.dallasequinix.savvis.net
0.0% 37 43.3 49.2 42.8 233.6 31.6
9.
208.175.175.90
0.0% 37 43.0 42.8 42.6 43.6 0.2
10.
65.106.1.102
75.0% 37 43.5 46.5 43.4 62.9 6.3
11.
65.106.1.101
0.0% 37 43.4 47.8 43.2 112.3 12.5
12.
65.106.0.41
0.0% 37 57.5 65.1 57.1 177.3 21.0
13.
65.106.1.73
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
|