I have an ongoing problem with lost packets and high latency and for the past few weeks checked my network/pc and with my provider, no issues there

I am in Australia, so I am used to a fairly high latency (300-400ms) but have a very good ISP and a good connection. Other sites in Germany/Europe I ping show that my connection is working as expected, only uthgard.org has consistently a really bad latency (usually 500+) and some packet loss. Today packet loss is even worse than normal and it would great if you could consider looking into this. My connection to Uthgard1 was always ok, latency as expected but no packet loss.

thanks

>>>
>ping web.de

Pinging web.de [82.165.229.138] with 32 bytes of data:
Reply from 82.165.229.138: bytes=32 time=343ms TTL=232
Reply from 82.165.229.138: bytes=32 time=339ms TTL=232
Reply from 82.165.229.138: bytes=32 time=346ms TTL=232
Reply from 82.165.229.138: bytes=32 time=345ms TTL=232

Ping statistics for 82.165.229.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 339ms, Maximum = 346ms, Average = 343ms

>ping uthgard.org

Pinging uthgard.org [138.201.93.202] with 32 bytes of data:
Reply from 138.201.93.202: bytes=32 time=520ms TTL=49
Reply from 138.201.93.202: bytes=32 time=529ms TTL=49
Reply from 138.201.93.202: bytes=32 time=515ms TTL=49
Reply from 138.201.93.202: bytes=32 time=530ms TTL=49

Ping statistics for 138.201.93.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 515ms, Maximum = 530ms, Average = 523ms

>ping uthgard.org

Pinging uthgard.org [138.201.93.202] with 32 bytes of data:
Reply from 138.201.93.202: bytes=32 time=517ms TTL=49
Request timed out.
Reply from 138.201.93.202: bytes=32 time=523ms TTL=49
Reply from 138.201.93.202: bytes=32 time=528ms TTL=49

Ping statistics for 138.201.93.202:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 517ms, Maximum = 528ms, Average = 522ms

>ping web.de

Pinging web.de [82.165.230.17] with 32 bytes of data:
Reply from 82.165.230.17: bytes=32 time=361ms TTL=231
Reply from 82.165.230.17: bytes=32 time=355ms TTL=231
Reply from 82.165.230.17: bytes=32 time=352ms TTL=231
Reply from 82.165.230.17: bytes=32 time=341ms TTL=231

Ping statistics for 82.165.230.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 341ms, Maximum = 361ms, Average = 352ms

>ping spiegel.de

Pinging spiegel.de [62.138.116.25] with 32 bytes of data:
Reply from 62.138.116.25: bytes=32 time=347ms TTL=230
Reply from 62.138.116.25: bytes=32 time=347ms TTL=230
Reply from 62.138.116.25: bytes=32 time=341ms TTL=230
Reply from 62.138.116.25: bytes=32 time=340ms TTL=230

Ping statistics for 62.138.116.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 340ms, Maximum = 347ms, Average = 343ms

>ping uthgard.org

Pinging uthgard.org [138.201.93.202] with 32 bytes of data:
Reply from 138.201.93.202: bytes=32 time=523ms TTL=49
Request timed out.
Reply from 138.201.93.202: bytes=32 time=522ms TTL=49
Request timed out.

Ping statistics for 138.201.93.202:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 522ms, Maximum = 523ms, Average = 522ms
<<<

for the past hour or so I am completely unable to connect (despite other german websites being fast(ish) as usual), seems nobody else has that problem as there are no other posts on this forum ... so its probably a Australia thing ... DNS possibly?

cheers

Has it always been this way or just recently?

Note that you should also be pinging server.uthgard.org instead of uthgard.org. But since both servers are hosted at the same hoster, their latency is probably rather similar.

Not really sure what we can do about it though

Ping from Sydney has been terrible consistently:
https://drive.google.com/file/d/0BxOV8j ... p=drivesdk

its much better today! pings around 390ms, no packet drops! its a bit weird I brought it up yesterday and its much better today... initially I thought Kroko fixed it hehe

Vlalkor wrote:Has it always been this way or just recently?

I only realized its bad when the beta started, compared to Uth1 it was certainly more laggy.
Initially I thought Kroko was messing with the server but it always stayed around that 550ms latency mark.
Yesterday was the worst day, with considerable packet loss. But, as mentioned above, I'd say its nearly back to Uth1 performance now, great!

TheKrokodil wrote:Note that you should also be pinging server.uthgard.org instead of uthgard.org. But since both servers are hosted at the same hoster, their latency is probably rather similar.

Not really sure what we can do about it though

Ping from Sydney has been terrible consistently:
https://drive.google.com/file/d/0BxOV8j ... p=drivesdk

edit: the pings your are showing is what I am used to, not great but playable (also tried server.uthgard.org, no difference), but the pings I had up to today were around the 550ms range, so considerably worse, adding to that the packet loss yesterday ... maybe there were some backbone shenanigans going on between your ISP/hoster and Australia since it seems fixed today

since other german sites are fine I guess it has to do with the backbone providers used by your ISP/hoster, maybe they took some of the packets the long way round ... if the problem comes back I'll do a traceroute

thanks for your feedback

cheers

the 'fix' was only temporary it seems ... below some tracerts
it seems very much like the domain hetzner.de is slowing things up considerably ... that is your hoster?

certainly weird, less hops but still considerably slower pings for server.uthgard.org
I guess that would affect most traffic from AsiaPac ... maybe your hoster does not like Asia?

from experience I know that with a ping of around 350ms I can play RvR ... badly ... but around 550ms no sense even trying ... even PvE is so laggy I can hardly play ...

<<<
>tracert web.de

Tracing route to web.de [82.165.229.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 9 ms 8 ms 9 ms lo0.lns20.syd4.on.ii.net [150.101.32.75]
3 8 ms 8 ms 8 ms xe-11-2-1.cr1.syd4.on.ii.net [150.101.35.11]
4 9 ms 8 ms 9 ms ae5.br1.syd4.on.ii.net [150.101.33.48]
5 155 ms 155 ms 155 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
6 197 ms 197 ms 197 ms xe-0-7-0-7.r01.lsanca20.us.bb.gin.ntt.net [204.1
.253.45]
7 320 ms 313 ms 313 ms ae-17.r01.lsanca07.us.bb.gin.ntt.net [129.250.4.
207]
8 189 ms 189 ms 189 ms ae-3.r23.lsanca07.us.bb.gin.ntt.net [129.250.4.1
06]
9 226 ms 226 ms 226 ms ae-6.r22.asbnva02.us.bb.gin.ntt.net [129.250.3.1
88]
10 225 ms 225 ms 225 ms ae-0.r23.asbnva02.us.bb.gin.ntt.net [129.250.3.8
5]
11 313 ms 313 ms 313 ms ae-2.r25.amstnl02.nl.bb.gin.ntt.net [129.250.6.1
63]
12 311 ms 310 ms 310 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.1
59]
13 306 ms 305 ms 305 ms ae-2.r03.londen01.uk.bb.gin.ntt.net [129.250.3.8
]
14 320 ms 320 ms 320 ms 212.119.29.78
15 343 ms 346 ms 346 ms xe-0-1-1.bb-a.fra3.fra.de.oneandone.net [212.227
.120.22]
16 343 ms 342 ms 343 ms ae-7-0.bb-a.tp.kae.de.oneandone.net [212.227.120
.226]
17 342 ms 341 ms 341 ms ae-1-0.gw-diste2-a.bs.kae.de.oneandone.net [212.
227.121.212]
18 340 ms 339 ms 339 ms bs.web.de [82.165.229.138]

Trace complete.

>tracert server.uthgard.org

Tracing route to server.uthgard.org [5.9.152.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 79 ms 74 ms 75 ms lo0.lns20.syd4.on.ii.net [150.101.32.75]
3 72 ms 73 ms 73 ms xe-11-2-1.cr1.syd4.on.ii.net [150.101.35.11]
4 230 ms 217 ms 221 ms ae5.br1.syd4.on.ii.net [150.101.33.48]
5 261 ms 264 ms 265 ms te0-0-0-0.br1.hkg2.on.ii.net [150.101.33.199]
6 251 ms 254 ms 257 ms te1-1-0.bdr1.sin1.on.ii.net [150.101.33.222]
7 258 ms 257 ms 261 ms 33891.sgw.equinix.com [27.111.228.116]
8 548 ms 554 ms 548 ms ae6-2090.fra20.core-backbone.com [80.255.15.153]

9 555 ms 546 ms 552 ms core-backbone-100g-fra.hetzner.de [80.255.15.122
]
10 550 ms 557 ms 549 ms core1.hetzner.de [213.239.245.9]
11 604 ms 602 ms 610 ms 213-239-229-80.clients.your-server.de [213.239.2
29.78]
12 601 ms 595 ms 599 ms ex9k1.rz19.hetzner.de [213.239.229.54]
13 555 ms 558 ms 563 ms server.uthgard.net [5.9.152.140]

Trace complete.
>>>

Not really sure what we can do about it

TheKrokodil wrote:Not really sure what we can do about it

yeah, no worries, wasn't expecting anything being possible to be done about it ... just hoping

cheers