High latency and poor speed tests lately

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.

All comments

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?

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.

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.

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.

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.

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

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

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.

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

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

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.

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_

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.

Just wanted to add another post--also from Chino Hills. My VPN connection and my World Of Warcraft connections have been essentially worthless for the last week or so, with tracert similar to above--and they both have a slow hop3, you guessed it, 130.81.140.162.

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 44 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 1056 ms 1104 ms 1034 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 1147 ms 1029 ms 1114 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 994 ms 1064 ms 1034 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 24 ms 19 ms 14 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

7 1026 ms 977 ms 1137 ms 192.205.35.161
8 1106 ms 1220 ms 11 ms cr1.la2ca.ip.att.net [12.123.30.6]
9 18 ms 19 ms 19 ms gar4.la2ca.ip.att.net [12.122.128.169]
10 11 ms 12 ms 14 ms 12.122.255.70
11 1012 ms 1057 ms 1049 ms 12.129.193.254
12 12.129.211.36 reports: Destination net unreachable.

Trace complete.

Tracing route to vpn.pvhmc.org [65.218.207.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 7 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 1007 ms 1059 ms 1083 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1037 ms 1086 ms 962 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1139 ms 1014 ms 1061 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 1004 ms 1044 ms 1001 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 972 ms 1077 ms 987 ms GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
8 34 ms 41 ms 47 ms pvhmc-gw.customer.alter.net [157.130.233.98]
9 51 ms 59 ms 52 ms vpn.pvhmc.org [65.218.207.68]

Trace complete.

FiosVictim

Strange problems indeed!

I have experienced the intermittent slow packet problem since FIOS installation a few months back. I won't attach ping results now, but my 25/15 Mb service operates just as described: "up to" the limits! Certainly, never actually near those limits!

My UL is steady at 5 Mbps (not as hoped for, but adequate), but my DL ranges from 1 Mbps to 12 Mbps which is very frustrating and cannot support streaming video (e.g. YouTube) without frequent pauses for re-buffering the stream. The various speed test sites and trace routes verify the same sorts of problems, but I am in Texas. I have visited 3 neighbors and see the same poor VZ performance. Also, I should add that my "slower" cable Internet 3 months ago was a better performer as it had a steady 8 Mbps flow rate (note I am using the same household wiring and the same 5 household PCs).

The problem is that the DL packet flow is sporadic and is blocked frequently....

1) Is this really a NEW problem?

2) Does VZ even acknowledge a system problem?

3) Can it be solved? (e.g. a server reboot is not a likely solution)

Well I have an update, I got frustrated because now its impacting my school website and work VPN connection. So I called support again while the problem was happening particularly badly and managed to get the engineer on the phone to acknowledge the problem and escalate it to an engineer to "look" at. That doesn't mean it will be fixed but at least they aren't arguing with me that its on my end or its the website server I'm trying to conect to.

Anyway, very important, the verizon support engineer said to have anyone else experiencing this problem call in and report. it. Let them know its a latency / slow network performance problem.

The person I spoke to had me go to speedtest.verizon.net net then had me run a couple of trace routes. which I was able to point out had high latency at G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net, which usually seems to be the culprit. If the support person won't escalate it then hang up and call back to get another engineer until they open a ticket and escalate it as a network issue.

So call in a ticket if you haven't already, can't hurt and it might just help.

Good luck!

Thanks for the update and the legwork, Torched. I will try to call tomorrow.

Ah, I'm also in Chino Hills. Interesting to see the problem coming into focus. There are TWO problematic switches so the issue will be harder to track and fix -- since different switches are turned on during different times of the day.

Before 5pm, it looks the problem is further down the route (for me, it's hop #6 which should be similar to you guys):

lax15.alter.net (152.63.116.157)

In the evenings, the problem happens EARLIER in the route (for me, hop #3) at:

LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

The reason being that, in the morning, Verizon is using LCR-11 (LSANCA-LCR-11.verizon-gni.net [130.81.140.122]) instead of LCR-12, so the problem goes away for that hop. At some point in the afternoon, they switch to LCR-12 and the ping times are HORRIBLE from that point onward. I'm seeing ping times up to 900ms.

BOTH these switches need to be fixed. I checked on alter.net in my browser and it goes to Verizon Business, so both switches are owned by Verizon (luckily) and they have the ability to actually do something about it.

Neil

Nestacio.. Could you & MisterJeferson please private message me you tn# and address so I could start to creat tickets & get them over to our team to look @ the router. Thanks guys. Brett

aravoth

I am having the exact same issue. I live in Troutdale Oregon, just outside of Portland. I'm supposed to have 15/2 but my speeds have been this :

Download Speed: 9117 kbps (1139.6 KB/sec transfer rate)
Upload Speed: 1841 kbps (230.1 KB/sec transfer rate)

From Speakeasy

And from speedtest it says 4.29Mb/s download, and 1.6 Mb/s uplaod.

It also says That I'm on the east coast, when I'm actually over two thousand miles away from the east coast.

Tracer route says this.

C:\Documents and Settings\Owner>cd\

C:\>tracert google.com

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

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 8 ms 6 ms 8 ms **.***.***.1
3 7 ms 7 ms 7 ms ***.**.***.10
4 13 ms 14 ms 15 ms P12-0.PTLDOR-LCR-01.verizon-gni.net [130.81.27.1
72]
5 14 ms 14 ms 14 ms so-7-3-0-0.SEA01-BB-RTR1.verizon-gni.net [130.81
.28.160]
6 13 ms 14 ms 14 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
7 15 ms 14 ms 15 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
8 14 ms 14 ms 14 ms POS4-0.BR2.SEA1.ALTER.NET [152.63.106.9]
9 13 ms 14 ms 14 ms 204.255.169.22
10 20 ms 16 ms 20 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

11 69 ms 72 ms 69 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
12 75 ms 72 ms 72 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
13 68 ms 72 ms 69 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
14 70 ms 70 ms 72 ms ae-93-98.ebr3.Dallas1.Level3.net [4.69.146.92]
15 101 ms * * ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 97 ms 97 ms 97 ms ae-21-52.car1.Atlanta1.Level3.net [4.68.103.34]

17 88 ms 89 ms 90 ms GOOGLE-INC.car1.Atlanta1.Level3.net [4.71.20.22]

18 89 ms 90 ms 112 ms 209.85.254.241
19 101 ms 92 ms 89 ms 209.85.253.137
20 97 ms 98 ms 97 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

Any Ideas? I guess it's an actual network issue, but is there anything I can do on my end? I've talked to tech support multiple times, I'm pretty sure they'll hire anyone at Verizon. The people I talked to told me that I had to many processes running, lol. 50 processes and less than 1/4 of them use the network. Then he just sat on the phone breathing through his mouth for 20 minutes before telling me that it was a problem with the box. He then transfered me to billing so it could be fixed..... seriously, the guy thought billing could fix it.......billing man, what the #$%^

aravoth

the network gremlin just struck again

C:\>tracert google.com

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

1 2 ms 2 ms 4 ms myrouter.home [192.168.1.1]
2 7 ms 8 ms 7 ms
3 11 ms 9 ms 9 ms
4 17 ms 17 ms 17 ms P12-0.PTLDOR-LCR-01.verizon-gni.net [130.81.27.1
72]
5 17 ms 16 ms 16 ms so-7-3-0-0.SEA01-BB-RTR1.verizon-gni.net [130.81
.28.160]
6 15 ms 17 ms 16 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
7 20 ms 59 ms 17 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
8 17 ms 16 ms 20 ms POS6-0.BR2.SEA1.ALTER.NET [152.63.106.1]
9 158 ms 202 ms 204 ms oc48-7-1.car4.seattle1.level3.net [4.68.63.229]

10 29 ms 17 ms 19 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

11 21 ms 19 ms 20 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

12 71 ms 72 ms 69 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
13 80 ms 72 ms 71 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
14 76 ms 75 ms 69 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
15 75 ms 70 ms 73 ms ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76]
16 99 ms 103 ms 107 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
17 200 ms 220 ms 103 ms ae-21-52.car1.Atlanta1.Level3.net [4.68.103.34]

18 91 ms 92 ms 91 ms GOOGLE-INC.car1.Atlanta1.Level3.net [4.78.208.11
4]
19 90 ms 99 ms 99 ms 209.85.254.247
20 93 ms 104 ms 95 ms 64.233.174.46
21 98 ms 100 ms 98 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

C:\>

All, who are having high latency issues w/ LSANCA-LCR-11/12 & posted all your trace routes much appreciated! We have opened a group ticket & will most likely be worked on safetime tonight. Will update you all tomorrow once I have reviewed the notes. Thanks again for all your help! Brett

That is excellent news Brett! Thank you for making the effort to help us out.

Just as an FYI I just spoke with a Nayomal from the Verizon Network group today who called me regarding my ticket from last night. He asked me for more information which I provided because he was trying to familiarize himself with my problem. He said he was going to get another group involved to look into the problem. I mention this just to help you guys out so you don't have people duplicating efforts.

I can post my ticket number later tonight when i'm home if you think that will be of help?

Thanks,

Brian

Thank you very much Brett!

And thanks to everyone else who has been posting information to get this fixed.

ElizabethS

Please do not post your ticket numbers on the thread. That is considered private information. But feel free to share them in PM.

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]

Proxus

Is everyone running Vista/Win 7. I have the exact same issue in NJ. Low pings sometimes/ high pings sometimes. Extremely high latency, unable to stay connected to games and RDP for work. XP Machines appears to not be having much of an issue.

I've had the same problem with each of the 3 OS's you listed. Originally I was running windows 7, reinstalled Vista to see if that would help(which it didn't), then moved my son's XP machine from wireless to wired and still the same problems. It really seems like it's a problem on Verizon's end, which Brett is pretty much confirmed and they are working on it.

Hairstylinstacy , Have you had any latency yet? All keep us updated. Thanks

http://support.microsoft.com/kb/939006

i used XP and Mac OSX with same results the past few days. I haven't tried today yet... will post later tonight when i get home to see if problem still persists...

Proxus

I am wondering if it possible could be the protocal stack in vista/win 7.

This fix is suppose to address it buy updating to the latest Service Pack, which I have installed. I still have the issue.

I am also going to try to roll back my vista ethernet driver, but I dont know if that will work. We are new to FIOS and I have never had such an issue with any ISP before. I am greatly disappointed.

Brett,

My latency has been normal this morning(great). My son has been playing world of wacraft and said his latency is 60-100ms(which he is says is normal)

Here is my latest tracert taken at 11:00am

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 6 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 7 ms 8 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 22 ms 20 ms 20 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 49 ms 42 ms 47 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 85 ms 89 ms 75 ms verizon-gw.customer.alter.net [157.130.203.246]

9 96 ms 77 ms 79 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.

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

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.

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.

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.

Interwebs

Haha, thanks for the good news Brett! Hope this gets solved very soon!

However, it seems that a lot of people from Chino Hills are getting this issue.... is this significant to the problem?

Following are new tracert to the 2 servers I posted earlier. The numbers have improved but I am still getting average in-game latency of ~400ms in World of Warcraft. A definite improvement from the last 2 weeks but still nowhere as good as previous to that.

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 7 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net{edited for privacy}
3 242 ms 254 ms 257 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 271 ms 284 ms 294 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 316 ms 344 ms 317 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 11 ms 12 ms 10 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 338 ms 329 ms 314 ms 192.205.35.161
8 296 ms 299 ms 12 ms cr1.la2ca.ip.att.net [12.123.30.6]
9 11 ms 10 ms 9 ms gar4.la2ca.ip.att.net [12.122.128.169]
10 11 ms 12 ms 12 ms 12.122.255.70
11 351 ms 339 ms 352 ms 12.129.193.254
12 12.129.211.36 reports: Destination net unreachable.

Trace complete.

Tracing route to vpn.pvhmc.org [65.218.207.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 12 ms 8 ms 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net {edited for privacy}
3 276 ms 289 ms 294 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 264 ms 259 ms 274 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 318 ms 317 ms 317 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 299 ms 307 ms 308 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 272 ms 272 ms 263 ms GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
8 14 ms 17 ms 16 ms pvhmc-gw.customer.alter.net [157.130.233.98]
9 16 ms 17 ms 16 ms vpn.pvhmc.org [65.218.207.68]

Trace complete.

Tracert for verizon.net and google.com also, in case they help:

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 9 ms 24 ms 8 ms L100.LSANCA-VFTTP-142.verizon-gni.net {edited for privacy}
3 20 ms 9 ms 23 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 10 ms 20 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 48 ms 54 ms 47 ms so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.18]
6 48 ms 55 ms 48 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 47 ms 50 ms 51 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 47 ms 52 ms 66 ms po121.ctn-core1.vzlink.com [206.46.225.18]
9 52 ms 53 ms 46 ms 206.46.228.130
10 58 ms 61 ms 47 ms 206.46.232.39

Trace complete.

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

1 17 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 15 ms 6 ms 25 ms L100.LSANCA-VFTTP-142.verizon-gni.net{edited for privacy}
3 203 ms 221 ms 198 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 217 ms 235 ms 226 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 250 ms 242 ms 252 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 17 ms 12 ms 20 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 237 ms 221 ms 219 ms 192.205.35.161
8 260 ms 268 ms 285 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 70 ms 87 ms 66 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 94 ms 93 ms 97 ms cr1.attga.ip.att.net [12.122.28.173]
11 256 ms 259 ms 286 ms 12.123.22.5
12 68 ms 69 ms 70 ms 12.88.97.6
13 97 ms 70 ms 76 ms 72.14.233.56
14 106 ms 291 ms 294 ms 209.85.254.241
15 68 ms 288 ms 71 ms 209.85.253.137
16 75 ms 85 ms 85 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

4: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 4 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 6 ms 8 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 8 ms 6 ms 7 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 9 ms 8 ms 7 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 21 ms 21 ms 19 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 192 ms 181 ms 182 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 163 ms 220 ms 236 ms verizon-gw.customer.alter.net [157.130.203.246]

9 194 ms 211 ms 213 ms 192.76.84.5
10 * * * Request timed out.

Things are horrible again. Surfing is slow, son is telling me that online games are unplayable because of the "lag"

Hope this helps getting this issue fixed.

5:00p

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

9 520 ms 484 ms 464 ms 192.76.84.5
10 * * * Request timed out.

I was hopeful this morning since things seemed better but unfortunately the problem has returned again this evening. Makes me think this is due to load / congestion.

Tracing route to e3002.b.akamaiedge.net [96.6.60.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 8 ms 7 ms l100.lsanca-vfttp-142.verizon-gni.net [173.55.53.1]
3 284 ms 295 ms 281 ms g4-0-6-1242.lsanca-lcr-12.verizon-gni.net [130.81.140.162]
4 293 ms 309 ms 292 ms so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net [130.81.29.246]
5 304 ms 297 ms 292 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 317 ms 330 ms 319 ms 0.so-7-3-0.XT2.LAX7.ALTER.NET [152.63.112.62]
7 314 ms 294 ms 302 ms 0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
8 35 ms 34 ms 37 ms 204.255.168.34
9 247 ms 243 ms 271 ms los-core-02.inet.qwest.net [205.171.32.13]
10 53 ms 54 ms 79 ms los-edge-01.inet.qwest.net [205.171.32.46]
11 41 ms 41 ms 42 ms a96-6-60-79.deploy.akamaitechnologies.com [96.6.60.79]

Trace complete.

Also, I get bad lag for servers back east (LOTRO.COM). But the latency spike is **bleep**her down stream.

Tracing route to gls.lotro.com [206.16.13.82]
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..1]
3 10 ms 10 ms 9 ms g4-0-6-1142.lsanca-lcr-11.verizon-gni.net [1301.140.122]
4 9 ms 10 ms 9 ms so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net [130..29.244]
5 9 ms 12 ms 10 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6 13 ms 12 ms 12 ms 0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157

7 11 ms 12 ms 11 ms 192.205.35.161
8 415 ms 429 ms 422 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 416 ms 435 ms 442 ms cr1.slkut.ip.att.net [12.122.30.29]
10 437 ms 430 ms 459 ms cr2.dvmco.ip.att.net [12.122.30.26]
11 490 ms 451 ms 439 ms cr1.cgcil.ip.att.net [12.122.31.86]
12 464 ms 449 ms 447 ms cr2.cgcil.ip.att.net [12.122.2.54]
13 463 ms 467 ms 426 ms cr1.n54ny.ip.att.net [12.122.1.1]
14 421 ms 417 ms 432 ms cr2.n54ny.ip.att.net [12.122.2.14]
15 432 ms 447 ms 459 ms cr1.cb1ma.ip.att.net [12.122.31.126]
16 455 ms 454 ms 439 ms gar5.cb1ma.ip.att.net [12.122.145.29]
17 461 ms 447 ms 419 ms 12-122-254-14.attens.net [12.122.254.14]
18 459 ms 447 ms 424 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.
0.0.174]
19 458 ms 472 ms 450 ms 12.130.10.69
20 440 ms 465 ms 459 ms 206.16.13.82

Trace complete.

Please help us and resolve this as soon as possible. .

Hi gang,

As promised, here's the result of the evening traceroute at 5:30pm PST. Predictably, lsanca-lcr-12.verizon-gni.net (130.81.140.162) has returned and is wreaking havoc with latency: 430ms ping times.

......

1 myrouter (192.168.1.1) 0.629 ms 0.375 ms 0.488 ms

2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 6.995 ms 6.877 ms 7.219 ms

3 g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162) 437.784 ms 429.885 ms 416.979 ms

4 so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246) 424.980 ms 422.137 ms 421.965 ms

5 0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125) 430.175 ms 444.371 ms 409.696 ms

6 0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153) 37.936 ms 39.381 ms 41.933 ms

7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 402.519 ms 428.860 ms 408.240 ms

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

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

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

9 ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 452.389 ms 433.865 ms 410.502 ms

10 ae-63-63.csw1.sanjose1.level3.net (4.69.134.226) 407.252 ms 417.010 ms 420.001 ms

11 ae-1-69.edge1.sanjose1.level3.net (4.68.18.14) 397.239 ms 371.884 ms 404.529 ms

12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 402.939 ms 394.159 ms 394.988 ms

13 209.85.251.98 (209.85.251.98) 399.983 ms 424.657 ms 419.952 ms

14 nuq04s01-in-f103.1e100.net (74.125.19.103) 454.476 ms 437.089 ms 449.736 ms

......

So Hop #3 still needs to be looked at, nothing has changed as of yet. To add to the comment from Torched, the problem ONLY SHOWS UP IN THE EVENING. There is a reason. Don't let the numbers below glaze your eyes over, just follow:

This is because, once again, in the MORNING, Hop #3 uses LCR-11. In the EVENING, Hop #3 uses LCR-12. To summarize:

Before 5pm: LCR-11 is active at Hop #3: this switch works (ping is acceptable)
After 5pm: LCR-12 instead at Hop #3: this switch is NOT working

The equipment activated at Hop #3 in the morning is DIFFERENT from the equipment being used in the route at Hop #3 in the evening.

The morning route has its own issue, namely LAX15.ALTER.NET (152.63.116.157) at Hop #6, which increases ping to ~200ms and higher.

Brett, if you're addressing one thing at a time, here's the suggestion: 1) fix LCR-12 first; then 2) fix LAX15 next.

Neil

6: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 4 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 7 ms 7 ms 7 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 7 ms 8 ms 7 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 20 ms 22 ms 20 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 426 ms 430 ms 452 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 423 ms 407 ms 418 ms verizon-gw.customer.alter.net [157.130.203.246]

9 392 ms 377 ms 364 ms 192.76.84.5
10 * * * Request timed out.

Well I called verizon technical support to see if there was any update on my ticket and as expected they are telling me I don't have a problem, and that I need to have my RWIN increased (meaning I need to install their new optimization software in order to improve my network performance). This is a complete load of garbage as we all know.

I'm EXTREMELY disastisfied with verizon technical support (Brett and team are excluded of course you've been very helpful). I have been very patient up until tonight, I have not yelled or complained. But tonight I had enough and demanded to speak with a supervisor. They transfered me to an excalation manager who answered and then hung up on me. This is the second time I have been hung up on by someone at Verizon. I find it hard to believe that Verizon employees are that incompetent with the operation of a telephone so I can only conclude that i'm being intentionally hung up on.

I'm now looking for alternative ISPs to resolve this problem. It will take a long time to select and setup new service so if this gets resolved in a relatively short time then I'll probably stay since up until now I have been very satisfied with FIOS.

What frustrates me is I was trying to direct the Verizon technician to this support forum to try and prove this is not a problem that is isoloated to me but he just refused and kept repeating my RWIN should be at 9000 and I need to install software in order to get good performance with FIOS.

I then said "Are you telling me that in order for me to recieved broadband service with FIOS I know need to install this software?" and he said "Yes"!

That's when I escalated...

Sorry for the rant...I'm just **bleep**, this impacts my ability to work from home and the online classes I'm taking.

From chino hills... this is my latest trace. as you can see, the network latency issue is NOT FIXED. It is getting very frustrating dealing with this and talking to FIOS support coz they don't seem to want to do anything about it. Not sure what part of ' several Chino Hills resident's are having the same problem' don't they understand. It's not a PC, router, config on our side but it's their so called 'FIBER' optic network that is messed up. It's been 2 weeks now and nothing!!!

$ tracert latimes.com

Tracing route to latimes.com [144.142.224.43]

over a maximum of 30 hops:

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

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

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

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

5 506 ms 532 ms 537 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]

6 507 ms 513 ms 516 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]

7 516 ms 508 ms 511 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]

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

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

10 * * * Request timed out.

11 484 ms 469 ms 491 ms secure.latimes.com [144.142.224.43]

Trace complete.

$ tracert verizon.net

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

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

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

5 488 ms 421 ms 412 ms 130.81.17.27

6 61 ms 56 ms 51 ms so-7-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.12]

7 42 ms 44 ms 37 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]

8 65 ms 57 ms 61 ms po1.ctn-border1.vzlink.com [206.46.225.85]

9 413 ms 417 ms 418 ms po121.ctn-core1.vzlink.com [206.46.225.18]

10 390 ms 406 ms 387 ms 206.46.228.130

11 53 ms 59 ms 57 ms 206.46.232.39

7: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 7 ms 5 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 7 ms 6 ms 7 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 7 ms 8 ms 7 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 651 ms 639 ms 633 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 660 ms 675 ms 690 ms verizon-gw.customer.alter.net [157.130.203.246]

9 622 ms 627 ms 599 ms 192.76.84.5
10 * * * Request timed out.

by the way, if you haven't tried it... you can use pingplotter to do trace and you can visually see where the latency is... you can configure it to trace at a certain number of intervals to get a good sampling and can send to a tech guy for analysis.

get it from http://www.pingplotter.com/

It doesn't look like maintenance fixed my issue. Seems worse tonight (10/27, 8:05pm):

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 8 ms 7 ms 7 ms xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
3 1111 ms 1076 ms 1104 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1054 ms 1047 ms 982 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1028 ms 1037 ms 981 ms 130.81.17.27
6 67 ms 77 ms 77 ms so-7-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.12]
7 127 ms 97 ms 85 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 71 ms 69 ms 77 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 1030 ms 1007 ms 992 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 75 ms 75 ms 79 ms 206.46.228.130
11 67 ms 63 ms 58 ms 206.46.232.39

Trace complete.

ken3685a

I'm also from Chino Hills and I'm having the same problem for the past 10 days or so. I called the tech support this morning and they pretty much blame my system for the slow down. If they don't resolve this problem soon, I might have to shop around for a new ISP.

tracert www.verizon.net

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 4 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 705 ms 734 ms 726 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 726 ms 768 ms 760 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 733 ms * 812 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 795 ms 779 ms 824 ms POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
7 781 ms 774 ms 777 ms p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.25
0.8.205]
8 760 ms 805 ms 823 ms po-1.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.2
54]
9 837 ms 842 ms 818 ms a69-192-44-79.deploy.akamaitechnologies.com [69.
192.44.79]

Trace complete.

Taken at 9:45pm

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

9 1112 ms 1153 ms 1167 ms 192.76.84.5

Called Verizon support again to see if there was any more information to obtain and after a lengthy conversation I was told that the problem is on my end, and that Verizon's service is fine...

ken3685a

As of 10:16pm, it's getting worse. This is getting ridiculous.... I will call the tech support tomorrow and if they still in denial stage, time to cancel the service.

tracert www.verizon.net

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 4 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 1151 ms 1159 ms 1139 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 1174 ms 1134 ms 1139 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 1174 ms 1162 ms 1137 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 1151 ms 1164 ms 1162 ms POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
7 1219 ms 1179 ms 1172 ms p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.25
0.8.205]
8 1191 ms * 1253 ms po-1.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.2
54]
9 1219 ms 1254 ms 1242 ms a69-192-44-79.deploy.akamaitechnologies.com [69.
192.44.79]

Trace complete.

@Hairstylinstacy wrote:
Called Verizon support again to see if there was any more information to obtain and after a lengthy conversation I was told that the problem is on my end, and that Verizon's service is fine...

Yeah, everything's fine from your home to the central office. The problem is further up the river. The techs on the phone don't seem to understand that. Even the field tech that came out to the house kept trying to say it wasn't their problem and said he'd have his supervisor call me. Never got a call.

I am from Chino Hills, these recent two weeks I am getting slow internet browsing. Here is my tracert to google.com @ 10/27 11:45PM

I guess the problem would be 130.8.1.140.162

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

1 2 ms 1 ms 2 ms L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
2 814 ms 818 ms 732 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 841 ms 716 ms 675 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 740 ms 714 ms 716 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 8 ms 5 ms 7 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
6 749 ms 716 ms 716 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
7 841 ms 820 ms 817 ms ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.179]
8 840 ms 820 ms 817 ms ae-2.ebr2.SanJose1.Level3.net [4.69.132.13]
9 36 ms 34 ms 33 ms ae-7.ebr1.Seattle1.Level3.net [4.69.132.50]
10 790 ms 822 ms 815 ms ae-1-51.edge1.Seattle3.Level3.net [4.68.105.12]
11 735 ms 716 ms 716 ms GOOGLE-INC.edge1.Seattle3.Level3.net [4.59.232.34]
12 37 ms 34 ms 37 ms 209.85.249.32
13 39 ms 38 ms 38 ms 72.14.239.12
14 776 ms 818 ms 819 ms 209.85.250.146
15 44 ms 42 ms 857 ms 216.239.48.165
16 51 ms 1034 ms 45 ms 72.14.232.10
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 ^C

Also this is tracert verizon.com, all looks good if using LCR-11 instead of 12, but still something high ping,

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

1 3 ms 1 ms 2 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 10 ms 5 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 19 ms 17 ms 17 ms 0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
6 960 ms 1024 ms 1022 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
7 920 ms 921 ms 921 ms verizon-gw.customer.alter.net [157.130.203.246]
8 24 ms 17 ms 19 ms 192.76.84.5
9 * * * Request timed out.
10 * * * Request timed out.
11 * * ^C

hope this help and wish Verizon fix this soon,

All, we do have a group ticket opened up on that router. I just updated the new trace routes & waiting a reply back, once i get one will update here. Thanks again

aravoth

It's not just chino hills, Like I said earlier, I'm in Portland, Oregon, same problem. {please keep your posts courteous}. This has been going on for way too long. Fix the fracken network already. I'm not calling tech support again. If I hear one more **bleep** tell me to push the reset button on that {edit} router verizon supplies, I am going to puke.

If I wanted DSL speeds, I would have ordered DSL.

Additionaly, Verizon needs to hire people for tech support that can read above a third grade level, and have a strong command of the english language. When a tech support person says, "I'mma putch ya through ta billin' soze you can axe em' what ta do", it doesn't inspire confidence, both in the person that said that, and the person that hired him.

Billing can not fix this, and twice now, Tech support has tried to transfer me to billing.

I can understand that problems arise, and need to be tracked down, isolated and fixed. It wouldn't be so bad if Tech support(outsourced I assume) would at least admit that there is a problem instead of blaming the customers each time. Honestly if it wasn't for Brett posting in this thread notifying us that things are acknowledged, and being escalated to the proper departments I would have canceled already and went back to AT&T Uverse.

Aravoth, your problem has nothing to do with what is being talked about here. The trace route you posted....

@aravoth wrote:

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

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 8 ms 6 ms 8 ms **.***.***.1
3 7 ms 7 ms 7 ms ***.**.***.10
4 13 ms 14 ms 15 ms P12-0.PTLDOR-LCR-01.verizon-gni.net [130.81.27.1
72]
5 14 ms 14 ms 14 ms so-7-3-0-0.SEA01-BB-RTR1.verizon-gni.net [130.81
.28.160]
6 13 ms 14 ms 14 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
7 15 ms 14 ms 15 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
8 14 ms 14 ms 14 ms POS4-0.BR2.SEA1.ALTER.NET [152.63.106.9]
9 13 ms 14 ms 14 ms 204.255.169.22
10 20 ms 16 ms 20 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

11 69 ms 72 ms 69 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
12 75 ms 72 ms 72 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
13 68 ms 72 ms 69 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
14 70 ms 70 ms 72 ms ae-93-98.ebr3.Dallas1.Level3.net [4.69.146.92]
15 101 ms * * ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 97 ms 97 ms 97 ms ae-21-52.car1.Atlanta1.Level3.net [4.68.103.34]

17 88 ms 89 ms 90 ms GOOGLE-INC.car1.Atlanta1.Level3.net [4.71.20.22]

18 89 ms 90 ms 112 ms 209.85.254.241
19 101 ms 92 ms 89 ms 209.85.253.137
20 97 ms 98 ms 97 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

shows no obvious network related issues. The only problem I see on this particular trace route is a possible problem on hop 15 in Atlanta GA. This is out on the internet and there is nothing that Verizon or you can do about that one. But for the most part your trace route looks perfectly normal. Unlike the ones being discussed on this thread.

No, if you are having speed issues. It is something different that what is being talked about here. If I were you, I'd start another thread, give a description of your problem and let the VZ guys start looking into it, and provide suggestions on your particular issue.

the latest tracert (10-28-2009, 2:15pm) from Chino Hills,

to google.com

Tracing route to google.com {edited for privacy}
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
2 279 ms 205 ms 203 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
3 216 ms 199 ms 204 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
4 220 ms 307 ms 305 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 7 ms 5 ms 6 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

6 7 ms 5 ms 5 ms 192.205.35.161
7 62 ms 60 ms 63 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 63 ms 61 ms 61 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 201 ms 304 ms 306 ms cr1.attga.ip.att.net [12.122.28.173]
10 190 ms 197 ms 270 ms 12.123.22.5
11 394 ms 408 ms 306 ms 12.88.97.6
12 64 ms 60 ms 61 ms 72.14.233.56
13 394 ms 304 ms 409 ms 209.85.254.249
14 64 ms 61 ms 71 ms 64.233.174.46
15 300 ms 307 ms 306 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

to verizon.com

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

1 2 ms 1 ms 1 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
2 6 ms 4 ms 5 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.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 8 ms 6 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 18 ms 17 ms 17 ms 0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
6 270 ms 204 ms 204 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
7 241 ms 204 ms 205 ms verizon-gw.customer.alter.net [157.130.203.246]

8 22 ms 17 ms 18 ms 192.76.84.5
9 * * * Request timed out.
10 * ^C

****** much much better than yesterday, good job ******

(well, if LCR-12 can lower to 100 ping that will be better 😛 )

Caution

Hello all.... Well to keep consistent i am another user/subscriber here in the Chino/Chino hills area. and as like everyone else i have severe latency while surfing the net or playing online game. below are some of my tracert print outs.....

Target Name: www.download.com
IP: 216.239.122.164
Date/Time: 10/28/2009 3:18:16 PM

1 1 ms 3 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 10 ms 9 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 511 ms 507 ms 424 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 507 ms 519 ms 430 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 500 ms 517 ms 426 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 495 ms 524 ms 429 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 18 ms 11 ms 14 ms [192.205.35.161]
8 50 ms 46 ms 46 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 530 ms 562 ms 460 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 561 ms 561 ms 468 ms gar10.dlstx.ip.att.net [12.122.138.125]
11 542 ms 557 ms 473 ms [12.87.121.22]
12 533 ms 551 ms 476 ms c18-rb-gtm1-tron-xw-lb.cnet.com [216.239.122.164]

Ping statistics for www.download.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 476ms, Maximum = 551ms, Average = 520ms

Target Name: www.download.com
IP: 216.239.122.176
Date/Time: 10/28/2009 3:34:06 PM

1 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 9 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 336 ms 340 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 334 ms 342 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 330 ms 336 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 332 ms 336 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 11 ms 16 ms [192.205.35.161]
8 49 ms 50 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 329 ms 373 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 334 ms 352 ms gar10.dlstx.ip.att.net [12.122.138.117]
11 341 ms 346 ms [12.87.121.22]
12 334 ms 343 ms c18-rb-gtm3-tron-xw-lb.cnet.com [216.239.122.176]

Ping statistics for www.download.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 334ms, Maximum = 343ms, Average = 338ms

When playing online games my latency starts at about 400ms...... and by 9pm...it will be near 5000ms....

Hopefully another person posting here will help.....

thanks

4:50pm can't believe lag is back !! (10/28/2009)

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

1 2 ms 1 ms 2 ms L101.VFTTP-142.LSANCA.verizon-gni.net{edited for privacy}
2 563 ms 513 ms 510 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 533 ms 511 ms 511 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 534 ms 511 ms 511 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 431 ms 512 ms 411 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
6 9 ms 5 ms 5 ms 192.205.35.161
7 63 ms 61 ms 61 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 105 ms 60 ms 61 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 490 ms 408 ms 410 ms cr1.attga.ip.att.net [12.122.28.173]
10 442 ms 409 ms 409 ms 12.123.22.5
11 432 ms 409 ms 409 ms 12.88.97.6
12 532 ms 513 ms 511 ms 72.14.233.54
13 535 ms 513 ms 509 ms 72.14.232.215
14 532 ms 511 ms 514 ms 209.85.253.145
15 639 ms 716 ms 616 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

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

1 7 ms 2 ms 2 ms L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.182.1]
2 6 ms 3 ms 4 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
3 9 ms 4 ms 4 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
4 7 ms 6 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 19 ms 17 ms 21 ms 0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
6 459 ms 409 ms 408 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
7 433 ms 406 ms 409 ms verizon-gw.customer.alter.net [157.130.203.246]
8 20 ms 17 ms 18 ms 192.76.84.5
9 * * * Request timed out.
10 * ^C

My current tracerts are below. Practically speaking (i.e. in-game and downloading), connection remains very poor.

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 7 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 246 ms 254 ms 247 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 287 ms 287 ms 297 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 329 ms 324 ms 337 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 12 ms 12 ms 22 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 305 ms 302 ms 292 ms 192.205.35.161
8 11 ms 12 ms 294 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 9 ms 12 ms 12 ms gar4.la2ca.ip.att.net [12.122.129.169]
10 12 ms 12 ms 12 ms 12.122.255.70
11 283 ms 281 ms 292 ms 12.129.193.254
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 12.129.211.36 reports: Destination net unreachable.

Trace complete.

Tracing route to vpn.pvhmc.org [65.218.207.68]
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 L100.LSANCA-VFTTP-142.verizon-gni.net
3 351 ms 334 ms 347 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 351 ms 352 ms 349 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 371 ms 357 ms 394 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 424 ms 409 ms 416 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 438 ms 422 ms 399 ms GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
8 15 ms 15 ms 14 ms pvhmc-gw.customer.alter.net [157.130.233.98]
9 21 ms 16 ms 19 ms vpn.pvhmc.org [65.218.207.68]

Trace complete.

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 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 10 ms 10 ms 9 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 9 ms 10 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 47 ms 47 ms 48 ms so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.18]
6 129 ms 84 ms 46 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 48 ms 47 ms 47 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 47 ms 47 ms 47 ms po121.ctn-core1.vzlink.com [206.46.225.18]
9 46 ms 47 ms 47 ms 206.46.228.130
10 45 ms 47 ms 47 ms 206.46.232.39

Trace complete.

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 7 ms 7 ms 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 473 ms 469 ms 455 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 391 ms 396 ms 402 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 377 ms 392 ms 362 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 10 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 380 ms * 418 ms 192.205.35.161
8 389 ms 397 ms 424 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 63 ms 65 ms 67 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 65 ms 64 ms 65 ms cr1.attga.ip.att.net [12.122.28.173]
11 376 ms 379 ms 390 ms 12.123.22.5
12 66 ms 64 ms 65 ms 12.88.97.6
13 480 ms 481 ms 527 ms 72.14.233.54
14 * 71 ms 77 ms 72.14.239.127
15 80 ms 72 ms 72 ms 64.233.174.46
16 70 ms 66 ms 67 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

6:00 PM 10/28/2009 problem still continues in Chino Hills, Ca.

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

1 <1 ms <1 ms <1 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 286 ms 282 ms 281 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 303 ms 305 ms 266 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 236 ms 236 ms 239 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 11 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

7 24 ms 24 ms 29 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 250 ms 239 ms 252 ms ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
9 29 ms 34 ms 37 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 250 ms 256 ms 245 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]

11 251 ms 254 ms 252 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12 299 ms 270 ms 314 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 31 ms 19 ms 34 ms 209.85.251.98
14 282 ms 316 ms 327 ms nuq04s01-in-f99.1e100.net [74.125.19.99]

Trace complete.

Tracing route to e3002.b.akamaiedge.net [96.6.236.79]
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 14 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 366 ms 359 ms 355 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 342 ms 330 ms 327 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 322 ms 424 ms 350 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 369 ms 367 ms 359 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 380 ms 372 ms 367 ms POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
8 362 ms 361 ms 355 ms p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.205]
9 361 ms 372 ms 402 ms as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]
10 405 ms 396 ms 375 ms po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]
11 400 ms 392 ms 429 ms a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]

Trace complete.

Caution

Hello again... Here is another latency report from Chino/Chino Hills.... Test done at approx 8pm

Target Name: www.google.com
IP: 74.125.19.104
Date/Time: 10/28/2009 8:02:32 PM

1 3 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 8 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 471 ms 495 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 471 ms 498 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 475 ms 503 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 468 ms 523 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 16 ms 10 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 13 ms 15 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
9 27 ms 30 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 498 ms 538 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11 19 ms 20 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12 24 ms 18 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 21 ms 524 ms [209.85.251.98]
14 494 ms 20 ms nuq04s01-in-f104.1e100.net [74.125.19.104]

Ping statistics for www.google.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 20ms, Maximum = 494ms, Average = 257ms

SIGH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

8:10pm getting worse ... 😞

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

1 2 ms 2 ms 1 ms L300.LSANCA-VFTTP-142.verizon-gni.net [hide for privacy]
2 639 ms 615 ms 613 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 629 ms 613 ms 614 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 626 ms 614 ms 716 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 8 ms 6 ms 9 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
6 603 ms 643 ms 616 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
7 614 ms 602 ms 639 ms ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.179]
8 623 ms 646 ms 717 ms ae-2.ebr2.SanJose1.Level3.net [4.69.132.13]
9 35 ms 33 ms 33 ms ae-7.ebr1.Seattle1.Level3.net [4.69.132.50]
10 677 ms 610 ms 718 ms ae-1-51.edge1.Seattle3.Level3.net [4.68.105.12]
11 626 ms 614 ms 719 ms GOOGLE-INC.edge1.Seattle3.Level3.net [4.59.232.34]
12 59 ms * 36 ms 209.85.249.32
13 39 ms 38 ms 38 ms 72.14.239.12
14 676 ms 717 ms 715 ms 216.239.48.32
15 42 ms 596 ms 613 ms 216.239.48.165
16 42 ms 593 ms 613 ms 72.14.232.2
17 42 ms 39 ms 41 ms pw-in-f100.1e100.net [74.125.53.100]

Trace complete.