Describe the Issue:<br />
Persistent high latency and occasional disconnects over the last several days. The issue appears to worsen throughout the day. Typical latency is around 50-70 ms around lunchtime (CET/CEST), increases to 100-200 ms during the afternoon, and reaches 300-600+ ms during the evening. The highest spike observed was approximately 1100 ms. Other players have reported similar issues.
To rule out local network problems, I ran continuous pings to both Google IPv4 (8.8.8.8) and Google IPv6 (google.de) while playing. Even when the game reported ~400 ms latency, both remained stable at 7-9 ms with no packet loss or noticeable jitter. My connection is VDSL (approximately 227 Mbps down / 42 Mbps up).
This may indicate route congestion, peering issues, or congestion involving any DDoS/proxy infrastructure rather than a local connectivity problem.
<br />
How to reproduce:<br />
Play from South-West Germany on Telekom during European peak hours. For me, latency gradually increases from midday into the evening. Continuous pings to Google remain stable while in-game latency rises significantly.
<br />
How is it supposed to work:<br />
Latency should remain relatively stable throughout the day, similar to the ~50 ms I consistently experienced previously, without large increases during peak hours or disconnects.
<br />
Character the bug occurred on:<br />
Snori
Additional observation: when connecting through a VPN endpoint in Poland, latency immediately drops to approximately 81 ms and remains stable. Without the VPN, latency ranges from 300-600+ ms during the same period. This suggests the issue is most likely route-related rather than server performance or local connectivity.
My best guess is that there may be congestion or routing issues somewhere between Telekom and the server infrastructure, potentially involving a transit provider, peering arrangement, or any DDoS/proxy infrastructure in front of the server. I cannot determine the exact cause from my side, but the VPN test seem to show that changing the route resolves the issue.