It's been quite a few days that's been happening now, so I'll just report in.
Italian players have been experiencing mass LD, all at the very same moment, regardless of their internet provider. We just get the first two squares red all of a sudden, and then in a matter of seconds we all LD.
Crashes are very random, they could happen once a day or never or even multiple times (I've experienced up to 4 times in one single day).

Is there something that can be done about it? I'm pretty sure it's a server issue at this point...

Juri wrote:It's been quite a few days that's been happening now, so I'll just report in.
Italian players have been experiencing mass LD, all at the very same moment, regardless of their internet provider. We just get the first two squares red all of a sudden, and then in a matter of seconds we all LD.
Crashes are very random, they could happen once a day or never or even multiple times (I've experienced up to 4 times in one single day).

Is there something that can be done about it? I'm pretty sure it's a server issue at this point...

If it were a 'server issue' wouldn't it effect ALL players, not just those from Italy? It's much more likely that a key internet node between Italy and Germany is having problems. Can you do a trace route to server.uthgard.net and see which node is causing the problems?

Traccia instradamento verso server.uthgard.net [46.4.115.53]
su un massimo di 30 punti di passaggio:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Richiesta scaduta.
3 10 ms 10 ms 10 ms 172.17.232.102
4 12 ms 11 ms 12 ms 172.17.232.73
5 22 ms 22 ms 23 ms 172.19.243.33
6 * * * Richiesta scaduta.
7 30 ms 33 ms 24 ms ae20.milano51.mil.seabone.net [195.22.205.13]
8 20 ms 20 ms 20 ms ntt-verio.milano51.mil.seabone.net [93.186.128.1
57]
9 59 ms 69 ms 69 ms ae-11.r01.mlanit01.it.bb.gin.ntt.net [129.250.2.
40]
10 59 ms 59 ms 59 ms ae-2.r24.frnkge08.de.bb.gin.ntt.net [129.250.3.1
83]
11 69 ms 69 ms 69 ms ae-13.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.
207]
12 69 ms 59 ms 59 ms 213.198.82.130
13 79 ms 59 ms 89 ms core22.fsn1.hetzner.com [213.239.245.178]
14 70 ms 69 ms 69 ms ex9k2.rz14.hetzner.de [213.239.229.118]
15 79 ms 59 ms 89 ms static.53.115.4.46.clients.your-server.de [46.4.
115.53]

Traccia completata.

Juri wrote:Traccia instradamento verso server.uthgard.net [46.4.115.53]
su un massimo di 30 punti di passaggio:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Richiesta scaduta.
3 10 ms 10 ms 10 ms 172.17.232.102
4 12 ms 11 ms 12 ms 172.17.232.73
5 22 ms 22 ms 23 ms 172.19.243.33
6 * * * Richiesta scaduta.
7 30 ms 33 ms 24 ms ae20.milano51.mil.seabone.net [195.22.205.13]
8 20 ms 20 ms 20 ms ntt-verio.milano51.mil.seabone.net [93.186.128.1
57]
9 59 ms 69 ms 69 ms ae-11.r01.mlanit01.it.bb.gin.ntt.net [129.250.2.
40]
10 59 ms 59 ms 59 ms ae-2.r24.frnkge08.de.bb.gin.ntt.net [129.250.3.1
83]
11 69 ms 69 ms 69 ms ae-13.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.
207]
12 69 ms 59 ms 59 ms 213.198.82.130
13 79 ms 59 ms 89 ms core22.fsn1.hetzner.com [213.239.245.178]
14 70 ms 69 ms 69 ms ex9k2.rz14.hetzner.de [213.239.229.118]
15 79 ms 59 ms 89 ms static.53.115.4.46.clients.your-server.de [46.4.
115.53]

Traccia completata.

It would be interesting to see what is at node 6 where the request timed out. Everything else seems fine.

The fact that all responses are dropped on step 6 normally indicates a firewall or a router which is set to ignore pings etc, the fact the rest of the hops are all sensible times and similar would make me not worry so much about that hop.

[Edit] Actually the fact that its 172.x addresses before that hop would indicate a private network, probably protected by a firewall, so that makes sense. Are you at a University or something?

Here is my tracert to Uthgard. Everything is working fine.. I never had any problems at all with my connection to uthgard.

Sporer rute til server.uthgard.net [46.4.115.53]
over et maksimum af 30 hop:
1 <1 ms <1 ms <1 ms 172.18.32.1
2 * * * Anmodning fik timeout.
3 * * * Anmodning fik timeout.
4 * * * Anmodning fik timeout.
5 * * * Anmodning fik timeout.
6 * * * Anmodning fik timeout.
7 * * * Anmodning fik timeout.
8 * * * Anmodning fik timeout.
9 * * * Anmodning fik timeout.
10 * * * Anmodning fik timeout.
11 * * * Anmodning fik timeout.
12 * * * Anmodning fik timeout.
13 * * * Anmodning fik timeout.
14 19 ms 19 ms 19 ms static.53.115.4.46.clients.your-server.de [46.4.
115.53]
Sporing fuldført.

Please use WinMTR trace to server.uthgard.net and send me the output via PM after about 1000 packets when you have strong network problems.

Define "strong network problems" please. I never have any problem whatsoever. Should i use WinMTR while I am crashing?

[Edit] Actually the fact that its 172.x addresses before that hop would indicate a private network, probably protected by a firewall, so that makes sense. Are you at a University or something?

No.

Juri wrote:Define "strong network problems" please. I never have any problem whatsoever. Should i use WinMTR while I am crashing?

[Edit] Actually the fact that its 172.x addresses before that hop would indicate a private network, probably protected by a firewall, so that makes sense. Are you at a University or something?

No.

Then whatever provider you are using is using private network addresses on their platform, either way hop 6 looks like its the handoff to the real internet so it could be some kind of security feature that's dropping the traceroute.

Anyway general times look fine, as Blue said, provide the winmtr results and I'm sure he can pass that on to Hetzner if it looks like its an issue on their end.