Accessibility Resource Center Skip to main content
Get it fast with In-store & curbside pickup or same day delivery.

High latency and poor speed tests lately

SOLVED
Reply
nestacio
Copper Contributor
Copper Contributor
Posts: 11
Registered: ‎10-22-2009

Re: High latency and poor speed tests lately

Message 41 of 128
(7,871 Views)

Hi Brett,

 

I am not able to test LSANCA-LCR-12 yet. that equipment only appears in the traceroute in the evenings here in Chino Hills, CA. I will post my traceroute for LCR-12 later tonight.

 

Here is my current traceroute (as of 11am PST):

 

 

 1  myrouter (192.168.1.1)  0.793 ms  0.388 ms  0.486 ms

 2  l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1)  7.238ms  7.783ms  9.489ms

 3  g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122)  10.478ms  9.159ms 

 4  so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.29.244)  9.730ms  9.576ms 

 5  0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133)  37.716ms  9.150ms  10.235ms

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

    0.ge-6-0-0.br2.lax15.alter.net (152.63.116.149)  226.760 ms  232.004 ms

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

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

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

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

    ae-63-60.ebr3.losangeles1.level3.net (4.69.144.52)  17.235 ms  14.391 ms

 9  ae-2.ebr3.sanjose1.level3.net (4.69.132.9)  237.848 ms  261.55ms  239.838ms

10  ae-63-63.csw1.sanjose1.level3.net (4.69.134.226)  252.618ms  216.51ms  208.3ms

11  ae-1-69.edge1.sanjose1.level3.net (4.68.18.14)  176.62 ms  187.039ms  162.6ms

12  google-inc.edge1.sanjose1.level3.net (4.79.43.146)  177.378ms  174.036ms 

13  209.85.251.98 (209.85.251.98)  147.398 ms  146.797 ms  172.664 ms

14  nuq04s01-in-f104.1e100.net (74.125.19.104)  149.644 ms  159.282 ms  152.626 ms

 

 

In the MORNING here in California, the problematic equipment is at lax15.alter.net (152.63.116.157) and it CHANGES to LSANCA-LCR-12.verizon-gni.net [130.81.140.162] in the evening.

 

I am confident you and the team were able to fix LCR-12 but I won't see the results of the fix yet (LCR-12 is, again, not in my traceroute until later). I will know more tonight when I run the next traceroute. For now, please flag the switch at lax15.alter.net as well since it's resulting in a 227ms ping time (not as bad as 900ms but still bad) as well.

 

Neil

 

 

Richard312
Contributor
Contributor
Posts: 4
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 42 of 128
(7,871 Views)

My Ping in the morning is much better than at night but there still hops with problems

 

 



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     6 ms     5 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     6 ms     6 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     8 ms     7 ms     8 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     7 ms     7 ms     7 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6   193 ms   204 ms   193 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]

  7    10 ms   175 ms   185 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
  8     8 ms   232 ms    14 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.2
44]
  9    21 ms    18 ms    17 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    28 ms    17 ms    17 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]

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

 12    15 ms    16 ms    16 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.14
6]
 13   281 ms   270 ms   257 ms  209.85.251.98
 14   213 ms    17 ms    16 ms  nuq04s01-in-f106.1e100.net [74.125.19.106]

Trace complete.

Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 43 of 128
(7,865 Views)

Taken at 11:30am


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     6 ms     4 ms     6 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     8 ms     7 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     7 ms     7 ms     7 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     7 ms     9 ms     7 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    19 ms    19 ms    20 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   107 ms   118 ms   109 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   103 ms   105 ms   104 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    88 ms    80 ms    85 ms  192.76.84.5
 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.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Windows\system32>

Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 44 of 128
(7,861 Views)

Taken at 12:00pm

 

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     4 ms     5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     6 ms     6 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     6 ms     7 ms     8 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-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    21 ms    20 ms    19 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7    55 ms    55 ms    69 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8    55 ms    63 ms    53 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    43 ms    46 ms    48 ms  192.76.84.5
 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.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Windows\system32>

MisterJefferson
Nickel Contributor
Nickel Contributor
Posts: 26
Registered: ‎10-15-2009

Re: High latency and poor speed tests lately

Message 45 of 128
(7,848 Views)

Indeed, my stats show that it starts bogging down around 2-3pm, is at its worst around 10-11pm, then tapers off to "normal" performance around 3-4am.  I'm inclined to believe some load balancing goes on and puts us on a different server (or other equip?) that has some issues. I've sometimes performed multiple traceroutes in a row where it toggles between LCR-11 and LCR-12, and 12 will show high latency but 11 does not. 

 

I won't be able to check again until later this evening.

Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 46 of 128
(7,841 Views)

Taken at 1:00pm

 

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     5 ms     6 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     7 ms     6 ms     8 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     7 ms     8 ms     9 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    22 ms    20 ms    20 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7    29 ms    50 ms    25 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8    34 ms    30 ms    35 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    27 ms    25 ms    25 ms  192.76.84.5

 

Everything else timed out.

spacedebris
Gold Contributor V
Gold Contributor V
Posts: 1,692
Registered: ‎05-17-2009

Re: High latency and poor speed tests lately

Message 47 of 128
(7,820 Views)

Proxus, the ones in southern California that are posting about problems are having issues with a specific Verizon router. Not related to any OS or anything at the house. They were having issues out on the Verizon network.

 

Now there are several others that are posting similar problems but most of them are outside the Verizon network and there is nothing that they or Verizon can do about it.

 

 

 

For those that don't know what we are talking about here is a basic description on interpreting a Trace route. When you look at a trace route and you see the hops (each numbered line is a hop). Each "Hop" is a router between you and your destination

Now I'm borrowing a trace route from one of the posts here just as an example

 

 1  myrouter (192.168.1.1)  0.793 ms  0.388 ms  0.486 ms

 2  l100.lsanca-vfttp-142.verizon-gni.net (xxxxxxxxxxx)  7.238ms  7.783ms  9.489ms

 3  g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122)  10.478ms  9.159ms 

 4  so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.29.244)  9.730ms  9.576ms 

 5  0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133)  37.716ms  9.150ms  10.235ms

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

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

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

 9  ae-2.ebr3.sanjose1.level3.net (4.69.132.9)  237.848 ms  261.55ms  239.838ms

10  ae-63-63.csw1.sanjose1.level3.net (4.69.134.226)  252.618ms  216.51ms  208.3ms

11  ae-1-69.edge1.sanjose1.level3.net (4.68.18.14)  176.62 ms  187.039ms  162.6ms

12  google-inc.edge1.sanjose1.level3.net (4.79.43.146)  177.378ms  174.036ms 

13  209.85.251.98 (209.85.251.98)  147.398 ms  146.797 ms  172.664 ms

14  nuq04s01-in-f104.1e100.net (74.125.19.104)  149.644 ms  159.282 ms  152.626 ms

 

Now in this example to google.

Hop number 1 is the router in the persons home.

Hop number 2 is what is called your default gateway. This is the first router after you leave your house, basically in the central office down the road somewhere.

Hops 3 and 4 are the Verizon network between you and the "Internet". Most of the people here were having problems with hop 3 when it read a specific router in the Verizon network. That is what they are working on now with VZBret.

Hops 5 to 11 (in this example) are the "internet". For all intents and purposes, your ISP nor you have any control over these. You can only hope for the best

Hops 12 to 14 are on the Google network.

 

Now the lower the ms number is the better. However for the most part, depending on distance and time of day, numbers lower than 200ms are usually OK




====================================================================================

Error exists between keyboard and chair.
Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 48 of 128
(7,814 Views)

Taken at 2:00pm

 

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     4 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     8 ms     7 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     7 ms     8 ms     8 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    20 ms    20 ms    20 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   122 ms   147 ms   139 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   123 ms   131 ms   128 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9   114 ms   125 ms   123 ms  192.76.84.5
 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.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 49 of 128
(7,805 Views)

Taken at 3:00pm

 

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     8 ms     7 ms     3 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     7 ms     7 ms     7 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     9 ms     9 ms    12 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    21 ms    21 ms    46 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   156 ms   171 ms   167 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   150 ms   156 ms   156 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9   152 ms   139 ms   128 ms  192.76.84.5
 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.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Hairstylinstacy
Nickel Contributor
Nickel Contributor
Posts: 31
Registered: ‎10-25-2009

Re: High latency and poor speed tests lately

Message 50 of 128
(7,801 Views)

My son just reported that his latency in world of warcraft just went up to 400+ and he is now "lagging" badly. I ran another tracert and this is what it showing

 

Taken at 3:20pm

 

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     5 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     7 ms     7 ms     8 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     8 ms     7 ms     8 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    21 ms    22 ms    20 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   269 ms   269 ms   259 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   241 ms   249 ms   275 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9   251 ms   245 ms   246 ms  192.76.84.5
 10     *        *        *     Request timed out.

 

Again everything past 10 timed out.

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.