[147496] in North American Network Operators' Group
RE: Verizon[AS 19262] connectivity issues to AS7393
daemon@ATHENA.MIT.EDU (cody@killsudo.info)
Mon Dec 12 13:36:18 2011
In-Reply-To: <483E6B0272B0284BA86D7596C40D29F901212A80D5A0@PUR-EXCH07.ox.com>
Date: Mon, 12 Dec 2011 12:34:22 -0600
From: cody@killsudo.info
To: "Matthew Huff" <mhuff@ox.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
The client just contacted us again to say that their issue has been
resolved. We are still waiting on a updated trace-route to see what has
changed.
Regards
Cody
> Not from Verizon, but Verizon's been having routing problems all weekend,
> getting much worse yesterday. The nexus may be in the Verizon / Level 3
> handoff, but it may be changing as Verizon routes around the issues.
>
>
> ----
> Matthew Huff | 1 Manhattanville Rd
> Director of Operations | Purchase, NY 10577
> OTA Management LLC | Phone: 914-460-4039
> aim: matthewbhuff | Fax: 914-460-4139
>
>
>> -----Original Message-----
>> From: cody@killsudo.info [mailto:cody@killsudo.info]
>> Sent: Monday, December 12, 2011 1:08 PM
>> To: nanog@nanog.org
>> Subject: Verizon[AS 19262] connectivity issues to AS7393
>>
>> We have a client that is complaining of connectivity issues and his
>> trace-routes are stopping inside Verizon's network.
>>
>> 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
>> 2 5 ms 4 ms 4 ms L100.NYCMNY-VFTTP-151.verizon-gni.net [98.116.13 4.1]
>> 3 8 ms 7 ms 7 ms G11-0-0-1251.NYCMNY-LCR-12.verizon-gni.net [130.
>> 81.139.32]
>> 4 * * * Request timed out.
>> 5 * * * Request timed out.
>>
>> We have no issues reaching 98.116.134.1 from any of our providers. I
>> asked the client to contact Verizon and Verizon tech's are responding
>> that the issue is not Verizon.
>>
>> Any chance someone from Verizon could contact me so we can find the
>> real problem?
>>
>> Thanks
>>
>> Cody
>>
>
>
