network lag

[blo0d]

Hi,

My tracert is:
Tracing route to 195.20.241.216 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms OpenWrt.home [192.168.1.1]
2 3 ms 2 ms 2 ms 145.236.238.211
3 4 ms 4 ms 3 ms c-ge0-22.ar1-ip3.net.telekom.hu [84.1.64.106]
4 4 ms 4 ms 4 ms 81.183.3.157
5 8 ms 15 ms 8 ms 80.157.206.192
6 21 ms 20 ms 21 ms f-eh4-i.F.DE.NET.DTAG.DE [62.154.1.86]
7 22 ms 21 ms 20 ms f-eh4-i.F.DE.NET.DTAG.DE [62.154.1.86]
8 41 ms 44 ms 43 ms 80.157.131.194
9 99 ms 100 ms 101 ms ae-9.bb-b.bs.kae.de.net.ionos.com [212.227.120.168]
10 23 ms 22 ms 50 ms port-channel-4.de-rhr-bangdsr01.oneandone.net [212.227.122.28]
11 64 ms 65 ms 64 ms 212.227.36.126
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

[[ZG] BubblesDevere]

Seems to be so low priority never gets to the end of the trace. Anyway, could you try a simple ping and see if you get any loss?

[blo0d]

i think over 12 hops ICMP is deny, so traceroute not complate, but i paste all trace.

Tracing route to 195.20.241.216 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms OpenWrt.home [192.168.1.1]
2 2 ms 2 ms 2 ms 145.236.238.211
3 3 ms 3 ms 6 ms c-ge0-22.ar1-ip3.net.telekom.hu [84.1.64.106]
4 4 ms 4 ms 4 ms 81.183.3.157
5 8 ms 9 ms 9 ms 80.157.206.192
6 21 ms 21 ms 20 ms f-eh4-i.F.DE.NET.DTAG.DE [62.154.1.86]
7 20 ms 20 ms 21 ms f-eh4-i.F.DE.NET.DTAG.DE [62.154.1.86]
8 95 ms 102 ms 101 ms 80.157.131.194
9 105 ms 105 ms 105 ms ae-9.bb-b.bs.kae.de.net.ionos.com [212.227.120.168]
10 22 ms 22 ms 22 ms port-channel-4.de-rhr-bangdsr01.oneandone.net [212.227.122.28]
11 70 ms 68 ms 65 ms 212.227.36.126
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.

[blo0d]

C:\>tracetcp.exe 195.20.241.216:27015 -p 1 -n

Tracing route to 195.20.241.216 on port 27015
Over a maximum of 30 hops.
1 2 ms 192.168.1.1
2 4 ms 145.236.238.211
3 6 ms 84.1.64.110
4 6 ms 81.183.3.60
5 10 ms 80.157.206.192
6 21 ms 217.5.114.110
7 22 ms 62.154.1.86
8 99 ms 80.157.131.194
9 * Request timed out.
10 23 ms 212.227.122.28
11 94 ms 212.227.36.126
12 26 ms 195.20.241.216
13 Destination Reached in 25 ms. Connection established to 195.20.241.216
Trace Complete.

[[ZG] BubblesDevere]

I received a response today:

It looks like there is a problem on the side of the user or the request path it takes. Have you checked the response time using a VPN for comparision? Overall it looked like the server was reached in 25 ms.

---

So please try a VPN, if not please contact you ISP with the same data you provided.

[[ZG] abracadabra]

C:\Users\abracadabra>ping 195.20.241.216

Pinging 195.20.241.216 with 32 bytes of data:
Reply from 195.20.241.216: bytes=32 time=47ms TTL=52
Reply from 195.20.241.216: bytes=32 time=45ms TTL=52
Reply from 195.20.241.216: bytes=32 time=47ms TTL=52
Reply from 195.20.241.216: bytes=32 time=46ms TTL=52

Ping statistics for 195.20.241.216:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 47ms, Average = 46ms



C:\Users\abracadabra>tracert 195.20.241.216

Tracing route to 195.20.241.216 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.0.1
2 16 ms 14 ms 11 ms 10.205.48.1
3 12 ms 9 ms 13 ms 10.242.130.144
4 14 ms 18 ms 14 ms 10.0.31.25
5 11 ms 13 ms 16 ms 10.0.50.223
6 13 ms 18 ms 14 ms ae20-0.alb2nqp7.dk.ip.tdc.net [87.53.191.250]
7 24 ms 23 ms 24 ms ae7-0.asd3nqp1.nl.ip.tdc.net [83.88.1.220]
8 53 ms 50 ms 48 ms et-0-1-0.core-ams14.as6724.net [80.249.210.180]
9 50 ms 49 ms 49 ms lo-0.bb-b.rs.ber.de.net.ionos.com [212.227.117.76]
10 * * * Request timed out.
11 53 ms 47 ms 49 ms public.gsp01-rs-ber-de.net.ionos.com [217.160.161.66]
12 50 ms 47 ms 47 ms public.gsp02-rs-ber-de.net.ionos.com [217.160.161.67]
13 * * * Request timed out.
14 * * * Request timed out.
15 46 ms 45 ms 49 ms ae-22.bb-b.fr7.fra.de.oneandone.net [212.227.120.40]
16 43 ms 41 ms 43 ms ae-14-0.bb-a.fra3.fra.de.net.ionos.com [212.227.120.148]
17 49 ms 45 ms 45 ms lo-0-0.rc-a.bap.rhr.de.net.ionos.com [212.227.117.208]
18 51 ms 53 ms 48 ms port-channel-3.de-rhr-bangdsr02.oneandone.net [212.227.121.10]
19 45 ms 45 ms 45 ms 212.227.36.126
20 46 ms 48 ms 47 ms 195.20.241.216

[[ZG] BubblesDevere]

Everything looks good

[[ZG] abracadabra]

Everything looks good

ping is twice as high as it should be
i also get lag spikes while playing which are not revealed by these tests

[[ZG] BubblesDevere]

Alright, it looks like the problem occurs between Denmask and Amsterdam exchange, however this happens just before reaching IONOS...
Could you open a ticket with that traceroute to your ISP and see what they say? I can take it further with IONOS after that.

[[ZG] abracadabra]

I contacted my ISP as suggested and got in contact with some intern who didn't understand what I was talking about. He said he would pass on the issue to the tech department but they never got back to me.
2 months later, when I run the traceroute, I get a different result:

C:\Users\abracadabra>tracert 195.20.241.216

Tracing route to 195.20.241.216 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 19 ms 14 ms 11 ms 10.205.48.1
3 9 ms 9 ms 9 ms 10.242.130.144
4 10 ms 12 ms 12 ms 10.0.31.25
5 15 ms 11 ms 11 ms 10.0.50.223
6 10 ms 17 ms 10 ms ae20-0.alb2nqp7.dk.ip.tdc.net [87.53.191.250]
7 23 ms 24 ms 27 ms ae7-0.asd3nqp1.nl.ip.tdc.net [83.88.1.220]
8 * * * Request timed out.
9 44 ms 44 ms 45 ms lo-0.bb-b.rs.ber.de.net.ionos.com [212.227.117.76]
10 44 ms 44 ms 42 ms ae-22.bb-b.fr7.fra.de.oneandone.net [212.227.120.40]
11 49 ms 42 ms 38 ms ae-14-0.bb-a.fra3.fra.de.net.ionos.com [212.227.120.148]
12 43 ms 44 ms 44 ms lo-0-0.rc-a.bap.rhr.de.net.ionos.com [212.227.117.208]
13 44 ms 43 ms 43 ms 212.227.121.227
14 44 ms 49 ms 44 ms 212.227.36.126
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.


My interpretation is that the jump in ping now occurs between the Amsterdam exchange and IONOS, and the final hop to 195.20.241.216 is never made.