Connection Issues

Support Technical Support
1

I’ve been having connection issues for the past week. After using WinMTR i found that i’m getting up to 4K ping on WoW server. I started having issues about 1 week ago on and off. Issue is worse during prime time. I bricked 2 keys today cause my connection kept lagging out. Discord is crystal clear, internet connection is fine. no lag on anything else. Everything stops moving except for me and I can’t cast anything or use skills etc. etc. here is the log:
| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 19216801 - 0 | 527 | 527 | 0 | 0 | 15 | 0 |

| 142-254-187-057infspectrumcom - 8 | 410 | 380 | 7 | 9 | 151 | 8 |

| lag-62yumaaz1401hnetopschartercom - 8 | 410 | 380 | 13 | 77 | 672 | 30 |

| lag-22yumaaz1401rnetopschartercom - 8 | 401 | 369 | 11 | 168 | 1145 | 25 |

| lag-39lsancarc01rnetopschartercom - 8 | 406 | 375 | 14 | 16 | 36 | 17 |

|lag-36lsancarc0yw-bcr00netopschartercom - 8 | 402 | 370 | 14 | 17 | 47 | 25 |

| lag-0.pr2.lax10netops.chartercom - 6 | 429 | 404 | 14 | 18 | 114 | 18 |

| 24.30.201.95 - 7 | 422 | 395 | 13 | 21 | 158 | 15 |

| ae1-br01-eqla1as57976net - 30 | 237 | 168 | 32 | 349 | 4765 | 83 |

| No response from host - 100 | 106 | 0 | 0 | 0 | 0 | 0 |

| et-0-0-0-pe01-swlv10as57976net - 8 | 402 | 370 | 19 | 21 | 62 | 21 |

| 1372211052 - 7 | 421 | 394 | 19 | 21 | 57 | 19 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

this seems to be the culprit ae1-br01-eqla1as57976net - 30 | 237 | 168 | 32 | 349 | 4765 | 83 |. I’m getting 30 - 50% packet loss

Any input would be greatly appreciated. Thank you. TOOK ALL PERIOD OUT BECAUSE I COULDN"T POST BECAUSE APPARENTLY IM POSTING LINKS. smooth brain filters.

2

Is that 8% packet loss getting out to your ISP? For reference, 1% packet loss is bad. That said I’m not super familiar with WinMTR so take my commentary with a grain of salt – more accustomed to ping/tracert.

Anyway, Discord is probably UDP (loss-insensitive) traffic, as the individual bits in voice and video are urgent but non-critical.

If there’s an issue with your route (e.g. that 30% find of yours) that’d also lead to a situation where other internet resources are fine but one (e.g. WoW) isn’t.

3

The WinMTR log i previously posted was for the US WEST servers. I ran WinMTR using US CENTRAL servers and I had no issues. Went back to USWEST and it’s the same issues I mentioned above. So why am I fine when connecting to USCENTRAL servers but not USWEST?? This makes no sense to me. I have no connectivity issues on any other games I play like CS GO, Warzone, FFXIV. All my streaming services are fine as well. I have plenty of bandwidth and the WinMTR log doesn’t seem to point to any issues on my end.

4

Yep.

Those other services, and your streaming services, are just not following the same route. Don’t forget the internet exists on physical hardware, being carried over physical media, and that the resources you’re connected to are in different physical locations.

Edit: Here’s a super simplified diagram I whipped up a few years back.

Very basic view of internet routing

So, you can envision how a failure reaching Blizzard wouldn’t affect Google or Fortnite.

3 Likes
5

The issue is the 8% packet loss right outside your router. This is on your ISP’s side. They will say there is nothing wrong, they will say everything is fine. Push the issue and force them to fix it especially since it happens during prime time. This means the nodes in your area are being overloaded and that is causing the issues you are experiencing.

1 Like
6

OK, Running more tests today, and contacting my ISP. Weird thing about all this is that I have NO issues with CS GO, FFXIV, or any other games. (OK contacted my ISP, there does seem to be an issue, they are sending someone out.) Thank you Amaelalin for the diagram it definitely helped me understand the situation better. I’ll post an update if the issue is resolved. Thank you guys for the help.

7

Hello Baudson, you’re welcome – I’m glad it was of help. :slight_smile:

Hopefully your ISP is able to help out. It’s possible that there also problems upstream, at which point all we can do is cross our fingers and hope things are sorted soon.

1 Like
8

I’ve had the same issues since Friday maintenance. I work for a ISP. Ive routed my traffic to CA through Seattle and through Salt lake City, happening on both routes. No loss from my router to Server at ISP. Mother to same realm is having the same issue. Also just ran a TW and the DK is having the issue as well. This is NOT a ISP issue. It only started right after maintenance on Friday.

9

My Tracert to Blizzard show the same thing:
9 232 ms 219 ms 220 ms et-0-0-29-br01-eqla1_as57976_net [137.221.65.0]
So the IP is Blizzards, but the country is Netherlands…why is the connection being routed overseas?

Summary

Country Netherlands
Domain blizzard.com
ASN AS57976
Registry ripe
Hosted IPs 128
ID BLIZZARD
10

Just want to chime in that I am having the exact same issue with incredibly similar results to everyone else running the traceroute, pathpings, etc.

11

Had it happen again, this time I did some experimenting. In game chat works fine, I can talk to people in the zone, and guild. NPCs and mobs in my local area no longer appear to have a functioning AI. I ran away from the area (also don’t take fall damage) and all NPCs stopped being even loaded. no interactivbles show up. I’m also able to run scripts to check how many Catalysts I have, or if I have completed quests, thus I’m obviously still being registered as being in game and on the server.
I ran to a instance portal and could see it load. I ran through and after 30mins in this state I was kicked after going through. The error was “Unknown location state” or something like that.
So this is 100% a issue on Blizzards side.

1 Like
12

Well it all makes sense now as far as why I was at 4K ping in WoW only vs. other games. I do suspect there are issues with my connection, but nowhere near bad enough to cause that kind of ping on ONE specific game. The ISP rep I spoke to today just indicated that there were some fluctuations with my signal, specifically my upload. Rep said he would send someone out to check out the line coming into my home to make sure everything is physically good. Rep stated that sometimes things happen like a squirrel chewing on a line etc. etc. That being said, what is going on with Blizzard? You’d think think they’d have the resources to eliminate issues like these.

13

I have not tested as extensively as you have (nice work, seriously), however that has been exactly my experience as well.

It has been happening sporadically and inconsistently. I can sometimes go 2 hours without an incident, and then get 2 incidents within 10 minutes. Last night it happened to me twice in a single key, and the only way I can get around it is by force quitting the game and hopping back in.

1 Like
14

Its honestly like when the Simulation stops working in Minecraft but the Rendering continues. You can’t interact with anything in the game world, and all the NPCs stop. If you go far enough the NPCs stop loading but since the Rendering part is still working the world itself continues to load.

1 Like
15

I had this same thing happen to me multiple times this morning. Game seems to partially drop me (actions, hearth, interactable objects stop working), but I remain in the game world. NPCs stop loading.

Other times I just drop entirely and have to load back into the game world. When it doesn’t drop me entirely, it almost feels like massive packet loss until things eventually just go dead entirely. Blew up some m+ keys this morning before work because of this. This just started today.

1 Like
16

Hey folks - curious if anyone on this thread is still experiencing the issue since yesterday/last night?

I did not have a single disconnect yesterday, and I’m curious if it’s the change I implemented or if Blizzard fixed something on their end with the recent maintenance window.

For the curious, I posted on Tiwtter and someone there posted an Overwatch thread where folks are having similar issues, and one guy suggested he fixed it by changing the SSID on his router, so I went ahead and did that. Just wanted to see what others were experiencing to see if that may have actually resolved it or not.

17

I haven’t had it happen since maintenance, at least not yet.

18

Oh and it was 100% on Blizzard’s side. It was occurring inside ATT/Blizzards routing network. Tracerts showed that.

1 Like
19

Yes, that was what was showing for me too on all tracert/pathping/mtrs. I suspect it was something with the maintenance but since I made a change the same day I wanted to ask here to rule that out.

20

if you’d like you can post a tracert or winmtr so we can see if it showed anything. i mean if it’s resolved then it doesn’t really matter, but most likely you’re looking at the ae1-br1-(etcetc) hop and it isn’t showing a problem even though it looks like it is.

1 Like