I’ll try running them exactly when i get DCed, but it will be hard to do. Some days I get them in the morning, some days at night, sometimes once per match, other times 3 times in a row in the same match.
For the moment I will send my normals pings.
WinMTR statistics
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 40 |
| 185.60.112.157 - 0 | 122 | 122 | 40 | 52 | 55 | 52 |
|________________________________________________|
Both IPs show 100% packetloss
Tracert on both IPs is the same
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.100.1
2 * * * Request timed out.
3 4 ms 4 ms 5 ms 10.0.242.138
4 36 ms 36 ms 36 ms 86.104.125.89
5 41 ms 41 ms 41 ms ae1-br01-eqfr5.as57976 [137.221.80.33]
6 42 ms 42 ms 48 ms et-0-0-2-br01-eqam1.as57976 [137.221.65.29]
7 90 ms 41 ms 41 ms et-0-0-31-pe01-eqam1.as57976 [137.221.78.67]
8 42 ms 41 ms 42 ms 185.60.112.158
Regular ping
Ping statistics for 185.60.112.158:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 42ms, Average = 41ms