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]

[LarJak]

Here is the latest Trace Route, just wish it stayed this consistant throughout the day.

12/20/2009 7:45AM EST
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 6 ms 7 ms L100.PHLAPA-VFTTP-76.verizon-gni.net [98.111.146.1]
3 6 ms 7 ms 6 ms G0-0-776.PHLAPA-LCR-07.verizon-gni.net [130.81.107.188]
4 * * * Request timed out.
5 15 ms 12 ms 56 ms so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.17.3]
6 64 ms 53 ms 52 ms so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
7 51 ms 52 ms 51 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 53 ms 51 ms 51 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 52 ms 51 ms 51 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 53 ms 53 ms 51 ms 206.46.228.130
11 51 ms 54 ms 94 ms 206.46.232.39

[VstevoV]

Im having the same latency problems. I have done most of the fixes that are posted online about high pings and conflicts with Windows 7 with no resolution. This problem has started for me about 2 weeks ago out of no where. I live near Tampa Florida and when I use speedtest.net my down/up load speeds are OK, but my pings are unstable and when I ping out to the west coast they get very high and jumpy. My main concern is that I play wow and Im getting high latency. Before this problem I was getting right around 100 latency. Now I'm lucky to stay below 300.  I spoke with Verizon csr and they have no clue and say that everything is fine on there end. So before I do anything else to my PC and or router I need some opinions and possible directions on how to correct my problem. At the moment I'm running Windows 7 64. My router Verizon provided is a Westell A90-9100EM15. Below is a traceroute to the battlenet servers. Please help!

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

  1     4 ms     2 ms     1 ms  myrouter.home [192.168.1.1]
  2     4 ms     4 ms     4 ms  L100.TAMPFL-VFTTP-103.verizon-gni.net [96.243.230.1]
  3    14 ms    12 ms    11 ms  G10-2-1203.TAMPFL-LCR-02.verizon-gni.net [130.81.129.132]
  4    20 ms    16 ms    14 ms  so-7-2-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81.28.237]
  5    50 ms    35 ms    70 ms  ge-1-0-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81.17.48]
  6    33 ms    34 ms    33 ms  0.so-2-2-0.XT2.ATL5.ALTER.NET [152.63.86.73]
  7    43 ms    35 ms    37 ms  0.so-7-0-0.XT2.ATL4.ALTER.NET [152.63.86.109]
  8    33 ms    29 ms    32 ms  0.so-7-0-0.BR2.ATL4.ALTER.NET [152.63.81.149]
  9    30 ms    31 ms    32 ms  192.205.36.89
 10    85 ms    89 ms    82 ms  cr1.attga.ip.att.net [12.122.81.242]
 11    87 ms    84 ms    87 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 12    88 ms    83 ms    83 ms  cr2.la2ca.ip.att.net [12.122.28.178]
 13    83 ms    84 ms    84 ms  cr84.la2ca.ip.att.net [12.123.30.249]
 14    84 ms    84 ms    83 ms  gar5.la2ca.ip.att.net [12.122.129.25]
 15    85 ms    85 ms    84 ms  12.122.255.74
 16    85 ms   119 ms    83 ms  12.129.193.246
 17     *     12.129.211.36  reports: Destination net unreachable.

Trace complete.