Latency problems, not my fault, VARIOUS WinMTR logs inside

Hi.

Some days ago, the game started to have ping spikes and volatile ping in general. I have no problem with high ping. I know limitations exist and you can't bend the laws of physics and ping will always be there due to distance and hops between my PC and your servers. But this game is unplayable if that number, high or low, is not stable enough.

It's too volatile right now and is not dependent on time of the day or anything on my side but is a roulette per instance, as your IP instances or whatever you call them. Doing MTRs to the one IP you provide is copium because even if you choose one gateway on the login menu, the map instances connect to different IPs and that explains why it doesn't depend on time of the day but is random. Sometimes you have a nice HO instance and sometimes it is a laggy one. Sometimes your HO is not laggy and when you get out of a also, not laggy one, now your HO is laggy because is a different instance with different IP. If anyone have the same problem I have, they can test this spamming new instances using the menagerie so they can get new instances fast enough to see it happening, the good and the bad instances, in a short time so is not a "perception" error.

What I did was creating some menagerie instances, checking the ping graph for instability (it's VERY obvious when it happens) to classify then as a stable or unstable instance and then used winMTR to get a sample of at least 100 packets from them as you can see them here, with the logs inside spoiler tags to help readability:

STABLES:

- 160.202.166.115:6112



- 160.202.166.126:6112



- 160.202.166.79:6112



Seems like the IPs on the range 160.202.166.* are the ones working but had one at 206.191.149.132:6112 that also worked but I have no MTR because doing this 6 times already is boring.

Now the unstables.

UNSTABLES:

- 174.127.113.158:6112



- 52.117.148.212:6112



- 192.211.48.178:6112



I also wrote 169.48.234.122:6112 , 107.155.77.26:6112 and 192.211.48.178:6112 as other IP instances failing like the others but no MTR due to the same reason of the last stable one, getting this data is boring because I should be playing your game and I can't.

The difference and the problem between stable and unstable instances in MTR is obvious and as I say, is not my fault or my ISP fault. The PC was the only thing consuming internet at the time of taking the logs, my internet connection is fiber with at least 350 Mbps download and upload speed, also tested at the time of taking the logs.

I know I don't buy 69 supporter packs each league but as a player that already has put some money in this game, I ask you to acknowledge and solve the problem that I and many others as I checked the forum, have. If there is no way to solve this soon, I still ask you to ACKNOWLEDGE it and to offer some way to make this instance choice more tight so I can end only in the instances that work as again, the game is unplayable with a ping so volatile.


Thanks a lot for your time and I will be waiting for your response here, before escalating this via email.

Bumping the thread as the problem still persist.

Bump

Had the same problem last league, and even further than last league. The biggest problem is when if happens, you literally can't play this day unless you want to lose all your maps and scarabs. Otherwise the next day everything seems to be fine, stable 30ms latency on every instance.

I have the same problem with 2 different internet providers in 2 different cities.

Did the menagerie thing. 5 of them were fine (30ms), the next one was like 3000ms. Still better than the the 30k ms+ that i had in a map.

Btw i lost connection while being in that lagged menagerie while writing this.

EDIT: I changed the gateway from frankfurt to amsterdam ajnd didnt have any problems so far. Might have been the random point where is starts working though