Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you switch and bring your phone.

Verizon peer (Level3) routing gone awry

Reply
waffleiron
Contributor
Contributor
Posts: 2
Registered: ‎02-05-2011

Verizon peer (Level3) routing gone awry

Message 1 of 4
(2,589 Views)

In Boston, going to a Comcast Business IP. Here's a part of the traceroute.

 

Verizon FIOS handing to ALterNet who then hands to Level 3 and sends it to San Jose, giving us an RTT 6 times greater than it should be. Started potentially about 7-10 days ago.

 

Anybody know who and how to contact somebody at Verizon to get them to have the routing optimized again. Frontline support can't escalate.

 

  1     1 ms     1 ms     1 ms  192.168.2.1
  2     2 ms     1 ms     2 ms  192.168.1.1
  3     8 ms     9 ms     8 ms  L100.BSTNMA-VFTTP-72.verizon-gni.net [96.237.177
.1]
  4     9 ms     8 ms     6 ms  G11-0-1-772.BSTNMA-LCR-07.verizon-gni.net [130.8
1.96.114]
  5     9 ms     7 ms     9 ms  so-0-3-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.2
9.252]
  6    19 ms    19 ms    19 ms  so-9-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
.19.70]
  7    16 ms    16 ms    19 ms  0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41]
  8    19 ms    15 ms    19 ms  0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
  9    17 ms    19 ms    19 ms  te-7-1-0.edge2.NewYork2.level3.net [4.68.127.21]

 10    15 ms    16 ms    19 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
 11    18 ms    19 ms    19 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 12    93 ms    89 ms    88 ms  ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
 13    88 ms    88 ms    91 ms  ae-84-84.csw3.SanJose1.Level3.net [4.69.134.250]

 14    85 ms    86 ms    86 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]

 15    90 ms    91 ms    91 ms  COMCAST-IP.edge1.SanJose1.Level3.net [4.79.43.13
8]
 16   109 ms   109 ms   108 ms  pos-0-13-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.85.133]
 17    99 ms   102 ms   100 ms  pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.117]
 18   106 ms   109 ms   106 ms  pos-2-15-0-0-ar01.woburn.ma.boston.comcast.net [
68.86.95.26]
 19   107 ms   107 ms   109 ms  po-63-ur02.lowell.ma.boston.comcast.net [68.85.6
9.78]
 20   109 ms   109 ms   108 ms  68.85.184.70

3 REPLIES 3
Shamika_VZ
Employee Emeritus Employee Emeritus
Employee Emeritus
Posts: 447
Registered: ‎01-02-2011

Re: Verizon peer (Level3) routing gone awry

Message 2 of 4
(2,484 Views)
Hello wafflerion,

We would like to take a look into this issue. I have sent you a private message, please respond when you have a moment.

Thanks,

Shamika_VZ

Verizon Support


Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

JiveTurkey
Nickel Contributor
Nickel Contributor
Posts: 44
Registered: ‎01-27-2010

Re: Verizon peer (Level3) routing gone awry

Message 3 of 4
(2,471 Views)

@waffleiron wrote:

In Boston, going to a Comcast Business IP. Here's a part of the traceroute.

 

Verizon FIOS handing to ALterNet who then hands to Level 3 and sends it to San Jose, giving us an RTT 6 times greater than it should be. Started potentially about 7-10 days ago.

 

Anybody know who and how to contact somebody at Verizon to get them to have the routing optimized again. Frontline support can't escalate.

 

  1     1 ms     1 ms     1 ms  192.168.2.1
  2     2 ms     1 ms     2 ms  192.168.1.1
  3     8 ms     9 ms     8 ms  L100.BSTNMA-VFTTP-72.verizon-gni.net [96.237.177
.1]
  4     9 ms     8 ms     6 ms  G11-0-1-772.BSTNMA-LCR-07.verizon-gni.net [130.8
1.96.114]
  5     9 ms     7 ms     9 ms  so-0-3-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.2
9.252]
  6    19 ms    19 ms    19 ms  so-9-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
.19.70]
  7    16 ms    16 ms    19 ms  0.so-0-0-0.XL3.NYC4.ALTER.NET [152.63.1.41]
  8    19 ms    15 ms    19 ms  0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
  9    17 ms    19 ms    19 ms  te-7-1-0.edge2.NewYork2.level3.net [4.68.127.21]

 10    15 ms    16 ms    19 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
 11    18 ms    19 ms    19 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 12    93 ms    89 ms    88 ms  ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
 13    88 ms    88 ms    91 ms  ae-84-84.csw3.SanJose1.Level3.net [4.69.134.250]

 14    85 ms    86 ms    86 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]

 15    90 ms    91 ms    91 ms  COMCAST-IP.edge1.SanJose1.Level3.net [4.79.43.13
8]
 16   109 ms   109 ms   108 ms  pos-0-13-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.85.133]
 17    99 ms   102 ms   100 ms  pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.117]
 18   106 ms   109 ms   106 ms  pos-2-15-0-0-ar01.woburn.ma.boston.comcast.net [
68.86.95.26]
 19   107 ms   107 ms   109 ms  po-63-ur02.lowell.ma.boston.comcast.net [68.85.6
9.78]
 20   109 ms   109 ms   108 ms  68.85.184.70


Seems to be me it's not so much Level3 as it is Comcast's Failtastic network.  Agreed, there's some latency in three Level3 hops, but nothing as bad as the 100ms+ on the final hops.

waffleiron
Contributor
Contributor
Posts: 2
Registered: ‎02-05-2011

Re: Verizon peer (Level3) routing gone awry

Message 4 of 4
(2,435 Views)

..sure got your email

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Have a spare Fios-G1100?Learn how to bridge it into your network
Get Started


Covid19

Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.
Modal Dialogue Title