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]

[MisterJefferson · Accepted solution]

It looks fixed on my end, so I hope this is a permanent thing.  My speed tests are back to normal, and I'm seeing much more reasonable latency.  Thanks, Brett, for following up.

- Jeff

Taken tonight, 10/30, 12:30am:

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     7 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3    12 ms    12 ms    12 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    12 ms    12 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    12 ms    12 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    49 ms    77 ms    64 ms  130.81.17.27
  7    49 ms    50 ms    49 ms  so-1-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.66]
  8    50 ms    50 ms    49 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9    49 ms    50 ms    49 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10    51 ms    49 ms    54 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    48 ms    49 ms    50 ms  206.46.228.130
 12    49 ms    50 ms    49 ms  206.46.232.39

Trace complete.

Taken tonight, 10/30, 12:40am:

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     7 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3     9 ms     9 ms    10 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4     8 ms    10 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    12 ms     9 ms    10 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6     8 ms    12 ms    10 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  7    12 ms    12 ms    12 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    13 ms    14 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  9    33 ms    34 ms    34 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    32 ms    17 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11    20 ms    22 ms    23 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12    19 ms    19 ms    19 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    29 ms    22 ms    32 ms  209.85.251.98
 14    18 ms    19 ms    19 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

Trace complete.

[Osler]

All seems to be running well here, too. Kudos to Brent--PM me your supervisor's phone number so I can send some feedback!

Tracing route to us.logon.battle.net [12.129.206.130]
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  L100.LSANCA-VFTTP-142.verizon-gni.net
  3    11 ms    12 ms    12 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    12 ms    16 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    13 ms    13 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    14 ms    14 ms    14 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    12 ms    11 ms    12 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  8    14 ms    14 ms    14 ms  192.205.35.161
  9    29 ms    12 ms    12 ms  cr1.la2ca.ip.att.net [12.123.30.6]
 10    32 ms    57 ms    35 ms  gar4.la2ca.ip.att.net [12.122.129.169]
 11    28 ms    34 ms    33 ms  12.122.255.70
 12    21 ms    16 ms    39 ms  12.129.193.254
 13     *     12.129.211.36  reports: Destination net unreachable.

Trace complete.

[VZ_Brett]

Excellent news guys! Keep an eye on it & let me know! Thanks again Brett

[weimdaddy]

Hello, Im part of the Group in Chino Hills having the latency issues...........I have good ping times but still slow on Download speeds from Speedtest.net. The Download im getting shows less than 1mb and 25mb on upload.

Browsing is extremely slow and was wondering if you have fixed some or all in my area?

[Hairstylinstacy]

Are you still having problems currently? I just ran another tracert and things are looking great. Can you trun a a tracert and post your results, that way the people here can try and identify the problem you are having(if it isn't the same as the rest of us)

Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     4 ms     5 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     7 ms     7 ms     6 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     8 ms     7 ms     6 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     9 ms     9 ms     8 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    19 ms    21 ms    21 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7    23 ms    23 ms    23 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8    23 ms    24 ms    23 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    24 ms    23 ms    24 ms  192.76.84.5
 10     *        *        *     Request timed out.

[weimdaddy]

Here are my Ping times for a trace route.............which are good but on a speed test from speedtest.net it shows me with a 1.2mb download and 22.1 mb upload. Something wrong with my line!

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\The WEIMDADDY>tracert www.verizon.com

Tracing route to a1280.g.akamai.net [65.200.11.154]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WEIMDADDY.home [192.168.1.1]
  2     3 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     6 ms     7 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     6 ms     7 ms     7 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     6 ms     7 ms     7 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6     6 ms     7 ms     7 ms  0.so-7-1-0.XL3.LAX15.ALTER.NET [152.63.1.226]
  7     8 ms     7 ms     9 ms  TenGigE0-6-1-0.GW4.LAX15.ALTER.NET [152.63.114.2
09]
  8    11 ms     9 ms     9 ms  a65.200.11.154.deploy.akamaitechnologies.com [65
.200.11.154]

Trace complete.

[dwoo]

5:25pm 11/5/2009 Chino Hills

lag is very bad

tracert to google.com and verizon.com as following:

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

  1     4 ms     2 ms     2 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2     5 ms     4 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     6 ms     5 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     5 ms     4 ms     4 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  5     8 ms   824 ms     6 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  6   853 ms   821 ms     6 ms  xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
  7    18 ms   812 ms   818 ms  ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
  8    16 ms    15 ms    17 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  9   925 ms   921 ms   818 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 10   831 ms   819 ms   818 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 11    17 ms    16 ms    15 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 12    21 ms    20 ms    15 ms  209.85.251.98
 13   858 ms   818 ms   819 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]

Trace complete.

C:\>tracert www.verizon.com

Tracing route to a1280.g.akamai.net [63.80.4.59]
over a maximum of 30 hops:

  1    25 ms    23 ms    27 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2     6 ms     4 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     6 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     8 ms     6 ms     5 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  5    18 ms    15 ms    16 ms  0.ge-7-1-0.XL3.SJC7.ALTER.NET [152.63.48.254]
  6   937 ms   919 ms   921 ms  TenGigE0-6-1-0.GW3.SJC7.ALTER.NET [152.63.50.25]
  7   856 ms   921 ms   921 ms  63.80.4.59

Trace complete.

[dwoo]

5:30pm

Looks like something bad back again (130.91.140.162)

C:\>tracert www.google.com

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

  1     2 ms     1 ms     1 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2   735 ms   716 ms   818 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   774 ms   782 ms   716 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   842 ms   819 ms   714 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     7 ms     5 ms     5 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  6   731 ms   716 ms   717 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7    10 ms    12 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  8    18 ms    17 ms    20 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  9   811 ms   818 ms   820 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 10   739 ms   819 ms   819 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 11    16 ms    14 ms    15 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 12    24 ms    17 ms    18 ms  209.85.251.98
 13   737 ms   793 ms   817 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

Trace complete.

C:\>tracert www.verizon.com

Tracing route to a1280.g.akamai.net [65.197.197.34]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2   797 ms   818 ms   820 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   739 ms   819 ms   818 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   840 ms   818 ms   819 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
  5   841 ms   716 ms   819 ms  0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
  6    14 ms     8 ms     7 ms  TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
  7    10 ms     6 ms     7 ms  a65.197.197.34.deploy.akamaitechnologies.com [65
.197.197.34]

Trace complete.

[brasscoe]

Seems to be affecting Chino Hills for sure, called Verizon again, no update, said I could call back tomorrow morning.  This sucks.  I have verizon business and a vpn server with 30+ clients, 3/4 of them having slow connection speeds now.  Maybe it's time to go back to Time Warner.

[Torched]

This problem is NOT resolved and should not be marked as such. It was temporarily resolved but is clearly back again.

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     8 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3   936 ms   945 ms   952 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   983 ms  1050 ms   989 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1019 ms  1044 ms  1052 ms  130.81.17.27
  6    49 ms    47 ms    47 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  7    47 ms    47 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    46 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9   997 ms   970 ms   979 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    47 ms    47 ms    49 ms  206.46.228.130
 11    84 ms    46 ms    47 ms  206.46.232.39

Trace complete.

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     9 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3  1040 ms   999 ms   967 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   921 ms   932 ms   929 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   926 ms   959 ms   919 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    13 ms    12 ms    11 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7    13 ms    12 ms    12 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    20 ms    17 ms    16 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
  9    19 ms    32 ms    34 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    29 ms    19 ms    19 ms  ae-73-73.csw2.SanJose1.Level3.net [4.69.134.230]

 11   983 ms  1009 ms  1070 ms  ae-2-79.edge1.SanJose1.Level3.net [4.68.18.78]
 12  1054 ms  1049 ms  1017 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    28 ms    19 ms    19 ms  209.85.251.98
 14   973 ms   987 ms   979 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

[brasscoe]

The trouble ticket they gave me was, {edited for privacy} calling again now to get status.

[jco88]

why is this problem back again!!!!!  This LSANCA-LCR-12 router/device is MESSED UP again!!

Target Name: latimes.com

         IP: 144.142.224.43

  Date/Time: 11/5/2009 7:44:51 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]

 2    3 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

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

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

 5 1008 ms  0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]

 6 1006 ms  0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]

 7 1008 ms  POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]

 8   10 ms  internapGIGE-gw.customer.alter.net [157.130.236.110]

 9   11 ms  border21.po1-20g-bbnet1.lax.pnap.net [216.52.255.38]

10   *       [-]

11  996 ms  secure.latimes.com [144.142.224.43]

Ping statistics for latimes.com

Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)

Round Trip Times: Minimum = 996ms, Maximum = 996ms, Average = 996ms

Target Name: hulu.com

         IP: 69.22.138.131

  Date/Time: 11/5/2009 7:45:18 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]

 2    4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

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

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

 5    6 ms  [130.81.17.203]

 6   32 ms  ae0-308.cr1.lax1.us.nlayer.net [69.31.127.45]

 7   56 ms  xe-1-2-0.cr1.sjc1.us.nlayer.net [69.22.142.54]

 8   28 ms  po1-30g.ar2.sjc1.us.nlayer.net [69.22.143.138]

 9   16 ms   [69.22.138.131]

Ping statistics for hulu.com

Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)

Round Trip Times: Minimum = 16ms, Maximum = 16ms, Average = 16ms

[jco88]

another trace.............. 

Target Name: www.verizon.net

         IP: 96.6.236.79

  Date/Time: 11/5/2009 7:48:06 PM

 1    0 ms    0 ms  Wireless_Broadband_Router.home [192.168.1.1]

 2    5 ms    4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

 3 1147 ms  937 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

 4 1147 ms  926 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

 5 1145 ms  914 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]

 6 1147 ms  919 ms  0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]

 7 1142 ms  929 ms  POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]

 8   37 ms   16 ms  p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.69]

 9   19 ms   21 ms  as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]

10 1157 ms  951 ms  po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]

11 1159 ms  945 ms  a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]

Ping statistics for www.verizon.net

Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)

Round Trip Times: Minimum = 945ms, Maximum = 1159ms, Average = 1052ms

[jco88]

btw, if Verizon FIOS support asks you to do a speed test by going to http://speedtest.verizon.net, it'll probably show pretty good download and upload speed.

I did a traceroute to www2.verizon.net which hosts the speedtest app and sure enough it doesn't go thru the ....LSANCA-LCR-12.verizon-gni.net troubled router/device so that test is no good.

my trace to google.... it's pretty bad...

C:\>tracert www.google.com

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     5 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3  1076 ms  1094 ms  1104 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4  1109 ms  1147 ms  1164 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5  1127 ms  1140 ms  1112 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

  6     9 ms     9 ms     9 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7  1107 ms  1082 ms  1067 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

  8  1104 ms  1092 ms  1089 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

  9    19 ms    17 ms    17 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

 10  1153 ms  1089 ms  1084 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]

 11    24 ms    24 ms    27 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]

 12    18 ms    17 ms    17 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

 13    16 ms    17 ms    17 ms  209.85.251.98

 14    16 ms    17 ms  1082 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

[dwoo]

heya 1500ms ping !!!!

Did I just get the highest ping? What prize I won?

C:\>tracert www.google.com

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

  1    24 ms    28 ms   119 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2     6 ms     4 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     6 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     7 ms     5 ms     4 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  5     8 ms  1693 ms     6 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  6     7 ms     6 ms  1744 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7  1725 ms  1740 ms  1638 ms  ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
  8    25 ms    19 ms    15 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  9  1614 ms  1740 ms  1740 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 10  1638 ms  1637 ms  1638 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 11    15 ms    15 ms    15 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 12    25 ms    17 ms    18 ms  209.85.251.98
 13  1680 ms  1635 ms  1531 ms  nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

[brasscoe]

Anyone else right now having problems bringing up these sites?

dell.com

newegg.com

speedtest.net

verizon.net

I can ping them, but can't go to them, seemes related.

[MisterJefferson]

They all come up fine and fast for me tonight. :?

[dwoo]

i can't connect to few sites either

www.newegg.com

www.dell.com

www.facebook.com

www.dealnews.com

and few others

but google is ok, 

and sometimes verizon.com 

pings are ok

FTPs are ok, 

Looks like only connect to websites has issues ..

nslookup looks ok, tracert looks ok too

Re-boot router twice, turn off Firewall too, still can't connect

Any suggestion?

[socalbob]

Just want to add the problemetic G4-0-0-2262.LSANCA-LCR-12.verizon-gni.net is affecting DSL service too.  I found this thread while researching why my 3Mbs/.768Kbs DSL is so slow during evening hour.  For what it's worth, here's my trace route:

  1    32 ms     2 ms     2 ms  xxx.xxx.xxx.1
  2   110 ms    98 ms    32 ms  L100.LSANCA-DSL-62.verizon-gni.net [xxx.xxx.xxx.1]
  3   152 ms   361 ms     *     G4-0-0-2262.LSANCA-LCR-12.verizon-gni.net [130.81.135.174]
  4     *      178 ms     *     so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5     *      251 ms     *     130.81.17.27
  6   183 ms   111 ms   186 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  7   228 ms    97 ms   182 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8   152 ms   283 ms   147 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9   140 ms   277 ms     *     po121.ctn-core1.vzlink.com [206.46.225.18]
 10   279 ms   216 ms   313 ms  206.46.228.130
 11   224 ms   213 ms   183 ms  206.46.232.39

[LarJak]

Hello from Ambler PA!

Thanks for making me feel better that I am not the only one with this problem. My high latency started around 12/9/09 I called into Verizon Tech Support on 12/12/09 as of today they had sent me a new router, dispatched a field tech who changed the ONT. He saw my lantency/slow issue and said that eveything in my house and to the ONT is good. He was supposed to leave the case open and have it esclated to tier 2 or a NT (network technician). 24 hours passed and I heard nothing, I called Verizon Tech Support to find out that the case was closed. They dispacted another tech. I asked if they are going to do anything different, knowing that they won't. When the second Tech showed up he at least was familiar with my other case and said the he will ground the new ONT, as if that is my issue, cleaned my fiber line all the way to the hub underground.  Then he took out his laptop and ran some speed test while on the phone with a NT and saw the slow speeds even from the ONT.

He said that he was able to get the ticket esclated and that Tier 2 was going to call me in 15 minutes and he would like to wait. Well while we were taling he said that he was on overtime pay and finally ask if he was holding me up from anything after sitting at my desk for 30 minutes milking the clock, which I PAY. He finally left since his wife called yelling at him on his private phone. I called back in twice today first to hear that the ticket again was closed. So now have another new ticket and then called 8 hours later to find out that I have to wait 24 business hours and they are not open on weekends. I hate Comcast but atleast they can resolve issues in a timly manor.

Been a FiOS customer since day 1 in 2006, 15/2 is what I am paying for but getting 1.69/0.654, and Verizon Tech Support says they see not issues, no fog and have rebuilt my x-connects serveral times.

Yes I ran the FiOS optimizer, what a joke it just changes the MTU size.

Did I mention I am in IT and know more they both the field techs and {please keep your posts courteous}

Here are my traces, "tracert verizon.net" any advise, PLEASE?

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   142 ms   101 ms    82 ms  L100.PHLAPA-VFTTP-76.verizon-gni.net [98.111.146.1]
3    61 ms    51 ms     9 ms  G0-0-776.PHLAPA-LCR-07.verizon-gni.net [130.81.107.188]
4     *        *        *     Request timed out.
5    14 ms    19 ms    14 ms  so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.17.3]
6   197 ms   172 ms   231 ms  so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
7   254 ms   149 ms   131 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8   103 ms    88 ms    51 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
9    52 ms   102 ms    94 ms  po121.ctn-core1.vzlink.com [206.46.225.18]

10    88 ms    51 ms   119 ms  206.46.228.130
11   111 ms    62 ms    69 ms  206.46.232.39

8:10pm 12/19/2009

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   919 ms   668 ms   759 ms  L100.PHLAPA-VFTTP-76.verizon-gni.net [98.111.146.1]

3   714 ms   734 ms   671 ms  G0-0-776.PHLAPA-LCR-07.verizon-gni.net [130.81.107.188]
4     *        *        *     Request timed out.

5   992 ms   971 ms   876 ms  so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.17.3]

6   706 ms   817 ms   841 ms  so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
7   794 ms  1009 ms   814 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8   924 ms   908 ms  1124 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
9   928 ms   808 ms  1012 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
10   895 ms  1033 ms   911 ms  206.46.228.130
11   566 ms   814 ms  1108 ms  206.46.232.39

Trace complete.