Profile of luvnest

It shouldn't fix it, correct, but I tried after getting the hint that German WoT-players have similar issues with Telekom (and the same fix worked for them) and it immediately worked for me too. So... dark magic?

In any case, it's worth a try.

I can live with the dark magic theory. Anyway thanks, will try it.

Turning off IPv6 in the settings of my router fixed the lag issue for me immediately... (ISP Deutsche Telekom)

Not sure how that is supposed to solve the problem. The CoH2 Battle Servers use IPv4, so disabling IPv6 on the client side shouldn't have any effect on this. Could you elaborate?

i still wonder how it appears from one day to another without a patch or some kind of change by the developers?!
i think the winter patch arrives next year, did i miss a changelog ?

played with some friends 3vs3 1 week ago with no problems and now i have to play with vpn because of my german Telekom internet connection ?! (which is normally the most expensive and best internet connection in germany)

good read! I'd like to add these threads for german speakers which further narrow down the problem

Telekomhilft 1

Telekomhilft 2

Telekomhilft 3

Telekomhilft 4

Telekomhilft 5

this article gives a hint why a VPN does solve this hole thing for some people.
German.
Golem Telekom Peering US


edit: and this article offers no help, but makes you feel less alone. (from End of Nov 2020)
Fifa Tournier wird zur Farce

You have to understand that this problem has nothing to do with the end points (nor relic servers or us). So relic can patch all they want it won't change the underlying problem.

By digging further into the issue, the problem lies in the peering process between the telekom backbone and the amazon web services (AWS) in NA (where relic's coh2 servers are hosted). By taking a look at the path traceroute results from the links above, we can see that packets get delayed between the junction of telekom and telia (another provider, which further transports the traffic to amazon). Apparently this junction bandwidth has been increased several times over the last months, but it's still not enough. Both parties (telekom and telia) have to negotiate bandwidths in order to settle the issue.

Using a VPN circumvents the issue. It takes a whole different path than the one described above, still through the telekom (your ISP) backbone but then somewhere else (depends on where the vpn server is located) and then from there to the amazon relic servers. Since non-telekom customers don't seem to have any issue it would theoretically suffice to use a VPN/Proxy server in germany which is located in their network. These other ISPs obviously have a better route to AWS.

So what is there to do?
1) Either wait for Telekom and Telia (or whatever transit provider is affected) to figure out their stuff
2) change provider
3) use VPN

What could Relic do?
4) Distribute their hosted servers on AWS globaly (e.g. some of the capacity in AWS in Frankfurt) so don't have to take a detour to NA all the time. This would improve the ping for alle players and avoid bottlenecks.

did you get this from coh2 console or terminal or bash (ping ...)?

try Ctrl Shift Ö (key right of L)

Working normal today

Well in that case I doubt that a few random ISPs in central europe and NA had problems and suddenly all at the same time fixed their issues. So the problem doesn't sit with the ISPs.