High latency and poor speed tests lately

[MisterJefferson]

For the past 4-5 days, I've been working with various Verizon techs to resolve a high latency/slow Internet problem.  Their ultimate solution was that they have no idea why it's doing this, and since I can reach a few websites at full speed and their line tests show I'm operating at full provisioning, it's not their problem.  "We can't control traffic outside of our networks."  Well, my results are also showing problems with the Verizon servers, so I would think they should be more concerned.  Most websites, however, exhibit the problem.  So I'm stuck, looking for a better answer than "go away."  Maybe some of you are experiencing a similar problem with latency or sporadic speeds?

My provisioning is 20M/5M.  I'm in the L.A. area. (In the traceroutes below, I masked Hop 2 for privacy.)

I've experienced this problem with 2 computers (1 desktop, 1 laptop), both using Ethernet ports; one test using wireless on the laptop.  I've plugged the router directly into the ONT coax to eliminate my house wiring as the culprit.  Westell 9100EM router.

A few websites seem okay, and speedtest.net results always show provisioning at full speed to the L.A. server, but the problem persists when using the non-L.A. server.  With speakeasy.net, even the L.A. server exhibits the problem.  The latency gets worse as the night goes on, sometimes over 1000ms for some traceroute hops.  In the morning, it seems to be back to normal.

Thanks for any help....

Jeff

Some examples...

In the past 2 mornings, I've had good results:

Speed Test (speakeasy.net, Los Angeles): ~ 19798K/4581K

Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping

Speed Test (speedtest.net, Dallas): ~ 19.81M/4.37M, 49ms ping

Tracing route to www.l.google.com [74.125.19.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     8 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxxxx.verizon-gni.net [173.55.xxx.xxx]
  3     8 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    53 ms    11 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    13 ms    12 ms    12 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6    12 ms    11 ms    13 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
  7     9 ms    12 ms    42 ms  xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
  8    14 ms    12 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  9    21 ms    34 ms    35 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    26 ms    19 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11    21 ms    22 ms    22 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12    23 ms    22 ms    23 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    29 ms    34 ms    22 ms  209.85.251.98
 14    20 ms    23 ms    19 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

In the past 4-5 evenings, I've had poor results:

Speed Test (speakeasy.net, Los Angeles): ~ 2441K/194K

Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping

Speed Test (speedtest.net, Dallas): ~ 8.28M/1.22M, 49ms ping

Tracing route to www.l.google.com [74.125.19.105]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   531 ms   502 ms   514 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   519 ms   506 ms   530 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   563 ms   564 ms   553 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6   577 ms   544 ms   524 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  7   477 ms   469 ms   459 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    11 ms    17 ms    19 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
  9   515 ms   559 ms   536 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    20 ms    19 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11   524 ms   499 ms   544 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12   490 ms   479 ms   464 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    24 ms    22 ms    32 ms  209.85.251.98
 14    23 ms    22 ms   489 ms  nuq04s01-in-f105.1e100.net [74.125.19.105]

[chernabog]

Similar problem for me too. I just had FIOS installed and I'm getting excellend download/upload but terrible ping. My results are as follows:

Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     4 ms     4 ms     5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3     9 ms     9 ms     8 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4     9 ms     9 ms     8 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    11 ms    10 ms    10 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6    11 ms    10 ms    11 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  7    10 ms     9 ms    10 ms  192.205.35.161
  8    66 ms    65 ms    66 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9    66 ms    65 ms    65 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 10   104 ms    97 ms   131 ms  cr1.attga.ip.att.net [12.122.28.173]
 11    65 ms    64 ms    64 ms  12.123.22.5
 12   135 ms   124 ms   135 ms  12.88.97.6
 13   110 ms   199 ms    92 ms  72.14.233.54
 14    66 ms   119 ms   119 ms  72.14.239.127
 15   152 ms   167 ms   162 ms  209.85.255.194
 16   120 ms   107 ms   111 ms  gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

Granted these results are also 4x better than they were 10 min ago. I was getting most pings in the 400 range but a couple were over 600! What's going on Verizon?

[spacedebris]

MisterJefferson, your problem looks to be with hop #3. That is a Verizon router just after the gateway router for you. This will need to be addressed by a Verizon Network technician. Your hops to your router and your hop to the gateway look fine. Verizon will need to reboot that second router or re-route your hops.

Chernabog, yours is more difficult, you dont have any obvious big issue. However you do have a moderate jump at hop number 8. this is off the verizon network and is out on the internet. on one of the ATT routers. Unlikely you are going to be able to do anything about this. And as it is off the Verizon network, there would be nothing verizon could do about it either. Usually though, if it is a router needing rebooting, it will generally self correct after a few days. Or you could be unlucky enough to be going through a system that is overloaded or just plain old. This can be frustraiting. I myself play a lot of online games and if the server is in Washington DC (I'm in California) one of the hops I have to go through is in kentucky with sprintlink and their routers constantly give me a 500ms ping and I havent been able to get it corrected in over 4 years. Something we sometimes have to live with when it is out of our control.

[spacedebris]

MisterJefferson I also noticed that the Hop number 3 changed between your good results and your bad results.

On the good it was

3     8 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]

On the bad it was

3   531 ms   502 ms   514 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

So it looks like when they switch you to that LCR-12 you have an issue. I'd contact Verizon Tech support, tell them that you are having a network issue and have them contact a network technition and have them look at that IP 130.81.140.162. It likely needs to be rebooted, reset, or replaced.

[nestacio]

Well, I'm glad it's not just me -- also getting terrible ping the last week or so. I used to see pings in the ~20ms range throughout the entire day, but now I am experiencing the same behavior: good ping in the morning, and successively worse and worse values throughout the day. Sometimes going higher than ~900ms in the evening. I'm also in Los Angeles.

Here are the results of my traceroute:

traceroute: Warning: www.l.google.com has multiple addresses; using 74.125.19.105

traceroute to www.l.google.com (74.125.19.105), 64 hops max, 52 byte packets

 1  myrouter (192.168.1.1)  0.634 ms  0.331 ms  0.478 ms

 2  l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1)  7.985 ms  6.892 ms  7.483 ms

 3  g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162)  210.618 ms  219.254 ms  202.147 ms

 4  so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246)  205.109 ms  194.284 ms  210.358 ms

 5  0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125)  259.831 ms  201.562 ms  207.601 ms

 6  0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153)  15.467 ms  24.865 ms  27.213 ms

 7  xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129)  227.344 ms  214.266 ms  198.670 ms

 8  ae-93-90.ebr3.losangeles1.level3.net (4.69.144.244)  11.946 ms

    ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116)  214.004 ms

    ae-83-80.ebr3.losangeles1.level3.net (4.69.144.180)  207.058 ms

 9  ae-2.ebr3.sanjose1.level3.net (4.69.132.9)  217.253 ms  228.709 ms  245.033 ms

10  ae-73-73.csw2.sanjose1.level3.net (4.69.134.230)  27.427 ms  34.813 ms  36.956 ms

11  ae-2-79.edge1.sanjose1.level3.net (4.68.18.78)  250.562 ms  239.283 ms  232.337 ms

12  google-inc.edge1.sanjose1.level3.net (4.79.43.146)  232.339 ms  211.787 ms  235.336 ms

13  209.85.251.98 (209.85.251.98)  252.116 ms  271.735 ms  229.820 ms

14  nuq04s01-in-f105.1e100.net (74.125.19.105)  19.967 ms  21.635 ms  25.225 ms

So hop #3 is the start of my woes; it is the EXACT switch/router location as MisterJefferson: 130.81.140.162.

What can we do about this? I'm assuming (perhaps wrongly) that Verizon is not equipped to troubleshoot this issue over the phone; I don't have a lot of confidence, based on other support calls to various services, that the customer support person has a script to deal with this type of repair request -- since it's not a repair that needs to be done to customer-owned equipment.

It's reassuring that the issue can be duplicated by someone other than myself. I'm hoping to resolve this since we have otherwise been really happy with the quality of the FIOS connection, which is amazing.

N

[spacedebris]

Yup, you have the same problem with the same router. Once one of you get to Verizon tech support and speak to a network technician, then once the techs are able to get that router either rebooted replaced then both your issues will likely be corrected.  Your right that one of the front line agents that you get when you call, will not be able to help you. They will need to get this to one of the network technicians. Hopefully, you'll get an agent that knows to send network related trouble up the line.

 3  g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162) 21 0.618 ms  219.254 ms  202.147 ms

maybe one of the employees here on the board can take it to one of their network techs for a look.

[VZ_Brett]

MisterJefferson .. If your still having a latency issue please direct message me your info so I can get this issue resolved thanks Brett

[nestacio]

Great to see you here Brett - MisterJefferson and I have the same issue; I took a look at the new traceroute info (as of this morning 10.23.09) and there is an improvement in the routing:

traceroute: Warning: www.l.google.com has multiple addresses; using 74.125.19.104

traceroute to www.l.google.com (74.125.19.104), 64 hops max, 52 byte packets

 1  myrouter (192.168.1.1)  0.564 ms  0.350 ms  0.488 ms

 2  l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1)  7.978 ms  6.874 ms  19.982 ms

 3  g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122)  10.477 ms  8.849 ms  10.232 ms

 4  so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.29.244)  12.486 ms  12.092 ms  12.217 ms

 5  0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133)  12.218 ms  11.845 ms  12.466 ms

 6  0.ge-7-0-0.br2.lax15.alter.net (152.63.116.157)  99.945 ms

    0.ge-6-0-0.br2.lax15.alter.net (152.63.116.149)  107.061 ms  122.270 ms

 7  xe-11-0-0.edge1.sanjose3.level3.net (4.68.111.249)  12.437 ms

    xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129)  116.309 ms

    xe-11-0-0.edge1.sanjose3.level3.net (4.68.111.249)  11.872 ms

 8  ae-63-60.ebr3.losangeles1.level3.net (4.69.144.52)  14.479 ms  17.096 ms

    ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116)  94.683 ms

 9  ae-2.ebr3.sanjose1.level3.net (4.69.132.9)  109.825 ms  111.811 ms  112.170 ms

10  ae-83-83.csw3.sanjose1.level3.net (4.69.134.234)  112.451 ms  106.826 ms  107.922 ms

11  ae-3-89.edge1.sanjose1.level3.net (4.68.18.142)  22.468 ms  21.347 ms  22.722 ms

12  google-inc.edge1.sanjose1.level3.net (4.79.43.146)  122.187 ms  117.049 ms  137.157 ms

13  209.85.251.98 (209.85.251.98)  127.426 ms  122.161 ms  149.677 ms

14  nuq04s01-in-f104.1e100.net (74.125.19.104)  145.379 ms  144.021 ms  127.655 ms

The ping is still hovering around ~130ms so the problematic equipment appears to be at hop #6 and #7 which do not seem to belong to Verizon; can the route be tweaked further?

Thanks for working on this,

nestacio

[spacedebris]

Yeah, your hop 3 is back to router #11 again. same as MisterJefferson does in the morning. In the morning you two go through #11 but in the afternoon, you go through router #12 and #12 is the problem.

unfortunatly each hop determines where the next one will go. so hop 5 determins hop 6 and so forth. Now your good on the verizon system and good on the first hop out of the verizon network. Verizon will not be able to do anything to avoid hop 6 now. Now it is a problem with the alter.net systems. This is the problem I run into, bad hops beyond Verizon. Unfortunatly there is likely nothing that can be done, short of contacting alter.net that is and praying that they give a **bleep** about someone other than their own customers. like I said in an earlier post. I've been having the same kind of problem with some routers run by sprintlink and it took me nearly 6 months to get ahold of them and they basically told me to take a flying leap since I was not their customer.

[nestacio]

Ok, Spacedebris is correct, the problem is NOT resolved, LCR-12 at 130.81.140.162 is NOTbeing re-routed, both MisterJefferson and I are being switched over from LCR-11 to LCR-12 in the evenings here in Los Angeles.

This is a problem.

Here is the traceroute as of 5:30pm Friday 10.23.09:

.......

Tracing route to www.l.google.com [74.125.19.103]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]

  2     8 ms     6 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3   458 ms   444 ms   459 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4   448 ms   409 ms   430 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5   416 ms   412 ms   421 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

  6    10 ms     9 ms    10 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

  7   414 ms   406 ms   419 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

  8   471 ms   494 ms   509 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

  9   513 ms   502 ms   525 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

 10   531 ms   534 ms   531 ms  ae-93-93.csw4.SanJose1.Level3.net [4.69.134.238]

 11   514 ms   454 ms   449 ms  ae-4-99.edge1.SanJose1.Level3.net [4.68.18.206]

 12   453 ms   437 ms   454 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

 13   440 ms   447 ms   454 ms  209.85.251.98

 14   492 ms   474 ms   446 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]

Trace complete.

.......

Brett / Verizon: can you fix this equipment? A 458ms ping is unacceptable. I will look around the customer service pages to see if I can open a ticket to get this resolved. If not, I will try and escalate to a manager.

In addition, alter.net is owned by Verizon Business; see prior posts. LCR-11 works in the morning until it hits alter.net. There is a breakdown in the equipment when it hits that equipment as well. Verizon, wth?

Neil

[chernabog]

1. http://img190.imageshack.us/img190/3411/latencyw.jpg 

2.  [edit]

3. http://img43.imageshack.us/img43/8881/vzdiag.jpg

4. http://img251.imageshack.us/img251/1575/tracert.jpg

Four images for your consideration. All are screenshots taken within a 10 minute timeframe. These screenshots show that in no way is my issue unique to one ATT server that I will hardly ever connect to. This is an issue that is affecting everything I am trying to connect to.

I tried to use the FIOS speed optimizer which was unsuccessful in doing it's job. I tried to run it on multiple computers with multiple OS's on both wired and wireless connections. ALL failed. I'm thinking that my router or the lines that were installed in my house or neighborhood are [edit] . I'm not going to pay for a service that I'm not receiving.

[Torched]

I believe i'm suffering from the same problem:

Tracing route to www.l.google.com [74.125.19.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3   561 ms   537 ms   559 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
  4   595 ms   571 ms   595 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  5   578 ms   594 ms   604 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    12 ms    11 ms    12 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7    11 ms    12 ms    14 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
  8    15 ms    17 ms    17 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1
16]
  9    21 ms    23 ms    29 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10   671 ms   682 ms   701 ms  ae-73-73.csw2.SanJose1.Level3.net [4.69.134.230]

 11   662 ms   729 ms   724 ms  ae-2-79.edge1.SanJose1.Level3.net [4.68.18.78]
 12   643 ms   656 ms   630 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.14
6]
 13    21 ms    21 ms    30 ms  209.85.251.98
 14    20 ms    19 ms    21 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

This seems to also be impact my teleworking ability. My companies data center is in Irvine, Ca and i'm getting VERY high latency to our corporate firewall. The hops jump inside alter.net's network which is Verizon business's network.

Please fix this ASAP, we have other teleworkers in the southern california area who have FIOS and are impacted by this.

[MisterJefferson]

I thought I'd post an update, since you guys have been helpful; I just sent Brett a more detailed response.  No, I'm not fixed yet.  I had a Verizon tech come out to the house today and swapped out the ONT, but as I figured, it wouldn't fix it since my problem is further down the network chain. But apparently the field techs are only responsible for the signal to the central office, which he says looks fine.

The other day, one phone tech had me run traceroutes to "verizon.net" instead of google.com; this shows my problem is within the Verizon network before I even reach the Internet.  Consequently, I wrote a Perl script to run traceroutes every 5 minutes so I have 24/7 data to compare, if needed.  I'm also running PingPlotter.

Here's a traceroute from a few minutes ago (10/24/09, Saturday, 4:50P PDT):

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     7 ms     7 ms  xxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   862 ms   876 ms   859 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   848 ms   814 ms   797 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   831 ms   839 ms   809 ms  130.81.17.27
  6    46 ms    49 ms    47 ms  so-1-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.66]
  7    46 ms    47 ms    48 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    47 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9   856 ms   887 ms   882 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    47 ms    47 ms    47 ms  206.46.228.130
 11    53 ms    47 ms    47 ms  206.46.232.39

Trace complete.

I also have a PingPlotter chart from the past day or two. It shows that the net bogs down in the morning and gets progressively worse (up to about 1250ms latency) around 10-11pm, then tapers off until 2-3am.

PingPlot:  http://www.warmhaven.com/test/2009-10-24_1635.gif

The field tech said he'd forward some of my charts to his boss for a callback.  So I'm in a holding pattern.

Jeff

[Torched]

More information:

ping www.verizon.net

Pinging e3002.b.akamaiedge.net [96.6.252.79] with 32 bytes of data:
Reply from 96.6.252.79: bytes=32 time=703ms TTL=54
Reply from 96.6.252.79: bytes=32 time=663ms TTL=54
Reply from 96.6.252.79: bytes=32 time=696ms TTL=54
Reply from 96.6.252.79: bytes=32 time=663ms TTL=54

Ping statistics for 96.6.252.79:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 663ms, Maximum = 703ms, Average = 681ms

Tracing route to e3002.b.akamaiedge.net [96.6.252.79]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     7 ms     6 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3   760 ms   744 ms   797 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
  4   750 ms   723 ms   732 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  5   696 ms   729 ms   696 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    12 ms    11 ms    11 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7    43 ms    14 ms    11 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
  8    20 ms    17 ms    16 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.5
2]
  9    23 ms    19 ms    32 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    31 ms    19 ms    31 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]

 11    20 ms    19 ms    23 ms  ae-33-89.car3.SanJose1.Level3.net [4.68.18.133]

 12   618 ms   606 ms   594 ms  a96-6-252-79.deploy.akamaitechnologies.com [96.6
.252.79]

Trace complete.

Obviosly verizon.net is outsourced to Akamia but again, latency jumps up inside Verizon's network. Someone needs to get eyes on those hops to see what is wrong.

[Interwebs]

I have been having this problem too, except it has been a little over a week ( 1 week and 2 days, to be exact) since it has started happening. Using speedtest.net, I noticed that connecting, uploading, downloading, and the latency around Los Angeles (near my area) is working perfectly. However, as I try to connect to places around East of the United States, my latency becomes outrageous (500-700?!). The middle states work fine; it's just the states closer to the east coast. Also, my results after testing my connection to Europe appear to be a little bit higher than normal, although it is a far sight better than what I got in Eastern United States.

I really hope this problem gets fixed fast; I often have trouble and terrible lag in doing tasks online or in an online game I play (Soldierfont, IJJI), mostly in the Eastern U.S. servers. 😞

Also it appears that results get a tiny bit better in the mornings than compared to those at night. At around past 10:00 pm my connection is almost dead 😛 At least it was a relief that this wasn't my computers problem.

[Richard312]

Im having this same problem for a week  and I also live in Chino hills

My ping to the Philadelphia server is 888ms with a jitter of 68ms on pingtest.net. But when i ping the San Francisco server, its perfectly "normal" with around 20-30 ms.

http://www.pingtest.net/result/1765466.png

My friend who also has fios lives about 500ft from me and in Chino hills. He pings 126ms to the Philly serve in comparison to my 888.

This is my tracert to google.com

Tracing route to www.l.google.com [74.125.19.106]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms    14 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     9 ms     9 ms     8 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     9 ms     9 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     8 ms     9 ms     9 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6   795 ms   759 ms   817 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]

  7   786 ms    10 ms   854 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
  8    13 ms    17 ms   833 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1
16]
  9    24 ms    29 ms    24 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    21 ms    19 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]

 11    18 ms    19 ms    19 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]

 12    22 ms    17 ms    17 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.14
6]
 13   816 ms   800 ms   730 ms  209.85.251.98
 14    20 ms    26 ms    19 ms  nuq04s01-in-f106.1e100.net [74.125.19.106]

Whats strange is that my friend gets a very similar tracert with the high MS on certain hops. But his general internet speed is "fine"

Is there any fix to this yet? or _soon_

[Hairstylinstacy]

I have been having similar issues as well for the past 10 days. Also live in Chino Hills.

Taken at 9:00pm PST

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     5 ms     5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     8 ms     8 ms    10 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     8 ms     9 ms    10 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5    45 ms    45 ms    45 ms  so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81
.19.18]
  6    45 ms    52 ms    58 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.
81.20.157]
  7    45 ms    45 ms    45 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  8    45 ms    45 ms    46 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
  9  1154 ms  1146 ms  1155 ms  206.46.228.130
 10  1189 ms  1296 ms  1253 ms  206.46.232.39

Trace complete.

[jco88]

I also live in Chino Hills, CA. For two weeks now, Verizon FIOS connection SUCK! I called FIOS support and no one seems to know or admit there is a problem in the SoCal area.  Here's my trace route to LATimes.  It's so **bleep** slow across the board - google.com, youtube, espn, etc... I have a ticket opened and after the first callback, i haven't received any more updates or info on what's going on.

$ tracert latimes.com

Tracing route to latimes.com [144.142.224.43]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     6 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3  1147 ms  1224 ms  1205 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4  1146 ms  1228 ms  1228 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1227 ms  1228 ms  1229 ms  0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
  6  1226 ms  1228 ms  1228 ms  0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
  7  1191 ms  1067 ms  1025 ms  POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
  8    17 ms    17 ms    17 ms  internapGIGE-gw.customer.alter.net [157.130.236.110]
  9  1104 ms  1126 ms  1126 ms  border21.po1-20g-bbnet1.lax.pnap.net [216.52.255.38]
 10  1124 ms  1228 ms  1228 ms  tribune-1.border21.lax.pnap.net [216.52.220.154]
 11  1059 ms  1192 ms  1228 ms  secure.latimes.com [144.142.224.43]

[jco88]

From Chino Hills again. here's my traceroute to google.com.  Same network latency problem. I've been paying monthly for a high speed connection and i'm getting Dial-up speed for more than a week now !!!  What's the point of paying for FIBER if you get modem speed !!! and I'm not getting a response from Verizon. They kept on asking me to reset my router. I told them my friend who lives in the same city a few miles away has the same exact problem so I don't know how a router reset would work! Obviously it's something in the Verizon network.

$ tracert www.google.com

Tracing route to www.l.google.com [74.125.19.105]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     6 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3  1264 ms  1228 ms  1228 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4  1226 ms  1228 ms  1126 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1230 ms  1225 ms  1228 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    56 ms    60 ms    54 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  7  1094 ms  1228 ms  1228 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8  1209 ms  1126 ms  1234 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
  9  1203 ms  1228 ms  1228 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    59 ms    52 ms    54 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
 11    63 ms    59 ms    62 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
 12    63 ms    72 ms    72 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13  1363 ms  1228 ms  1228 ms  209.85.251.98
 14    57 ms    62 ms    54 ms  nuq04s01-in-f105.1e100.net [74.125.19.105]

Trace complete.

[Richard312]

Im getting different hops tonight in comparison to last night

C:\Users\pc>tracert www.google.com

Tracing route to www.l.google.com [74.125.19.103]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3   965 ms   972 ms  1007 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4  1012 ms  1040 ms  1003 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1026 ms  1021 ms  1006 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6     9 ms     9 ms     9 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

 7  1038 ms  1038 ms  1039 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    18 ms    12 ms    14 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
  9    22 ms    19 ms    19 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    17 ms    17 ms    25 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]

 11    53 ms    25 ms    19 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]

 12    17 ms    17 ms    19 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13  1089 ms  1055 ms  1010 ms  209.85.251.98
 14    18 ms    18 ms    19 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]

Trace complete.

[VZ_Brett]

All who are having latency issues please monitor & provied new trace routes. Per notes they are looking for an update to see if issue was corrected. Thanks all again we will continue on this issue untill resolved. Thanks Brett