[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
No route to verizon
- Subject: No route to verizon
- From: r.hyunseog at ieee.org (Alex H. Ryu)
- Date: Mon, 15 Dec 2008 13:55:31 -0600
- In-reply-to: <3FAEFF57159841B89B73F98DAF9F96D6@stupidcomp>
- References: <4FAF11268A404B368385EB3E4E297A5F@stupidcomp> <[email protected]> <3FAEFF57159841B89B73F98DAF9F96D6@stupidcomp>
It may be.
If the customer is BGP customer, and they have connectivity problem,
your traffic will flow into Verizon since Verizon have supernet.
But within Verizon network, Verizon router doesn't have specific route
info to route into.
So you may see time-out as soon as it hit Verizon network.
Alex
Sharlon R. Carty wrote:
> Ok thanks everyone.
> I'll be contacting Verizon.
>
> I do not believe the issue lies with the customer not paying their bills.
>
> -----Original Message-----
> From: Justin M. Streiner [mailto:streiner at cluebyfour.org]
> Sent: Monday, December 15, 2008 3:21 PM
> To: nanog at nanog.org
> Subject: Re: No route to verizon
>
> On Mon, 15 Dec 2008, Sharlon R. Carty wrote:
>
>
>> This is my first post.
>>
>> Can anyone provide some info or Verizon why there is no connectivity to
>> Verizon CA(Verizon Business UUNETCA8-A)?
>> Can not reach the following net range: 66.48.66.160 - 66.48.66.175
>>
>
> Your best bet might be to call Verizon directly, as a range this small is
> not likely to be seen in the global routing table as a free-standing
> route. I see 66.48.0.0/16 from my transit providers, originated from
> AS701, which is what I'd expect to see.
>
> Beyond that, your post doesn't contain enough information to do much more
> troubleshooting.
>
> jms
>
>
>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r_hyunseog.vcf
Type: text/x-vcard
Size: 360 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20081215/e8ceeaa7/attachment.vcf>