High ping (latency) In European servers.

[Ardit]

I just got M-net and i was expected to have a normal ping in online gaming (CSGO) but i keep getting 60+ ping in German servers and its pretty same in all Europe.
I have 18mb up 1.2 down.
No one else is connected to the router when i play.
I tried both wireless and cable and nothing is using my internet except the application im running.

Is there something that can be done?

[DarkSider]

Hi,

Can you provide us a traceroute to some of the gameservers? Please also include a traceroute to a populare website - like "heise.de".

You can perform a traceroute within windows by opening the command-shell and enter the command "tracert <ip/hostname>", e.g. tracert heise.de.
Please copy the results to the forum.

regards,
Fabian

[Ardit]

Hi,

Can you provide us a traceroute to some of the gameservers? Please also include a traceroute to a populare website - like "heise.de".

You can perform a traceroute within windows by opening the command-shell and enter the command "tracert <ip/hostname>", e.g. tracert heise.de.
Please copy the results to the forum.

regards,
Fabian

Hello : Microsoft Windows [Version 10.0.18362.295]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert heise.de

Tracing route to heise.de [2a02:2e0:3fe302::]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms fritz.box [2001:a61:a61:d401:de39:6fff:fe15:64d5]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Windows\system32>

Tracing route to 155.133.230.35 over a maximum of 30 hops

1 1 ms 1 ms 2 ms fritz.box [192.168.178.1]
2 34 ms 33 ms 34 ms host-62-245-142-165.customer.m-online.net [62.245.142.165]
3 42 ms 32 ms 32 ms ae0.r3.muc2.m-online.net [212.18.6.83]
4 35 ms 35 ms 35 ms mcn-b2-link.telia.net [62.115.147.10]
5 70 ms 60 ms 61 ms ffm-bb3-link.telia.net [62.115.120.127]
6 60 ms 62 ms 60 ms war-b1-link.telia.net [62.115.135.179]
7 61 ms 61 ms 59 ms valve-ic-333070-war-b1.c.telia.net [62.115.11.23]
8 * 61 ms * valve-ic-333070-war-b1.c.telia.net [62.115.11.23]
9 * * * Request timed out.
10 63 ms 60 ms 61 ms 155.133.230.35

Trace complete.

C:\Windows\system32>tracert 146.66.154.20

Tracing route to 146.66.154.20 over a maximum of 30 hops

1 2 ms 1 ms 2 ms fritz.box [192.168.178.1]
2 34 ms 33 ms 35 ms host-62-245-142-165.customer.m-online.net [62.245.142.165]
3 38 ms 41 ms 40 ms ae0.rt-decix-2.m-online.net [212.18.6.185]
4 42 ms 39 ms 40 ms decix.valve.net [80.81.193.63]
5 * 57 ms * decix.valve.net [80.81.193.63]
6 * * * Request timed out.
7 * * * Request timed out.
8 49 ms 51 ms 50 ms 146.66.154.20

Trace complete.

Here is ping measurement ingame https://steamuserimages-a.akamaihd.net/ ... 5FF8F2B0F/

Thanks

[DarkSider]

Thanks for sharing the traceroutes. The ping to the first hop outside of your network is around 30ms. Unfortunately this is normal for some xDSL configurations on the M-Net network as some level of error correction is applied

[Ardit]

Thanks for sharing the traceroutes. The ping to the first hop outside of your network is around 30ms. Unfortunately this is normal for some xDSL configurations on the M-Net network as some level of error correction is applied

Alright
Is there anything that can be done to have a lower ping?
Otherwise ill be forced to look into an other provider because like this is a waste for me.
Thanks

[Florian S.]

Thanks for sharing the traceroutes. The ping to the first hop outside of your network is around 30ms. Unfortunately this is normal for some xDSL configurations on the M-Net network as some level of error correction is applied

Alright
Is there anything that can be done to have a lower ping?
Otherwise ill be forced to look into an other provider because like this is a waste for me.
Thanks

The problem does not exist in our network so we cannot do anything here. Contact the support of the game and send them the requested logfiles if necessary. There is no mistake on our part.

[Ardit]

Thanks for sharing the traceroutes. The ping to the first hop outside of your network is around 30ms. Unfortunately this is normal for some xDSL configurations on the M-Net network as some level of error correction is applied

Alright
Is there anything that can be done to have a lower ping?
Otherwise ill be forced to look into an other provider because like this is a waste for me.
Thanks

The problem does not exist in our network so we cannot do anything here. Contact the support of the game and send them the requested logfiles if necessary. There is no mistake on our part.

Upgrading to a 50mb vdsl from actually 18 dsl that i am will it help or not even that? Thanks

[Florian S.]

The available bandwidth has, as a rule, nothing to do with the communication time of the individual servers. It is therefore rather unlikely that this will help.

[mio2019]

So is Darksider right, that this has to do something with the xDSL configuration?
And this is m-net responsibility, right?
In this case contacting the support of the game does not make sense at all. Or how can they help in this case?

My first hop outside the network is much smaller:

Code: Alles auswählen

traceroute6 to heise.de (2a02:2e0:3fe:1001:302::) from 2001:a61:1255:d501:98f9:50af:5d21:291f, 64 hops max, 12 byte packets
 1  fritz.box  3.879 ms  4.003 ms  1.316 ms
 2  2001:a60::69:0:2:2  11.754 ms  12.324 ms  12.797 ms
 3  te0-0-2-3.c350.f.de.plusline.net  16.884 ms  15.498 ms  16.392 ms
...

[DarkSider]

Ah, now we are getting somewhere. As the IPv6 trace shows a first hop response time of only about 12ms - it might be the AFTR gateway that adds some latency.

There is an option IPv4 option for just under 5 €, so get your own ipv4 address and you don't share it with other M-Net customers.

regards,
Fabian

[mio2019]

But my IPv4 traceroute seems to be "faster"

Code: Alles auswählen

$traceroute heise.de
traceroute to heise.de (193.99.144.80), 64 hops max, 52 byte packets
 1  fritz.box (192.168.178.1)  8.005 ms  4.004 ms  1.883 ms
 2  host-62-245-142-189.customer.m-online.net (62.245.142.189)  5.938 ms  6.166 ms  6.551 ms
 3  host-62-245-142-187.customer.m-online.net (62.245.142.187)  7.127 ms  13.475 ms  8.674 ms
 4  ae0.rt-decix-2.m-online.net (212.18.6.185)  12.840 ms  13.249 ms  12.414 ms
 5  te0-0-2-3.c350.f.de.plusline.net (80.81.193.132)  14.431 ms  13.742 ms  17.739 ms
...

compared to IPv6

Code: Alles auswählen

$ traceroute6 heise.de
traceroute6 to heise.de (2a02:2e0:3fe:1001:302::) from 2001:a61:1255:d501:98f9:50af:5d21:291f, 64 hops max, 12 byte packets
 1  fritz.box  16.450 ms  3.340 ms  3.142 ms
 2  2001:a60::69:0:2:2  16.105 ms  11.663 ms  12.892 ms
 3  te0-0-2-3.c350.f.de.plusline.net  13.399 ms  13.788 ms  13.674 ms
...

and I have Dual Stack Lite.

[DarkSider]

Hi,

I was referring to your first post with this tracert:

Code: Alles auswählen

2 34 ms 33 ms 34 ms host-62-245-142-165.customer.m-online.net [62.245.142.165]

The latency of the 2nd hop (outside your network) is 34 ms which is quite high.

As you posted an ipv6 trace

Code: Alles auswählen

2  2001:a60::69:0:2:2  11.754 ms  12.324 ms  12.797 ms

where the 2nd hop has only a latency of about 12ms my guess was that the AFTR gateway might be under some kind of "load".

However just now you posted some more traces where the ipv4 connection actually has a lower latency. Maybe the AFTR-GW load changes at different times. What I also find a bit concerning:

Code: Alles auswählen

 1  fritz.box  16.450 ms  3.340 ms  3.142 ms

The reply from your router should always be a flat 1ms.

Do you use WiFi? If you do use WiFi rerun all the tests with a proper cabled setup. WiFi is also a big cause of uncertainty!

However, a latency of about 12ms to your 2nd hop is well within reasonable and technical limits!

bye,
Fabian

[Ardit]

The available bandwidth has, as a rule, nothing to do with the communication time of the individual servers. It is therefore rather unlikely that this will help.

What about Fastpath will it help? I have read some posts here in the forums that helped other people to reduce their latency.
How does it work? How can i activate it?

[mio2019]

You're right - I was using Wifi.

[DarkSider]

Ah I'm talking to two ppl sorry I didn't get this right in my last post

Fastpath is not available on all plans. I actually don't know if they still offer it with ADSL2