As a reminder, please make sure you include specifics in your reports, such as:
General geographical location
Service provider
Time the issue started
As noted earlier in the thread this isn’t a problem Blizzard can address directly, but we have alerted the relevant parties and hopefully the underlying issue can be resolved swiftly.
While issues like this will often be detected automatically at the source, it’s important that you contact your service providers directly to report issues like this, as they would be in the best position to work with any carriers involved to get any problems addressed as soon as possible.
-Austria, south styria
-A1 as a provider
-The issue started yesterday, 18th november.
-I think about 09:00? Maybe earlier?
I had very bad experiences with A1 but i cannot switch providers because there is no other option where i live. So it would be cool if you (Blizzard) could make some pressure towards them in a polite way
Ok, this specific result is an ISP issue. There is 66% packet loss at Hop 8 (prs-bb2-link.ip.twelve99.net). This is a significant issue and likely a bottleneck. For this specific issue contact your ISP since this example is not on Blizzard’s side.
Been having the issue for a few weeks now. Thought first it was on my end, but I literally only have the issue on wow. Get 500-1000 world ping, everything stops for about 30 seconds before everything zooms into action. I can move, most of the time the game seems to register that I’m moving as I end up in the location I’m at when the game returns, just everyone else is frozen. Game can be fine for hours, until it hickups and it keeps happening every x minutes until its fine again. Did have issues in a dungeon just now, so here is my tracert. Located in Norway, provider NTE.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.1
2 3 ms 4 ms 3 ms 89.151.255.214.nteb no [89.151.255.214]
3 12 ms 12 ms 14 ms 217-168-93.93.ntebredband no [217.168.93.93]
4 11 ms 13 ms 12 ms 217-168-93.93.ntebredband no [217.168.93.93]
5 12 ms 12 ms 12 ms et-4-0-0.edge1.Oslo2.Level3 net [62.67.73.109]
6 31 ms 31 ms 31 ms ae1.3104.edge7.ams1.neo.colt net [171.75.8.214]
7 46 ms 30 ms 30 ms BLIZZARD-EN.edge7.Amsterdam1.Level3 net [212.72.41.90]
8 220 ms 205 ms 218 ms ae2-br01-eqam1.as57976 net [137.221.78.27]
9 * * * Request timed out.
10 30 ms 30 ms 30 ms et-0-0-0-pe04-eqam3.as57976 net [137.221.78.53]
11 30 ms 30 ms 39 ms 137.221.66.47
12 30 ms 30 ms 30 ms 185.60.112.157
The specific issue that was causing the increase in reports at the start of this topic has now been resolved and service is back to normal.
For anyone reporting issues that started more than 2 days ago, or still have issues – the cause would be unrelated and I’d recommend you check out this page for more info and troubleshooting steps:
As always though, please continue to report any persistent issues to your service provider directly.
I’ll close this topic here, so as to prevent confusion with future or other similar incidents.
