Hi, Haeldir, and thank you for this information! o/
So, a really quick explanation of what we are seeing here, so you can follow along: each line is a point or node along the path the data takes from your router to our servers. The first line is your router, the second one is a node close to you, the third one a node apparently in Amsterdam, and so for until you reach our servers in the last line.
The columns give us different data from said node. The most intereseing ones for us are % (percentage of packages sent that didn’t come back from that point), Avg (average time for packages to get there and back), and Wrst (longest or worst time for packages to get to the point and back).
With this in mind, you can see really quick that in the second line in the three tests there’s a consistent package loss (3-2%). While it may not seem too high, it can affect games like WoW or Overwatch, that are relatively sensible to these things. Notice how in the last test this spreads to every single line (which is normal. If you lose packages when reaching the first node, any node you try to reach passing by that first one will show similar results).
Now, where things get worrisome is when we start seeing between the average and the worst times, because that means that there are intermittent issues causing high latency that usually is not there, which is what you are experiencing in the game. We are always looking for the first line where this happens, as it will spread from there.
This happens in the first test in the 4th line, 80.249.208.83. You can see that the average is 32 milliseconds, which is pretty decent, but it has spikes of 115. Not terribly high, but it’s bad news.
We see the same result in the second test, again in the 4th line (same IP, so it’s the same node as before). Again, average of 33 milliseconds and spikes of 198. The next line though, ae1-br02-eqam1-as57976-net, goes up to 2419 milliseconds, or almost 2 seconds and a half. That’s a disconnection.
In the last test, the results are similar, although we see a slight spike in the Amsterdam line too, from 26 to 41. But it’s in the 4th, 80.249.208.83, where it goes up to 118, and spreads from there.
So, with this in mind, I think we can safely conclude that there’s some problem in the node with the address 80.249.208.83, which is a node in the Netherlands. There may be some issues with ae1-br02-eqam1-as57976-net, but that’s probably just spreading from the previous one.
Unfortunately, this means that neither Blizzard nor you can do anything directly about it (we can’t tell you to go and restart that node for example, like we could if the issue was your router). What you need to do in these cases is call your ISP. Explain to them the situation with this information at hand, so that they can check the node at 80.249.208.83, or notify it to the people responsible for said node. Hopefully, it can be resolved soon enough so that you and anyone else that connects to us through that node gets this resolved as soon as possible
Aaaand… this ended up being longer than expected, but hopefully this information is useful.