Insane lag for some?

[Granger]

Most likely they are on a provider with a bad routing toward the server, leading in packet loss, leading to retransmits or disconnects.

In case you please execute the following in a cmd.exe (or whatever works for your system):

Code: Select all

ping game.havenandhearth.com -n 100

For my system this results in

Code: Select all

Ping wird ausgeführt für ansgar.seatribe.se [213.239.201.139]
Antwort von 213.239.201.139: Bytes=32 Zeit=42ms TTL=53
Antwort von 213.239.201.139: Bytes=32 Zeit=42ms TTL=53
[... 96 more of them ...]
Antwort von 213.239.201.139: Bytes=32 Zeit=44ms TTL=53
Antwort von 213.239.201.139: Bytes=32 Zeit=43ms TTL=53

Ping-Statistik für 213.239.201.139:
    Pakete: Gesendet = 100, Empfangen = 100, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 41ms, Maximum = 47ms, Mittelwert = 42ms


In case you see lost packets (underlined part) or highly fluctuating roundtrip times: you have a problem reaching the server, complain at your ISP or fix your local network.

[Ukhata]

trust me, its hetzner.de

they are a FILTHY bad internet relay.
its them.

just tough it out for a few days, and it should pass.

[boreial]

getting back from ping

[code][/code]Pinging ansgar.seatribe.se [213.239.201.139] with 32 bytes of data:
Request timed out.
Reply from 213.239.201.139: bytes=32 time=177ms TTL=45
Request timed out.
Request timed out.
Reply from 213.239.201.139: bytes=32 time=166ms TTL=45
Reply from 213.239.201.139: bytes=32 time=170ms TTL=45
Reply from 213.239.201.139: bytes=32 time=185ms TTL=45
Reply from 213.239.201.139: bytes=32 time=179ms TTL=45
Reply from 213.239.201.139: bytes=32 time=174ms TTL=45
Request timed out.

Ping statistics for 213.239.201.139:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 185ms, Average = 175ms

[Ukhata]

do a tracert (trace route) makes more sense for lag instead of lost pings.

[Granger]

trust me, its hetzner.de

they are a FILTHY bad internet relay.
its them.

They are a hosting company, not a relay.

do a tracert (trace route) makes more sense for lag instead of lost pings.

In case you have packetloss you'll have TCP retransmits, they'll give you lag for sure.
Enough lost packets and you'll have TCP disconnects.

As I have a server there I'm currently doing diagnostics from that end...

[Ukhata]

trust me, its hetzner.de

they are a FILTHY bad internet relay.
its them.

They are a hosting company, not a relay.

true, but my connection to haven and hearth is always routed over 2-4 Hetzner routers.
which also makes them a relay no?

[jorb]

This might be better as comments in the server status thread. Not sure it is a bug per se.

[Granger]

trust me, its hetzner.de

they are a FILTHY bad internet relay.
its them.

They are a hosting company, not a relay.

true, but my connection to haven and hearth is always routed over 2-4 Hetzner routers.
which also makes them a relay no?

In my experience hetzner reacts quickly in case you point them towards problems within their system.
Since you act as having plenty of technically expertise: feel free to do so.

[whiskeypete]

trust me, its hetzner.de
they are a FILTHY bad internet relay.
its them.

Hetzners gonna Hetz.

[loftar]

trust me, its hetzner.de

they are a FILTHY bad internet relay.
its them.

just tough it out for a few days, and it should pass.

It is true that Hetzner's routers do act up a bit every once in a while, but when they do, it's seldom for more than a few minutes. There are also many cases where the link between Hetzner and the client is bad. That particularly tends to be the issue when the problem is more persistent.