Level 3 network having problems?

*songdog* · 10-06-2003, 02:14 AM

My net access is miserable again.

I ran traceroutes to www.verizonwireless.com and www.dslreports.com and it appears to me that all the hops on or after parts of Level 3's network in California are timing out.

Can anyone confirm or add anything?

*sheila* · 10-06-2003, 02:19 AM

If you are on Verizon's California network, I have not been able to do successful traceroutes past the verizon/bbnplanet to Level3 router for over a month now. I get four hops and it dies.

I've talked to other Verizon customers in the Verizon newsgroup's and this seems to be common. Although Verizon support has disavowed any knowledge of it, common guess seems to be that Verizon is filtering ICMP packets at their borders, causing most traceroutes to fail. Mine consistently go four hops and die.

If you can traceroute with some other kind of packet, such as UDP or SYN you may have different results.

Anyhow, not sure if this is what your problem is, but thought that it *may* be, so thought I'd share my frustration. I spent many, many hours on hold to come to this conclusion.

*songdog* · 10-06-2003, 02:27 AM

My ISP is Comcast (formerly AT&T Broadband). My interest in Verizon is with the cell phone division's web site, not their land line stuff. And my traceroute to dslreports.com was also problematic. So I think the problem I'm seeing is more related to Level 3's network near San Diego.

See below:

Code:

Tracing route to www.verizonwireless.com [162.115.163.100]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    10 ms    10 ms    10 ms  12.x.x.x
  3    10 ms    10 ms    10 ms  12.x.x.x
  4    10 ms    10 ms    20 ms  12.x.x.x
  5    10 ms    10 ms    10 ms  12.x.x.x
  6    10 ms    10 ms    11 ms  xxx.dvmco.ip.att.net [12.x.x.x]
  7    10 ms    10 ms    10 ms  gbr3-p70.dvmco.ip.att.net [12.122.5.17]
  8    30 ms    40 ms    50 ms  tbr2-p013301.sffca.ip.att.net [12.122.12.133]
  9    30 ms    30 ms    40 ms  ggr2-p390.sffca.ip.att.net [12.123.13.194]
 10    30 ms    40 ms    40 ms  so-1-1-0.edge1.SanJose1.Level3.net [209.0.227.29]
 11    30 ms    40 ms    30 ms  so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137]
 12    50 ms    40 ms    50 ms  so-0-1-0.mp2.SanDiego1.Level3.net [64.159.1.138]
 13    70 ms    40 ms    50 ms  gige11-1.hsipaccess2.SanDiego1.Level3.net [64.159.1.62]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    10 ms    10 ms    10 ms  12.x.x.x
  3    10 ms    10 ms    10 ms  12.x.x.x
  4   <10 ms    10 ms    10 ms  12.x.x.x
  5    20 ms    10 ms    10 ms  12.x.x.x
  6    10 ms    10 ms     *     xxx.dvmco.ip.att.net [12.x.x.x]
  7    10 ms    20 ms    10 ms  gbr3-p80.dvmco.ip.att.net [12.122.5.25]
  8    40 ms    30 ms    40 ms  tbr2-p013801.sffca.ip.att.net [12.122.12.129]
  9    40 ms    30 ms     *     ggr1-p370.sffca.ip.att.net [12.123.13.69]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.