Re: XO Peering Question..

I am seeing a MED of 3 from XO. Josh > On Jan 8, 2015, at 11:31 AM, > wrote: > > Hey All, > Quick question for those of you who may be pulling a partial or full table > from XO.. > > Can you tell me your MED/Weight on the routes from them? > > Please and Thank you. > > > > > [cid:62CA

XO Peering Question..

Hey All, Quick question for those of you who may be pulling a partial or full table from XO.. Can you tell me your MED/Weight on the routes from them? Please and Thank you. [cid:62CA825B-35AD-469A-B224-9BA199DC5662]GREGORY S CROFT Information Security Engineer gcr...@unitedshore.com

AT&T - XO Peering (AS7018 and AS2828)

Hi, Please could someone from ATT and/or XO contact me off list to discuss some issues we've been seeing on a link between AS7018 and AS2828. Thanks Pat -- --- Patrick Sumby Director of Global Engineering Sohonet

RE: XO peering.

ic Cc: Jake Mertel; John Martinez; nanog@nanog.org Subject: RE: XO peering. On Tue, 2009-03-10 at 11:41 -0500, Mort, Eric wrote: > 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 see

RE: XO peering.

gt; Eric J. Mort > XO Communications > Sr. Manager - IP Operations > Desk - 314-787-7826 > Cell - 314.486-9057 > em...@xo.com > > > -Original Message- > From: Jake Mertel [mailto:j...@nobistech.net] > Sent: Tuesday, March 10, 2009 11:34 AM > To: John Martinez; na

Re: XO peering.

Our office has XO, and sent an email out complainging about Salesforce.In Chicago. --chris Stefan Molnar wrote: It just cleared up for me. Nice to have a call center complain constantly. Thanks On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote: On Tue, Mar 10, 2009 at 9:35 PM, Stefa

Re: XO peering.

It just cleared up for me. Nice to have a call center complain constantly. Thanks On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote: On Tue, Mar 10, 2009 at 9:35 PM, Stefan Molnar wrote: There was a peering issue in San Jose with XO, that impacted our operations this morning.  But looks

RE: XO peering.

- 314.486-9057 em...@xo.com -Original Message- From: Jake Mertel [mailto:j...@nobistech.net] Sent: Tuesday, March 10, 2009 11:34 AM To: John Martinez; nanog@nanog.org Subject: RE: XO peering. We had a number of issues in the Seattle area this morning, seemed to be isolated to traffic transiting

Re: XO peering.

IL 61701 > > > -Original Message- > From: John Martinez [mailto:jmarti...@zero11.com] > Sent: Tuesday, March 10, 2009 11:23 AM > To: nanog@nanog.org > Subject: Re: XO peering. > > We saw an issue with Level 3 hand off to XO in Chicago. > > Stefan Molnar wrote: &g

RE: XO peering.

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:jmarti...@zero11.com] Sent: Tuesday, March 10, 2009 11:23 AM To: nanog@nanog.org Subject: Re: XO pe

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? >

Re: XO peering.

On Tue, Mar 10, 2009 at 9:35 PM, 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 Sales

XO peering.

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. T