[112599] in North American Network Operators' Group
Re: XO peering.
daemon@ATHENA.MIT.EDU (Stefan Molnar)
Tue Mar 10 12:44:22 2009
Date: Tue, 10 Mar 2009 08:42:21 -0800 (PST)
From: Stefan Molnar <stefan@csudsu.com>
To: Suresh Ramasubramanian <ops.lists@gmail.com>
In-Reply-To: <bb0e440a0903100918q4eaa35a5x2a04f6a73551fc36@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--0-1859668437-1236703341=:18723
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
It just cleared up for me. Nice to have a call center complain=20
constantly.
Thanks
On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote:
> On Tue, Mar 10, 2009 at 9:35 PM, Stefan Molnar <stefan@csudsu.com> wrote:
>> There was a peering issue in San Jose with XO, that impacted our operati=
ons
>> this morning. =C2=A0But looks like a side effect is after the hand off t=
o 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.
>
> This is from a host in XO AS2828
>
> I can reach, for example, www.verio.net 204.202.20.3 / AS2914
> NTT-COMMUNICATIONS-2914 just fine.
>
> www.salesforce.com is also reachable, through NTT
>
> --=20
> Suresh Ramasubramanian (ops.lists@gmail.com)
>
>
--0-1859668437-1236703341=:18723--
