[126564] in North American Network Operators' Group
RE: Extended outage at Vitelity / XO?
daemon@ATHENA.MIT.EDU (James J. Lumby II)
Fri May 21 09:36:10 2010
From: "James J. Lumby II" <james@cpctechnology.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Fri, 21 May 2010 08:35:37 -0500
Cc: "graham.freeman@cernio.com" <graham.freeman@cernio.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Our carrier, icall, had the same problem, so it wasn't just vitality. It g=
ot fixed this morning:
2010-05-21 8:32AM EST - XO Communications and Acme Packet, the vendor of th=
e failed equipment, have made repairs and resolved the issue. We do not exp=
ect any further issues at this time. A formal RFO will be provided once we =
have received one.
2010-05-20 9:53PM EST - XO technicans have been unable to remedy the issue =
in the projected timeline. We are awaiting further updates.
2010-05-20 8:48PM EST - XO technicans are on-site and have provided an esti=
mated resolution time of 30 minutes.
2010-05-20 7:15PM EST - XO Communications, one of our primary inbound DID p=
roviders, is currently experiencing a major equipment outage. This outage i=
s affecting many of our US inbound DIDs.
So, no, it doesn't look like an billing dispute imo.
Thank you,
James Lumby
CPC Technologies, LLC.
http://www.cpctechnology.com
817-435-0010 x 5040
Subject: Extended outage at Vitelity / XO?
To: NANOG list <nanog@nanog.org>
Message-ID: <C4AEA55D-FD64-4849-B034-138E7134BF32@gmail.com>
Content-Type: text/plain; charset=3Dus-ascii
Hi, folks,
All 30 of the DIDs I have at one of VOIP providers, Vitelity.net, have been=
offline for more than 8 hours as of this writing.
Vitelity quickly acknowledged the problem, and are characterizing this as a=
"global DID outage" at XO Communications, affecting "over 100,000 of [Vite=
lity's] DIDs alone and many others throughout [XO's] network." Now, I kn=
ow major outages do happen, and service with Vitelity has been generally go=
od, but 8 hours and counting is pretty awful.
I'm worried that this may in fact be the result of a contract dispute of so=
me kind between Vitelity and XO, and, if so, that this may be an even bigge=
r problem for me than it already is.
Can anyone else confirm Vitelity's report of widespread outages with XO?
thanks,
Graham
