- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been having horrible latency playing World of Warcraft. There are a lot of people on the WoW forums with the same issue and there's no solutions coming from that side.
According to many on the forums the issue seems to be affecting FIOS customers in the US, but most seem to think that according to pathpings that the issue is originating with ATT. The pathping below is from this past weekend - if it's not Verizon that's causing this, can they do anything to nudge ATT to get on the ball?
Any help is appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having the exact same problem, and will keep watching the responces you receive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same problems but only after about 7pm-11pm every night. My upload is unaffected but my download is cut to 1/10 of what it should be and my ping shoots from 65 normally to 800-1100.
I live in Long Beach, California if that helps at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i have been a FIOS customer for the last year and me and my family have been very happy so far. But within the last 2 weeks my gaming latency has exploded making it impossible to play.
I live in Murrieta CA
Here is a copy of my tracert and pathping.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Robin>tracert 206.16.119.45
Tracing route to 206.16.119.45 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 6 ms L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
3 14 ms 16 ms 16 ms G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
4 13 ms 11 ms 12 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 11 ms 11 ms 11 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 * 11 ms 11 ms 192.205.35.161
7 22 ms 28 ms 24 ms cr1.la2ca.ip.att.net [12.123.132.129]
8 28 ms 26 ms 21 ms cr2.phmaz.ip.att.net [12.122.31.190]
9 21 ms 22 ms 34 ms 12.123.206.225
10 22 ms 26 ms 22 ms 12-122-254-50.attens.net [12.122.254.50]
11 * 26 ms 24 ms mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
----------------------------------------------------------------------------------------------------------------------
C:\Users\Robin>pathping 206.16.119.45
Tracing route to 206.16.119.45 over a maximum of 30 hops
0 Robin-PC.home [192.168.1.10]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
3 G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
4 so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 192.205.35.161
7 cr1.la2ca.ip.att.net [12.123.132.129]
8 cr2.phmaz.ip.att.net [12.122.31.190]
9 12.123.206.225
10 12-122-254-50.attens.net [12.122.254.50]
11 mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Robin-PC.home [192.168.1.10]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
0/ 100 = 0% |
3 14ms 2/ 100 = 2% 2/ 100 = 2% G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
10/ 100 = 10% |
5 16ms 10/ 100 = 10% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
1/ 100 = 1% |
6 16ms 11/ 100 = 11% 0/ 100 = 0% 192.205.35.161
89/ 100 = 89% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.123.132.129]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.31.190]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.206.225
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-50.attens.net [12.122.254.50]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
Trace complete.
I'm no expert but it seems that there is excessive packet loss in the bolded areas.
Hopefully this will help resolve this issue soon before i start kicking puppies!!!!
Thnx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yup, there are a LOT of threads about this issue:
http://us.battle.net/wow/en/forum/topic/7789138947?page=1
It looks like ATT or someone else could have problems also. This is absurd now, SOMEONE needs to fix this NOW!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good, I have been scouring the web to see if anyone else has been having the same problem. I live in Temecula, CA and have been noticing for the past week and a half my 25/25 has been cut to about 5/25, though the verison home agent and box network test says everything checks out. MY latency in WoW isn't terrible bit it is noticibly erratic at times. I normally connect to my realm at about 86ms and on occasion it will shoot up to around anywhere from 150 to 400ms at times. I'm guessing the issue is out of Verizons hands and I hope it is resolved soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This problem just started up for me last night (Wed 2/6/2013). From the Blizzard tech support forum I'm not the only one.
I have a tracert available:
Tracing route to 63.240.161.189 over a maximum of 30 hops
1 1 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 6 ms 9 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.1]
3 16 ms 21 ms 19 ms G0-12-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.184.78]
4 37 ms * * ae0-0.RES-BB-RTR1.verizon-gni.net [130.81.209.114]
5 39 ms 41 ms * 0.xe-5-1-0.BR1.IAD8.ALTER.NET [152.63.37.69]
6 14 ms 17 ms 17 ms 192.205.36.141
7 36 ms 34 ms 36 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 * 65 ms 64 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 118 ms * * gar2.clboh.ip.att.net [12.122.133.197]
10 64 ms * * 12.122.251.22
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Again, like CLOCKWORK at 8:15pm PST speeds cut to 1/3 of what they should be, packet loss, latency issues etc.
Who the heck do we contact?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Blizz had posted that they're working with ISP's to resolve the issues. Not sure how this is going with Verizon since they weren't specific to what was actually being done.
A temporary fix is to get smoothping. A lot of people are saying this has helped with the latency issues. I can't say for sure how good because I haven't gone out to get it yet, but if we have issues today, then I'll likely sign up for it. The only downside is that it's a paid service ($7.50 US per month).
Hoping for some more news about how this is being fixed soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Update - they're requesting information from Verizon customers only to be posted here, so at least they'll be looking into it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm in the Dallas/Ft Worth, TX area and experiencing the exact same thing. I don't play WoW, but I do play Diablo3 occasionally and having the same issue with lags, high latency spikes (2000+ ms)...however, the problem does not affect only Diablo3. Speeds go from 30/25 to 1/25 or sometimes worse affecting anything I do online.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same issue for me a little north of los angeles.
Any time I log into Diablo 3 between 7pm and 11:30pm PST my latency starts out normal upon logging in, but by time i reach a mob in game, it spikes to 1000+ms
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 67 ms 4 ms 4 ms L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
3 14 ms 17 ms 11 ms G0-6-1-0.LSANCA-LCR-22.verizon-gni.net [130.81.138.234]
4 22 ms 10 ms 14 ms so-5-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.238]
5 17 ms 14 ms 17 ms 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 13 ms 10 ms 9 ms 204.255.168.134
7 22 ms 15 ms 11 ms cr1.la2ca.ip.att.net [12.123.132.129]
8 15 ms 29 ms 10 ms gar20.la2ca.ip.att.net [12.122.128.181]
9 15 ms 13 ms 14 ms 12.122.251.190
10 12 ms 19 ms * mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does Verizon have anything to say about this issue? It continues to be a problem since Wednesday 2/6 for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone had any luck with a resolution from either Blizz or Verizon? I've barely been able to log in the past few days and can't even access the WoW forums most of the time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@tkc wrote:Does Verizon have anything to say about this issue? It continues to be a problem since Wednesday 2/6 for me.
The Verizon Community Forums is where customers help other customers.
If you need assistance for specific Verizon account issues, please contact us.
for trouble like this, I find front line support less helpful, and the online twitter support more helpful. if you have twitter I would DM them
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Hubrisnxs wrote:
@tkc wrote:Does Verizon have anything to say about this issue? It continues to be a problem since Wednesday 2/6 for me.
The Verizon Community Forums is where customers help other customers.
If you need assistance for specific Verizon account issues, please contact us.for trouble like this, I find front line support less helpful, and the online twitter support more helpful. if you have twitter I would DM them
I have fround the Verizon Twitter guys ESPECIALLY concerned and helpful. You directed me to them a few days ago and I have them out tomorrow for the 2nd time in one week!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good luck. Let us know how it goes. I have been in contact with the Twitter support team as well and they are going back and forth with the network team as well. Despite several calls to front line support, I've yet to get a call back on my open case from the Fiber Solutions Center...very frustrating.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is anyone still trying to resolve this issue with online gaming in California, especially in Los Angeles area? I haven't seen any other current posts(anything later than Feb 2013) regarding this latency and also high ping issues. If there is anyone who has gotten anything resolved either through Verizon tech support(which I HIGHLY doubt as I have gotten NOWHERE with them myself), please enlighten some of us who is still frustratingly dealing with this issue.
