- Previous message: John Martinez: "Re: XO peering."
- Maybe in reply to: Stefan Molnar: "XO peering."
- Next in thread: Stefan Molnar: "Re: XO peering."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Mort, Eric (no email)
Date: Tue Mar 10 2009 - 12:41:19 EDT
We had some hardware issues in San Jose which triggered some other
ugliness. We believe we have the issues mitigated at this time. Folks
still seeing issues are encouraged to hit me up offline.
Thanks,
Eric J. Mort
XO Communications
Sr. Manager - IP Operations
Desk - 314-787-7826
Cell - 314.486-9057
-----Original Message-----
From: Jake Mertel [mailto:]
Sent: Tuesday, March 10, 2009 11:34 AM
To: John Martinez;
Subject: RE: XO peering.
We had a number of issues in the Seattle area this morning, seemed to be
isolated to traffic transiting via Level 3. We were forced to turn off
the connection, and it's still disabled until we get an update from XO.
-- Regards, Jake Mertel Nobis Technology Group, L.L.C. Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417 Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701 -----Original Message----- From: John Martinez [mailto:] Sent: Tuesday, March 10, 2009 11:23 AM To: Subject: Re: XO peering. We saw an issue with Level 3 hand off to XO in Chicago. Stefan Molnar wrote: > > There was a peering issue in San Jose with XO, that impacted our > operations this morning. But looks like a side effect is after the hand > off to NTT. > > Anyone who has an XO link can reach areas insdie NTT? > > As an example our route to Salesforce /21 is via NTT and it is not happy > right now. > > Thanks, > Stefan >
|
|
|