High Ping after update 1.3.1

I played Last Epoch all seasons and NEVER had ms Problems with EU West and after the Update 1.3.1 i cant play anymore my ms is ALWAYS 140+ ms and my normal ms is like 20-25.

I tried everything like : changing preffered server and restart the Game , check files for damaged ones and stuff i restarted my router and all that but i dont know what to do anymore really.

Has anyone an Idea pls ?

3 Likes

Hi, I have the exact same issue.

29.08 Update: The problem seem to be worse with more players online. Ping was almost to normal on thursday night (~50-60 ms)and is now worse than ever (> 180 ms). Based on that I am not assuming a problem on my end or ISP.

I can confirm that US east seems to have better ping from Germany than EU west which makes no sense to me.

Additionally in some monoliths there are no problems: Age of Winter for example.

2 Likes

yep can confirm it happend after the update, before constantly 30ms

1 Like

Same issue. Better Ping on US West then EU West, playing from germany. Isn’t fun playing with a ping between 120-150 ms.

1 Like

Same problem here. End of time ping is fine with 20ms. But every Monolith is 140ms…

3 Likes

Same here. Never had any problems with ping before. But since the patch, it’s constantly at 150. When I use VPN, the ping is at 30. Without VPN, it’s currently unplayable.

1 Like

Same here.

1 Like

Same here. Since 1.3.1 EU West ist nearly unlpayable. I am from Germany and have better ping in US East then in EU West!

1 Like

Same here. My normal Ping is 12-15 and now 120-142. Its like PoE in the first 2 weeks. Unplayable

After a bit of research, it looks like a peering issue, specifically when routing goes through German providers, especially Telekom. That explains why, for example, only the EU gateway and particularly German users seem to be affected, and why a VPN bypasses the issue (different routing or peering). Unfortunately, these are well-known problems that we also saw in games like World of Warcraft or Path of Exile, though I thought those darker times were long gone. The fact that the issues started with the second-to-last patch was probably just a coincidence.

Since not many users seem to be affected, I fear the matter will just be ignored and the season is pretty much over for me. I have no motivation to pay for a VPN or check daily if the situation has changed.

A shame, I was having quite a lot of fun with the season so far and had hoped it would last a bit longer. Currently playing Flay and the rubberbanding in particular is just really frustrating. Maybe next time.

Linked an older POE-Post which described to Problem back in 2023. It’s in german, so pls use ChatGPT for a translation if interested.

Yeah, this has been an issue for a while now with EU services. Kinda funny how upon login it tells you that you are supposed to have 18ms ping and instead you get 135ms.
I assume unless we get more people to be loud about this we cant expect any meaningful changes which will eventually to some players just leaving and not coming back. And rightfully so.

1 Like

I agree that it could be a routing issue of german providers ( Telekom) too.
But the issue accurs excactly with the release of 1.3.1 . I had no problems before the patch. When the patch went live i made a break of max. 45 mins, in which i downloaded and installed the patch. When i get back online the problem was there.

Maybe coincidence, maybe a problem with the update of the EU Servers.

Anyways the EU Server Hosting Partner of EHG has to solve it.

EDIT: The problem seems solved. I am playing since 1h now on EU West with a ping of 10ms!

1 Like

from release to the point of Patch i never had any problem, and i´m Connecting from Germany and with Telecom. Never had any Issuse in PoE. but after that update something is off.

Just logged in and nope not solved for me 140-200ms ping in Monos

Sadly i must confirm that the problem is back.
At least i had 1,5 hours of fluid gameplay for today :disappointed_relieved:

1 Like

Only underscores that it’s probably a peering issue. As long as the respective node isn’t overloaded, the traffic can very well pass through “normally,” which explains why it works intermittently. That could indeed be related to the patch; I suspect the instances are each served by different server clusters, which don’t necessarily have to come from the same network. It’s possible they changed something in the code regarding how the creation of instances is distributed or managed. But that’s just a rough theory.

That said, I no longer have any problems when I use my employer’s VPN, which makes peering all the more likely.