I've been experiencing this problem for about a month now and it's quite frustrating as I am unable to raid anymore due to this issue. I've been a Verizon customer for 3-4 years, and I've never had any issue with this game ever since a month ago when I would lag really bad in-game while trying to raid with substantially good ms/fps. I've called both Blizzard and Verizon tech support to figure out the problem but to no avail. Here is my tracert during the period of me lagging in the raid:
Tracing route to 199.107.24.233 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 31 ms 31 ms 31 ms 10.1.78.1
3 31 ms 31 ms 33 ms P9-0.WASHDC-LCR-07.verizon-gni.net [130.81.136.100]
4 32 ms 31 ms 31 ms so-3-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.29.0]
5 36 ms * * 0.xe-7-0-0.XL3.IAD8.ALTER.NET [152.63.34.201]
6 31 ms 44 ms 32 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]
7 33 ms 34 ms 34 ms 192.205.36.141
8 46 ms 45 ms 47 ms cr2.wswdc.ip.att.net [12.122.81.250]
9 46 ms 45 ms 47 ms cr2.n54ny.ip.att.net [12.122.3.37]
10 41 ms 39 ms 43 ms cr84.n54ny.ip.att.net [12.122.115.94]
11 40 ms 41 ms 41 ms gar20.n54ny.ip.att.net [12.122.130.237]
12 40 ms 40 ms 39 ms 12-122-254-114.attens.net [12.122.254.114]
13 40 ms 39 ms 41 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
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.
If anyone is experiencing this same issue or can offer some help, plz reply.
Ever since Blizzard patched World of Warcraft a few months ago, it seems a lot of people are reporting trouble with the game. I don't know why other than it's throtting/DPI gone horribly wrong on some ISPs (Games use UDP Data? What's hard about that, honestly? Wireshark has no issue picking apart the data, and you can see it's WoW). Your Trace route looks fine despite what looks to be intentional packet dropping at 152.63.34.201.
Yeah, I spoke to a supervisor for verizon today and he said this is the first time they heard about this issue for some reason and I'm the first one to report it. I'm beat out of idea on what to do to fix the issue, it only happens to me while im raiding though, outside of raiding, I'm usually fine. I dunno know if it could be like what Blizz posted which is the way they changed the traffic flow to the server that's causing the issue or is it on my end.
For the most part, that is really all I can think of. If your latencies aren't changing any more than a few milliseconds pinging a site such as Google, it's either data prioritization as I mentioned, or perhaps if the game works similar to Source Engine games, rates are simply too low for the amount of activity taking place on the server. Additionally, could be an AT&T issue as well since BattleNet tends to be hosted on their backbone. AT&T isn't well known for giving peering agreements the same amount of traffic prioritzation over their own network traffic/customers.
so basically I'm **bleep** out of luck till Blizz somehow fixed this huh?
As far as I know, the problem with the lag could be with anyone so I can't point the problem as being to anyone. For me to personally figure out what the issue is, I would need access to the routers en-route to see if something is being done with the data that shouldn't be. For now, I suppose it's probably a good idea to ask around on the Blizzard Forums as well, to see if anyone has an idea who has Verizon as well as an ISP.
Take a look at this thread, it has a bit more info on your issue.
Start a new topic or ask questions in the open forum.
