Lost connection to game server

Technical Support
1

I’ve already opened a ticket #19288 but I think I found the issue using PathPing + TraceRoute.
Looks like [137.221.77.67] is not responding, it is not an ISP issue!

Tracing route to 185.60.114.159 over a maximum of 30 hops

0 gilad-pc [192.168.1.100]
1 192.168.1.1
2 10.97.97.1
3 * 100.127.255.65
4 109.226.0.170
5 -te0-7-0-35.203.agr21.fra06.atlas.cogentco.com [149.14.69.121]
6 -be2844.rcr22.fra06.atlas.cogentco.com [130.117.0.29]
7 -gi0-0-1-5.nr11.b015760-1.fra06.atlas.cogentco.com [149.11.20.61]
8 137.221.80.35
9 -et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
10 -be1-pe01-eqpa4.as57976.net [137.221.77.67]
11 185.60.114.159

Computing statistics for 275 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 gilad-pc [192.168.1.100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 10.97.97.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% 100.127.255.65
0/ 100 = 0% |
4 8ms 1/ 100 = 1% 1/ 100 = 1% 109.226.0.170
0/ 100 = 0% |
5 63ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0–35.203.agr21.fra06.atlas.cogentco.com [149.14.69.121]
0/ 100 = 0% |
6 63ms 0/ 100 = 0% 0/ 100 = 0% - -be2844.rcr22.fra06.atlas.cogentco.com [130.117.0.29]
0/ 100 = 0% |
7 67ms 0/ 100 = 0% 0/ 100 = 0% -gi0-0-1-5.nr11.b015760-1.fra06.atlas.cogentco.com [149.11.20.61]
0/ 100 = 0% |
8 70ms 0/ 100 = 0% 0/ 100 = 0% 137.221.80.35
0/ 100 = 0% |
9 74ms 0/ 100 = 0% 0/ 100 = 0% -et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
0/ 100 = 0% |
10 — 100/ 100 =100% 100/ 100 =100% -be1-pe01-eqpa4.as57976.net [137.221.77.67]
0/ 100 = 0% |
11 72ms 0/ 100 = 0% 0/ 100 = 0% 185.60.114.159

Trace complete.

TraceRT:

Tracing route to 185.60.114.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 10.97.97.1
3 * * * Request timed out.
4 8 ms 8 ms 8 ms 109.226.0.170
5 63 ms 62 ms 66 ms -te0-7-0-35.203.agr21.fra06.atlas.cogentco.com [149.14.69.121]
6 63 ms 64 ms 63 ms -be2844.rcr22.fra06.atlas.cogentco.com [130.117.0.29]
7 63 ms 73 ms 63 ms -gi0-0-1-5.nr11.b015760-1.fra06.atlas.cogentco.com [149.11.20.61]
8 73 ms 73 ms 72 ms 137.221.80.35
9 72 ms 72 ms 72 ms -et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
10 73 ms 72 ms 72 ms -be1-pe01-eqpa4.as57976.net [137.221.77.67]
11 73 ms 72 ms 72 ms 185.60.114.159

Trace complete.

2

Maybe it has to do something with DDos attacks that are in progress, look it up on the net.

3

I’m still waiting for an answer for tech support!!

4

Hello Krasilies :slight_smile:

The data you see in the pathping regarding the IP 137.221.77.67 does not indicate an issue, it simply means that the node has some form of flood protection that blocks certain kind of tests.

The same protection does not apply to the trace route though, and you can see there that the node offers healthy results :slight_smile:

Should you continue to experience disconnections, would you be so kind as to post the results of a WinMTR test?

That should give us a bit more data to work with to see what may be causing the problem you described ^^