Re: XO outage in NJ/NY?

2012-08-30 Thread virendra rode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/30/2012 01:10 PM, chris wrote: > Anyone heard anything about an XO fiber cut in northeast? We have > had a bunch of issues with some DID's in NJ today and one of our > carriers forwarded a a vague statement from XO: > > *XO Communications is c

Re: XO outage in NJ/NY?

2012-08-30 Thread George Herbert
For anyone not already familiar, go sign up at: https://puck.nether.net/mailman/listinfo/outages On Thu, Aug 30, 2012 at 1:13 PM, Blake Dunlap wrote: > I suggest subscribing to outages. They are chatting about such a fiber cut, > and are generally the place to look for major outage level event

Re: XO outage in NJ/NY?

2012-08-30 Thread Blake Dunlap
I suggest subscribing to outages. They are chatting about such a fiber cut, and are generally the place to look for major outage level events like the below. -Blake On Thu, Aug 30, 2012 at 3:10 PM, chris wrote: > Anyone heard anything about an XO fiber cut in northeast? We have had a > bunch of

Re: XO Outage

2008-09-22 Thread Zaid Ali
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

Re: XO Outage

2008-09-22 Thread Justin Sharp
Seems like Savvis/XO routes have been restored, albeit through an unusual Dallas route (usually takes an XO Los Angeles route).. 1. scrubbed 0.0% 2040.4 0.7 0.3 7.0 0.9 2. ip65-44-114-97.z114-44-65.customer.al

Re: XO Outage

2008-09-22 Thread Mike Lyon
Also seeing some issues with XO out here: Tracing route to yahoo.com [68.180.206.184] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 10.100.20.1 2 2 ms 1 ms 2 ms sjcisr01-int.wyse.com [10.100.1.15] 3 3 ms 2 ms 2 ms 132.237.245.1 4 3 ms 3 ms

Re: XO Outage

2008-09-22 Thread mike newton
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. +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