This problem occures again and again, especially after special events where new players rush the servers and player numbers go up. Recently lots of servers show the "crowded" tag. In the past the "bad-guy-routing-knot" was "lease.web", now it's "msn.net" at hop 6 and after. Please buy enough traffic rights at last and take care that they fullfill their contracts. My provider is the german Telekom and game play was utterly impossible yesterday at sunday evening, main play time. Loading screens and reconnecting every few minutes made even afk life skilling impossible. 

Target Name: 20.76.13.192
IP: 20.76.13.192
Date/Time: 19.12.2023 10:43:33 - 19.12.2023 10:53:33

Hop Sent PL% Min Max Avg Host Name / [IP]
1 106 0 0,69 3,36 1,12 fritz.box [192.168.178.1]
2 106 0 1,85 38,71 4,72 p3e9bf3c3.dip0.t-ipconnect.de [62.155.243.195]
3 106 0 8,69 27,66 9,97 f-ed11-i.F.DE.NET.DTAG.DE [217.5.116.162]
4 106 0 8,34 20,23 9,37 f-ed11-i.F.DE.NET.DTAG.DE [217.5.116.162]
5 106 0 7,54 94,83 20,87 80.157.131.138 [80.157.131.138]
6 106 49 8,54 68,11 13,76 ae22-0.icr01.fra23.ntwk.msn.net [104.44.230.16]
7 106 67 17,14 165,76 26,75 be-100-0.ibr01.fra23.ntwk.msn.net [104.44.20.186]
8 106 8 17,37 132,68 27,12 be-2-0.ibr04.bl7.ntwk.msn.net [104.44.7.77]
9 106 0 16,52 78,53 20,55 ae104-0.icr03.ams21.ntwk.msn.net [104.44.23.231]
10 106 100 0 0 0 20.76.13.192 [20.76.13.192]

Routing is decided by your ISP. You would need to ask Telekom to fix this or use a VPN which has its own routing.

Ehm, nope. Routing is much more complex. It's not my first packet loss incident in an MMO and to hear this bullshit again in 2023 just makes me sad. 

What bullshit?
You mean the bullshit, your ISP is resonsible for the routing? Because that's no bullshit, it's 100% true!

Or the bullshit, you can change your routing by using a VPN? Because that's also no bullshit and 100% true!

PA can't do anything for you to fix this problem!

Only the telekom can help you, or you could help your self by using a VPN.

And for the 100% package loss at the last hop, it's because the server does not allow ping requests.

PS: I'm also from germany and hve 0 package loss. But I also have a different provider (netcologne).

"And for the 100% package loss at the last hop, it's because the server does not allow ping requests."

This is old knews, I already know that. It's when your pings bounce onto a firewall. 

Your understanding of routing is still bullshit though. 

It seems as if there was some fast solution for enforcing the peering between traffic borders of ISP providers. 

Thanks, looks much better. Ping graph is for routing connection at 7:45 PM CET - prime time - to a pretty crowded Kama5 BDO server. 

Target Name: 20.76.13.195
IP: 20.76.13.195
Date/Time: 20.12.2023 19:29:55 - 20.12.2023 19:39:55

Hop Sent PL% Min Max Avg Host Name / [IP]
1 135 0 0,61 10,43 1,17 fritz.box [192.168.178.1]
2 135 0 1,75 34,67 3,99 p3e9bf3c3.dip0.t-ipconnect.de [62.155.243.195]
3 135 0 8,74 28,04 9,98 f-ed12-i.F.DE.NET.DTAG.DE [217.0.195.185]
4 135 0 8,40 20,95 9,58 f-ed12-i.F.DE.NET.DTAG.DE [217.0.195.185]
5 135 0 8,65 100,76 14,80 62.157.250.70 [62.157.250.70]
6 135 0 8,13 42,32 12,42 ae31-0.icr02.fra21.ntwk.msn.net [104.44.230.18]
7 135 1 14,08 150,36 17,98 be-122-0.ibr02.fra21.ntwk.msn.net [104.44.23.109]
8 135 0 14,06 143,11 20,51 be-8-0.ibr02.ams30.ntwk.msn.net [104.44.28.123]
9 135 0 13,66 63,06 20,44 ae122-0.icr02.ams30.ntwk.msn.net [104.44.22.224]
10 135 100 0 0 0 20.76.13.195 [20.76.13.195]

So long and take further care for your "whales" :-)