Wow51900319

Well, I got back to WoW with classic, and it didn’t take long to remember why I left.
Happens highly irregularly; sometimes it can take hours to show up, sometimes it happens every couple minutes.
I’ve done all the usual guides, MTRs as follows:
185.60.112.157

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 16 1065 903 0 3 2105 1
46.59.117.235 1 1697 1696 1 3 1591 18
a444-vast-gw.bahnhof.net 1 1696 1695 2 3 2085 22
h-158-174-156-158.NA.cust.bahnhof.se 1 1692 1690 1 3 2083 2
h-158-174-156-153.NA.cust.bahnhof.se 1 1692 1690 2 4 2081 27
gbg-cr3.gbg-cr4.bahnhof.net 1 1692 1690 12 14 2090 12
gbg-cr4.sto-cr2.bahnhof.net 1 1690 1688 12 14 1601 13
sto-cr2.sto-cr3.bahnhof.net 1 1690 1688 12 14 2091 13
sto-cr3.sto-tlc-er1.bahnhof.net 1 1695 1694 12 14 1602 14
PNI-bahnhof-blizzard.bahnhof.net 1 1683 1679 12 17 1602 12
ae1-br01-eqsk1.as57976.net 1 1695 1694 23 26 2104 23
et-0-0-3-br01-eqam1.as57976.net 1 1631 1621 23 61 4404 24
et-0-0-31-pe02-eqam1.as57976.net 1 1687 1684 23 29 2108 24
185.60.112.157 1 1691 1689 23 26 2107 23

185.60.114.159

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 29 798 568 0 4 1616 1
46.59.117.235 1 1702 1701 1 3 2076 2
a444-vast-gw.bahnhof.net 1 1700 1699 2 3 2081 3
h-158-174-156-158.NA.cust.bahnhof.se 1 1697 1695 1 3 2080 2
h-158-174-156-153.NA.cust.bahnhof.se 1 1697 1695 2 3 2079 2
gbg-cr3.gbg-cr4.bahnhof.net 1 1694 1692 12 14 1585 13
gbg-cr4.sto-cr2.bahnhof.net 1 1687 1683 12 14 2091 12
sto-cr2.sto-cr3.bahnhof.net 1 1691 1688 12 14 2091 13
sto-cr3.sto-tlc-er1.bahnhof.net 1 1698 1697 12 14 1588 12
PNI-bahnhof-blizzard.bahnhof.net 1 1689 1686 12 18 2093 13
ae1-br01-eqsk1.as57976.net 1 1695 1693 32 35 2112 32
et-0-0-3-br01-eqam1.as57976.net 1 1627 1615 32 70 4411 32
et-0-0-29-br02-eqam1.as57976.net 1 1661 1656 32 83 4088 34
et-0-0-3-br02-eqpa4.as57976.net 1 1687 1683 43 53 2124 44
be2-pe01-eqpa4.as57976.net 1 1691 1688 32 34 2113 32
185.60.114.159 1 1692 1689 32 35 2112 35

185.60.112.158

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 29 799 571 0 4 2109 2
46.59.117.235 1 1699 1698 1 3 1579 2
a444-vast-gw.bahnhof.net 1 1698 1697 2 3 1578 2
h-158-174-156-158.NA.cust.bahnhof.se 1 1700 1699 1 3 1579 3
h-158-174-156-153.NA.cust.bahnhof.se 1 1699 1698 2 3 1578 2
gbg-cr3.gbg-cr4.bahnhof.net 1 1696 1695 12 14 2094 13
gbg-cr4.sto-cr2.bahnhof.net 1 1693 1691 12 14 2094 14
sto-cr2.sto-cr3.bahnhof.net 1 1695 1694 12 14 1596 14
sto-cr3.sto-tlc-er1.bahnhof.net 1 1693 1691 12 14 2093 13
PNI-bahnhof-blizzard.bahnhof.net 1 1688 1685 12 18 2093 13
ae1-br01-eqsk1.as57976.net 1 1689 1686 23 26 1606 24
et-0-0-3-br01-eqam1.as57976.net 1 1624 1612 23 61 3768 26
et-0-0-31-pe01-eqam1.as57976.net 1 1692 1690 23 29 2102 25
185.60.112.158 1 1685 1681 23 25 1599 24
1 Like

yes i keep getting the same thing like you 10mins or 2hrs so random at times
followed all the tips online still the same even got a new ethernet card just in case.

Hey Laenera,

The WinMTR stats that you posted suggests that there’s an occasional problem between your PC and Router. That first line shows just that part of the journey, to your router, and it’s showing quite a lot of packet loss on all 3 tests, and a latency of up to 2 seconds. Are you using WiFi or a Powerline adapter by any chance? If so, try a direct cable connection if possible, and see if that helps your situation

WiFi, direct cable is… not really an option. Probably.
It should be noted WoW is the only game I get kicked from, though. Never had a problem with SC2 or HotS.
Are there any known issues specifically regarding this game?
If not, I’ll see what I can do about moving the computer… gonna be tough finding a spot near the router; packed room on the other side of the building and all.

It’s not really a valid exercise in logic, to compare unlike things. Even though they are made by Blizzard, and are computer games, they are still not valid comparisons as you don’t know what their connectivity protocols are.

Well, no, but I would’ve assumed Blizzard had these things more or less standardized.
Netcode is complex stuff, you don’t really wanna redo it every time you build a new game, much less apply multiple patches for every one of your games every time you find a way to improve upon it.

Hi, Laenera! o/

While reusing code is certainly not a bad idea when you want two programs to perform the same functions, each of our games has different needs. For example, Overwatch is a really fast paced game, so we want code to be really responsive. On the other hand, Hearthstone can be played relatively slowly, so we can be more lax.

That being said, I don’t have the specifics of how the netcode works in each of our games, as that’s something that only developers would know. What I can tell you is what I see in the winMTR you posted.

The first line, as Galcavon mentioned, suggests there’s an issue when connecting to your router. To put it in perspective, the best connection time to your router, which is probably just a few meters away from your computer, is 0 milliseconds, as it should be (anything over 2 milliseconds for the router usually means something is not right, as if you take that to cover a few meters, imagine how long it would take for the hundreds kilometers up to our servers).

The column Wrst (worst, obviously) shows spikes of 2109 milliseconds. That is over 2 seconds. In other words, when your PC tries to talk with your router, sometimes it takes up to 2 seconds for your router to answer, and sometimes, it doesn’t even answer (that’s what the % column indicates, the percentage of packages that don’t return from that point).

If using direct cable is not an option, then we are relatively limited, since there are many things that can interfere with a WiFi connection (I’ve even heard of someone that disconnected every time someone started the microwave in the kitchen).

Still, there are a few things we can try. First, let’s restart your router. Make sure to keep it off for at least 1 minute, and to disconnect all the devices connecting to it, before turning it back on. After a few minutes of turning it on, connect the devices one by one, waiting a few seconds every time, so it doesn’t become overloaded with access requests right away:

Then, try to flush your DNS, as this can help sometimes:

This is pretty basic, but if you still see these spikes in a winMTR after performing these steps, I would contact the router provider, as the router may be malfunctioning. But again, it’s hard to tell if your only option is WiFi.

So after much ado, I’ve managed to move my rig, and it is now plugged directly into the router.
MTRs are looking a lot better as a result… but I’m still getting 519d.

New MTRs as follows, would appreciate a quick response, as I’m not sure how long I can keep the computer here.

185.60.112.157

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 2 2029 2001 0 0 3 1
46.59.117.235 0 2140 2140 1 1 26 2
a444-vast-gw.bahnhof.net 0 2140 2140 1 1 9 2
h-158-174-156-158.NA.cust.bahnhof.se 1 2136 2135 1 1 38 1
h-158-174-156-153.NA.cust.bahnhof.se 0 2140 2140 1 1 10 2
gbg-cr3.gbg-cr4.bahnhof.net 1 2132 2130 11 12 17 12
gbg-cr4.sto-cr2.bahnhof.net 1 2135 2134 12 12 21 13
sto-cr2.sto-cr3.bahnhof.net 0 2139 2139 11 12 19 13
sto-cr3.sto-tlc-er1.bahnhof.net 1 2132 2130 11 12 21 12
PNI-bahnhof-blizzard.bahnhof.net 1 2128 2125 12 16 195 12
ae1-br01-eqsk1.as57976.net 1 2136 2135 22 24 106 23
et-0-0-3-br01-eqam1.as57976.net 0 2140 2140 22 26 131 23
et-0-0-31-pe02-eqam1.as57976.net 0 2139 2139 23 26 106 23
185.60.112.157 1 2135 2134 22 23 65 24

185.60.114.159

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 2 2046 2025 0 0 4 0
46.59.117.235 0 2128 2128 1 1 27 1
a444-vast-gw.bahnhof.net 0 2128 2128 1 1 9 2
h-158-174-156-158.NA.cust.bahnhof.se 0 2128 2128 1 1 35 1
h-158-174-156-153.NA.cust.bahnhof.se 0 2128 2128 1 1 9 4
gbg-cr3.gbg-cr4.bahnhof.net 1 2125 2124 11 12 25 12
gbg-cr4.sto-cr2.bahnhof.net 1 2120 2118 11 12 45 12
sto-cr2.sto-cr3.bahnhof.net 0 2128 2128 11 12 37 12
sto-cr3.sto-tlc-er1.bahnhof.net 1 2124 2123 11 12 53 12
PNI-bahnhof-blizzard.bahnhof.net 1 2124 2123 12 15 124 12
ae1-br01-eqsk1.as57976.net 0 2129 2129 31 33 137 38
et-0-0-3-br01-eqam1.as57976.net 0 2129 2129 31 35 136 32
et-0-0-29-br02-eqam1.as57976.net 0 2129 2129 31 35 670 32
et-0-0-3-br02-eqpa4.as57976.net 1 2078 2067 42 51 3502 45
be2-pe01-eqpa4.as57976.net 0 2129 2129 32 32 38 33
185.60.114.159 0 2129 2129 31 32 56 32

185.60.112.158

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.200.1 2 2020 1991 0 0 6 0
46.59.117.235 0 2133 2133 1 1 27 1
a444-vast-gw.bahnhof.net 0 2133 2133 1 1 10 2
h-158-174-156-158.NA.cust.bahnhof.se 0 2134 2134 1 1 33 1
h-158-174-156-153.NA.cust.bahnhof.se 0 2134 2134 1 1 18 1
gbg-cr3.gbg-cr4.bahnhof.net 1 2126 2124 11 12 46 13
gbg-cr4.sto-cr2.bahnhof.net 0 2133 2133 12 12 18 12
sto-cr2.sto-cr3.bahnhof.net 0 2133 2133 11 12 60 12
sto-cr3.sto-tlc-er1.bahnhof.net 0 2133 2133 11 12 61 12
PNI-bahnhof-blizzard.bahnhof.net 0 2133 2133 12 16 190 14
ae1-br01-eqsk1.as57976.net 0 2134 2134 22 24 124 24
et-0-0-3-br01-eqam1.as57976.net 1 2129 2128 22 26 133 38
et-0-0-31-pe01-eqam1.as57976.net 1 2126 2124 23 26 118 23
185.60.112.158 1 2129 2128 22 23 56 23

Hi again, Laenera! o/

This winMTR shows much better results indeed, but there are still some issues.

We can see a consisten 2% package loss in the first line (that should be your router), and this seems to spread down, as you can see other lines with a 1%.

The other worrying detail is that we see a lot of difference between the average and worst columns in almost every line. This means that usually, the connection to each node along the path replies quite fast, but ocasionally, it takes a while. We have a huge 3.5 seconds in the second test preceded by some other big spikes which seems to indicate some issues at some point before that node. Even on the first line we are seeing small spikes of 3-4 milliseconds.

Because some of the issues are appearing so early (the second line for example seems to have consistent spikes of 25~ milliseconds, which is bad news for such an early node), it’s hard to tell exactly where the problem is happening, but at this point I can only recommend you to check with your ISP, both about the package loss in the first line, and the spikes you are seeing in latency for every node along the path to reach our servers.