- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. http://img190.imageshack.us/img190/3411/latencyw.jpg
2. [edit]
3. http://img43.imageshack.us/img43/8881/vzdiag.jpg
4. http://img251.imageshack.us/img251/1575/tracert.jpg
Four images for your consideration. All are screenshots taken within a 10 minute timeframe. These screenshots show that in no way is my issue unique to one ATT server that I will hardly ever connect to. This is an issue that is affecting everything I am trying to connect to.
I tried to use the FIOS speed optimizer which was unsuccessful in doing it's job. I tried to run it on multiple computers with multiple OS's on both wired and wireless connections. ALL failed. I'm thinking that my router or the lines that were installed in my house or neighborhood are [edit] . I'm not going to pay for a service that I'm not receiving.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe i'm suffering from the same problem:
Tracing route to www.l.google.com [74.125.19.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 561 ms 537 ms 559 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 595 ms 571 ms 595 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 578 ms 594 ms 604 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 12 ms 11 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 11 ms 12 ms 14 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
8 15 ms 17 ms 17 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1
16]
9 21 ms 23 ms 29 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 671 ms 682 ms 701 ms ae-73-73.csw2.SanJose1.Level3.net [4.69.134.230]
11 662 ms 729 ms 724 ms ae-2-79.edge1.SanJose1.Level3.net [4.68.18.78]
12 643 ms 656 ms 630 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.14
6]
13 21 ms 21 ms 30 ms 209.85.251.98
14 20 ms 19 ms 21 ms nuq04s01-in-f147.1e100.net [74.125.19.147]
Trace complete.
This seems to also be impact my teleworking ability. My companies data center is in Irvine, Ca and i'm getting VERY high latency to our corporate firewall. The hops jump inside alter.net's network which is Verizon business's network.
Please fix this ASAP, we have other teleworkers in the southern california area who have FIOS and are impacted by this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im having this same problem for a week and I also live in Chino hills
My ping to the Philadelphia server is 888ms with a jitter of 68ms on pingtest.net. But when i ping the San Francisco server, its perfectly "normal" with around 20-30 ms.
http://www.pingtest.net/result/1765466.png
My friend who also has fios lives about 500ft from me and in Chino hills. He pings 126ms to the Philly serve in comparison to my 888.
This is my tracert to google.com
Tracing route to www.l.google.com [74.125.19.106]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms myrouter.home [192.168.1.1]
2 5 ms 14 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 9 ms 9 ms 8 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 9 ms 9 ms 9 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 8 ms 9 ms 9 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6 795 ms 759 ms 817 ms 0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
7 786 ms 10 ms 854 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.
129]
8 13 ms 17 ms 833 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1
16]
9 24 ms 29 ms 24 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 21 ms 19 ms 19 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
11 18 ms 19 ms 19 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
12 22 ms 17 ms 17 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.14
6]
13 816 ms 800 ms 730 ms 209.85.251.98
14 20 ms 26 ms 19 ms nuq04s01-in-f106.1e100.net [74.125.19.106]
Whats strange is that my friend gets a very similar tracert with the high MS on certain hops. But his general internet speed is "fine"
Is there any fix to this yet? or _soon_
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!