Need Evidence Report: Recurring high ping on Skial 2fort EU 24/32/64 players

[Mister Jo.]

Summary Recurring high ping on Skial 2fort EU 24/32/64 players

Detailed Explanation
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| speedport.ip - 0 | 88 | 88 | 0 | 0 | 1 | 0 |
| 172.27.99.1 - 90 | 20 | 2 | 0 | 9 | 11 | 7 |
| 172.24.115.1 - 0 | 88 | 88 | 7 | 8 | 16 | 7 |
| 195.29.224.33 - 0 | 88 | 88 | 8 | 9 | 16 | 8 |
| htr11-hst12.ip.t-com.hr - 0 | 88 | 88 | 12 | 13 | 17 | 16 |
| hvz12-htr11.ip.t-com.hr - 0 | 88 | 88 | 15 | 16 | 20 | 18 |
| mvz-ts-10-hvz12.ip.t-com.hr - 0 | 88 | 88 | 14 | 16 | 31 | 15 |
| 80.150.169.41 - 0 | 88 | 88 | 31 | 39 | 259 | 259 |
| waw-sb4-i.WAW.PL.NET.DTAG.DE - 0 | 88 | 88 | 49 | 50 | 55 | 50 |
| 80.150.168.82 - 0 | 88 | 88 | 48 | 52 | 169 | 50 |
| ae9.cr0-waw3.ip4.gtt.net - 0 | 88 | 88 | 48 | 55 | 182 | 50 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| 91.216.250.229 - 0 | 88 | 88 | 86 | 111 | 139 | 114 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

[Bottiger]

How often does this happen? I cannot replicate the problem, traceroute with your same ISP.

traceroute to 91.216.250.224 (91.216.250.224) 64 hops max, 76 byte packets
1 10.11.1.1 (10.11.1.1) [AS???] 1.248 ms 0.459 ms 0.434 ms
2 172.27.99.1 (172.27.99.1) [AS???] 20.929 ms
*
*
3 172.24.112.1 (172.24.112.1) [AS???] 21.59 ms 21.425 ms 21.4 ms
4 htr11-gut23.ip.t-com.hr (195.29.225.205) [AS5391] 21.354 ms 21.788 ms 21.795 ms
5 hvz12-htr11.ip.t-com.hr (195.29.224.74) [AS5391] 26.855 ms 23.792 ms 24.52 ms
6 mvz-ts-10-hvz12.ip.t-com.hr (195.29.241.146) [AS5391] 23.29 ms 23.822 ms 23.362 ms
7 80.150.169.41 (80.150.169.41) [AS3320] 28.139 ms 28.171 ms 28.597 ms
8 waw-sb4-i.WAW.PL.NET.DTAG.DE (217.239.41.6) [AS3320] 55.728 ms 55.696 ms 55.458 ms
9 80.150.168.82 (80.150.168.82) [AS3320] 60.047 ms 54.945 ms 54.586 ms
10 ae9.cr0-waw3.ip4.gtt.net (213.200.114.190) [AS3257] 126.277 ms 54.565 ms 54.872 ms
11 * * *
12 * * *
13 * * *
14 91.216.250.224 (91.216.250.224) [AS208810] 56.626 ms 56.534 ms 56.889 ms

 

[Mister Jo.]

How often does this happen? I cannot replicate the problem, traceroute with your same ISP.

Happens pretty damn often, lasts a couple of days then just fixes itself. It's been happening for like 4, 5 days this time i believe and it just fixed itself last night not so long after i reported it. Usually once or twice a month it comes and goes, personally, i thought it was just pretty bad routing because i never have bad ping or bad connections.

Also, remember how i said it fixed itself, when the pings bad, both on tracert and on winMTR the only above 70 or 80 ping one is the direct server connection, i did a tracert again and the server is on 50 ping and works completely fine. Not sure if that means anything tho.
Tracing route to 91.216.250.224 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms speedport.ip [192.168.1.1]
2 * * * Request timed out.
3 10 ms 9 ms 8 ms 172.24.115.129
4 9 ms 9 ms 8 ms 195.29.240.137
5 13 ms 13 ms 16 ms hdr11-hst11.ip.t-com.hr [195.29.144.53]
6 14 ms 17 ms 14 ms hvz11-hdr11.ip.t-com.hr [195.29.144.38]
7 14 ms 14 ms 14 ms mvz-ts-10-hvz11.ip.t-com.hr [195.29.241.178]
8 28 ms 28 ms 28 ms 80.150.169.41
9 47 ms 47 ms 46 ms waw-sb4-i.WAW.PL.NET.DTAG.DE [217.239.41.6]
10 52 ms 48 ms 48 ms 80.150.168.82
11 69 ms 185 ms 48 ms ae9.cr0-waw3.ip4.gtt.net [213.200.114.190]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 50 ms 50 ms 50 ms 91.216.250.224

Edit: Forgot to mention that the Server Info in server search never shows the true ping, its always on my normal 40 to 50 ish range, but when i enter its 100 plus

 

[Bottiger]

If it only happens once or twice a month it is unfortunately not likely that our network providers will do anything. It is generally not possible to keep all connections to all isps perfectly clear at all times.

I have tested the connection again and there is no lag so it doesn't seem to be happening frequently unless it always happens right before I test it.

Your first traceroute shows the problem is that deutsche telekom, the network your isp uses to connect to GTT (our network provider) is congested at that time. Your 2nd traceroute doesn't show any issues.

It will be hard for us to convince your isp to do anything about this since we are not their customer, and on top of that, it is not happening all the time.

If you are getting 100 ping when you enter the server, you may have a configuration or firewall problem on your end.