Hello,
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
--sharlon
Sharlon R. Carty wrote:
Hello,
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
11. ae-4-99.edge2.NewYork2.Level 0.0%
12. mci-level3-xe.newyork2.Level 0.0%
13. 0.xe-5-0-3.XL4.NYC4.ALTER.NE 0.0%
14. ??? 100.0
It gets into Verizons network and as far as New York. Maybe a fault
between Verizon and the customer ? After all, Alter.net is Verizon.
/Martin
Sharlon R. Carty wrote:
Hello,
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--sharlon
That network is assigned to a customer:
Tremor Technology Group Inc TREMORUU2 (NET-66-48-66-160-1)
66.48.66.160 - 66.48.66.175
You would have to contact them. Lots of possibilities: line failure,
equipment failure, or they didn't pay their bill.
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
Ok thanks everyone.
I'll be contacting Verizon.
I do not believe the issue lies with the customer not paying their bills.
My traceroute also ends with ALTER.NET:
traceroute to 66.48.66.160 (66.48.66.160), 30 hops max, 40 byte packets
...
7 los-edge-01.inet.qwest.net (63.147.28.181) 1.701 ms 1.870 ms 1.734 ms
8 los-core-01.inet.qwest.net (205.171.32.33) 1.755 ms 1.670 ms 1.823 ms
9 lap-brdr-01.inet.qwest.net (205.171.32.10) 1.722 ms 2.082 ms 2.676 ms
10 0.so-4-3-0.BR1.LAX7.ALTER.NET (204.255.169.193) 2.094 ms 2.046 ms 1.720 ms
matthew black
e-mail postmaster
california state university, long beach
Matthew Black wrote:
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: