In the last week or so I have started experiencing ~1000ms lag in the computer game World of Warcraft (as indicated by WoW's own in game "world" latency meter; the "home" latency meter remains fine).
I have played WoW for nearly a decade and have not experienced this problem until now. I tried everything I could think of from disabling all firewalls to reinstalling the game (even on other computers on my network). Everything else appears to work as before -- Youtube, Xbox, other PC games, but not WoW.
I am still able to get saturated 35 megabit downloads (for example from Blizzard Downloader), <20 ms pings from Battlefield 3, and am frequently chosen as host on Xbox peer hosted games (like Call of Duty). But WoW is borked.
I ran a traceroute to my WoW server and it turned out fine (~35ms ping max).
All I can think of at this point is that Verizon screwed up and is applying some kind of Qos/Traffic Shaping/Throttling that broke World of Warcraft for me,.
Same deal. We are located in Northern Virginia. Since the middle of June we have been experiencing the same exact symptoms as yourself. - can still get normal download speeds for the most part but have insanely high "world" latency and low "home" latency which renders WoW unplayable.
Tech support has not been helpful. Nothing in our setup has changed at all. Wondering if it's even worthwhile to have them send a tech out since it's likely (as you suggested) something Verizon is doing. Only other thought was that perhaps it was related to a tornado-producing storm we had that week - not sure where you are located.
Yes, I'm also in Northern Virginia and I did wonder whether the one of the storms might have somehow been involved. I too couldn't get customer support to believe me since synthetic benchmarks like Speedtest are coming up fine. All I can think of is that there's some kind of local area bandwidth oversubscription (possibly due to storm damage) and due to whatever weird QoS/throttling rules might be in place WoW traffic is getting whacked.
I am fairly certain that the start of the latency issues coincided with the storm on 6/13. My concern is that I do not think there is anything wrong with my line or the connection outside my house, so I don't think having Verizon send a tech out would do anything. Like yourself, speedtests tell me that I am getting the speeds I pay for. It is only latency when playing games that I see.
In addition to WoW, I am also participating in the FFXIV beta test and unfortunately seeing some issues there as well. I dont know how to approach the problem. Perhaps someone can chime in with some advice about how to approach this issue.
Hello, I've had some problems since yesterday (didn't play the day before, so not sure if it started then). I'm located in northern Baltimore.
I think I tracked it down to Verizon's network. What I did, is follow the instructions at:
https://us.battle.net/support/en/article/running-a-pathping-test
Doing this, I found that only one hop, at so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net (130.81.199.4) was losing packets. In pathping, it reported it as 5%. If I then try to ping it 100 times (in a command prompt, I do ping 130.81.199.4 -n 100), it's usually more around 11%.
I'm just guessing that since the ip name is verizon-gni.net, this is verizon's network at fault. They probably just have to go call someone in philadelphia and have them go kick the router or whatever it is. Unfortunately there doesn't seem to be a good place to report this.
I used the online chat with Tech support and they were not that helpful - they said 5% packet loss was "just fine" and started grilling me about using a wired vs wireless connection (I've tried both, but it's obvious the problem is not on my end, and I've never been able to convince a tech support person of this fact, ever, not in the past, and I didn't have the patience to try tonight).
I've conatacted Heather_VZ about this because someone suggested it, maybe she has some insider info on how to resolve these kind of things.
If you could try the above and report back, that could help our cause, if it turns out our problems are similar.
Good luck! - Aurora of Windrunner 😉
Howdy all,
We can help look into the issue for you, and find out if there is a problem with the verizon side of the network. We would like to get some info from you such as what servers you are playing on and if you can provide a pathping or traceRT to the server that would be great.
Josh B
Hi Josh, appreciate you taking the time to help!
First thing I did this evening is ping the offending address:
Ping statistics for 130.81.199.4:
Packets: Sent = 100, Received = 92, Lost = 8 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 73ms, Average = 14ms
It started out good too, I thought maybe it was fixed, but still 8% (a second 100-ping test was also 8%)
I play the Windrunner-US server, which is on the Reckoning battle group with an IP address of: 12.129.209.68
Here is a complete pathping report to 12.129.209.68 (this forum has stripped out the spaces so it's not aligned that well)
-----------------------------------------------------------------------------
Tracing route to 12.129.209.68 over a maximum of 30 hops
0 ysera.home [192.168.1.9]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.BLTMMD-VFTTP-34.verizon-gni.net [96.234.154.1]
3 G0-10-1-3.BLTMMD-LCR-22.verizon-gni.net [130.81.215.220]
4 so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.4]
5 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-238.attens.net [12.122.254.238]
14 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ysera.home [192.168.1.9]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-34.verizon-gni.net [96.234.154.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-10-1-3.BLTMMD-LCR-22.verizon-gni.net [130.81.215.220]
0/ 100 = 0% |
4 16ms 8/ 100 = 8% 8/ 100 = 8% so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.4]
0/ 100 = 0% |
5 24ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.141
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
Trace complete.
-----------------------------------------------------------------------------
The odd part is, if I ping the offending IP from my work, I get no packet loss. I don't really know how these things work that well, but perhaps that means the problem is on the path from hop 3-4 and not 4 itself. Well I guess that narrows it down to a paultry 100 miles, should be easy from there right? 🙂
Anyway, please let me know if there's anything else i can do, or if you're able to find/fix the problem.
My WoW connection has returned to normal the last few days.
I had not seen the traceroute issues that the above poster is seeing; I only ever had problems in the actual game.
For what it is worth, my WoW server is in Blizzard's Chicago datacenter, his is in the LA one.
Likewise for me. Tuesday was the first day that I saw an improvement. Not getting world lag.
Well, 130.81.199.4 seems to be fixed now, I am now getting 0 packet loss. Thanks for your time and help on this!
Start a new topic or ask questions in the open forum.
