Guys, it’s ridiculous. How in the world WoW is the only game with such issues in spite of all the money we pay to play it. Sickening. But anyway: the issues doesn’t apply to just me, but a few other friends too (most just unsubbed without even reporting it as they knew it won’t help with anything).
It’s best to see the issue on this screenshot from PingPlotter:
https://i.imgur.com/bTit6Ml.jpeg
Up to the eighth hop - which is how far my ISP goes - things are perfectly fine. The bottom one shows the rest of the journey. And the faulty node is, as usual, under Blizzard’s supervision:
ae1-br01-eqfr5.as57976.net
It obviously won’t be fixed, as usual as well, but I just want to report it since I’m sick of bricking keys due to Blizzard’s inaptitude of handling data traffic.
It isn’t, I don’t use it. The issue is at the node I specified above, and I reached out to the traffic center owning the node (RIPE), and the reponse I got basically confirmed that there’s some issue but: this range is allocated to Blizzard and so we cannot assist you, you need to report it to them.
https://i.imgur.com/wyboGlH.jpeg
The best part? As an unrelated third-party I had my issue reviewed, checked and answered within a few hours. Blizzard should be taking notes, but then again there’s 2 new irl$ mounts, so it’s all good /s