Hi!
Some of you complain about the rather slow operation of Elten - a problem that I cannot reproduce and which does not seem to occur in Poland.
Can I ask you for information about your location and ping time to elten.link? The issue is probably related to the distance, but I would like to confirm it and, based on it, consider whether we have any options for workarounds.

this was obtained from seedy 360's networking tool t2000.
Ping results.

Hostname: elten.link.
IP address: 51.83.158.234.
Packet size: 64 bytes.
Packets sent: 10.
Packets received: 10.
Jitter: 21488 milliseconds.
Packet loss: 0%.
Minimum round trip time: 189 milliseconds.
Maximum round trip time: 270 milliseconds.
Average round trip time: 201 milliseconds.

this is the results for elten-net.eu in case they are different.

Ping results.

Hostname: elten-net.eu.
IP address: 51.83.158.235.
Packet size: 64 bytes.
Packets sent: 10.
Packets received: 10.
Jitter: 10963 milliseconds.
Packet loss: 0%.
Minimum round trip time: 187 milliseconds.
Maximum round trip time: 233 milliseconds.
Average round trip time: 195 milliseconds.

You can also ping using embedded tool in Tools section probably it's named Network test or something similar. I'm using Elten in Polish so can't give proper name.

Not this time. It's not a clear ping. It will give you server response time, that is useful, but it's not only a ping, but also request process time included in it.
-- (daszekmdn):
You can also ping using embedded tool in Tools section probably it's named Network test or something similar. I'm using Elten in Polish so can't give proper name.


--

location cologne, germany
network utilities
Ping summary of elten.link:80:
Minimum: 28.51 MS
Maximum: 51.27 MS
Average: 35.445 MS

Here's what I got from running a session refresh test with the speed test thing under tools.

Average time: 172ms
Minimum time: 150ms
Maximum time: 286ms
Errors count: 0

1. 172ms
2. 161ms
3. 151ms
4. 152ms
5. 150ms
6. 172ms
7. 286ms
8. 154ms
9. 152ms
10. 172ms

Average time: 58ms
Minimum time: 40ms
Maximum time: 80ms
Errors count: 0

1. 72ms
2. 79ms
3. 41ms
4. 63ms
5. 44ms
6. 40ms
7. 52ms
8. 66ms
9. 80ms
10. 43ms

For windows Users, i recommend conducting 2 tests. one is the usual ping, and the second, is more faithful to the not ideal network conditions.
test 1
Enter your console of choice (cmd, powershell) and type:
ping -n 20 elten.link

test 2:
ping -n 50 -l 512 elten.link
where N is the number of packets and L is the packet length.
Setting N between 20 and 100 allows for catching a bit more anomallies and instability than usual 4 or 10 packets provided by default.

The results of the first ping were between 30 and 33 ms, which still is ok.
The results of the second ping were also like that.

Now this is old, but dead already. Tbh knew it. Just a small difference in ping and suddenly elten is fast? It doesn't make sense at all.