Forum Discussion

4 years ago

Packet loss on server hosted by your-server.de

For a while now, me and one of my buddies (lets say "buddy 1") have had packet loss when connecting to a specific server, while "buddy 2" never has packet loss in the same game. Today we connected to...

MiniMized_HiRO

4 years ago

If you want to help troubleshoot this issue, please add your own traceroutes to servers where you experience packet loss. Please make sure however, the packet loss isn't caused by another issue on your end.

To find a servers IP, check the windows resource monitor > network activity for r5apex.exe or capture network traffic with wireshark and look for traffic on UDP port range 37005-38551. This needs to be done while you're still connected to that particular server.

Once you have the server IP, use cmd.exe to run a "tracert" to the servers IP address and post it here. Adding your ISP can be useful (if it isn't obvious from the traceroute hops).

MiniMized_HiRO

4 years ago

Different day, different server, same story (me and buddy 1 with packet loss, buddy 2 no packet loss).

Telekom Deutschland (is affected by packet loss)

  1     1 ms     1 ms    <1 ms  [redacted]
  2     9 ms     7 ms     7 ms  p50928109.dip0.t-ipconnect.de [80.146.129.9]
  3    15 ms    14 ms    19 ms  pd900c022.dip0.t-ipconnect.de [217.0.192.34]
  4    16 ms    14 ms    14 ms  80.157.201.198
  5    15 ms    15 ms    14 ms  be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118]
  6    18 ms    17 ms    17 ms  be2846.rcr22.fra06.atlas.cogentco.com [154.54.37.30]
  7    18 ms    16 ms    17 ms  be2851.nr21.b015759-0.fra06.atlas.cogentco.com [154.25.7.2]
  8    18 ms    15 ms    15 ms  185.225.211.255
  9    18 ms    17 ms    18 ms  185.225.211.253
 10    17 ms    15 ms    15 ms  185.225.209.170

Wingo (is affected by packet loss)

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2    <1 ms     1 ms    <1 ms  [redacted]
  3     3 ms     2 ms     3 ms  138.187.22.41
  4     3 ms     2 ms     2 ms  172.25.17.84
  5     2 ms     2 ms     2 ms  178.238.168.45.ipv4.net.wingo.ch [178.238.168.45]
  6     3 ms     3 ms     3 ms  i79zhb-015-ae5.bb.ip-plus.net [193.5.122.0]
  7    11 ms    11 ms    11 ms  hu0-1-0-4.ccr52.zrh02.atlas.cogentco.com [149.6.176.225]
  8    12 ms    11 ms    12 ms  be3073.ccr22.muc03.atlas.cogentco.com [130.117.0.62]
  9    11 ms    11 ms    11 ms  be2960.ccr42.fra03.atlas.cogentco.com [154.54.36.253]
 10    12 ms    12 ms    12 ms  be2846.rcr22.fra06.atlas.cogentco.com [154.54.37.30]
 11    12 ms    12 ms    12 ms  be2851.nr21.b015759-0.fra06.atlas.cogentco.com [154.25.7.2]
 12    14 ms    13 ms    15 ms  185.225.211.255
 13    13 ms    12 ms    13 ms  185.225.211.252
 14    13 ms    12 ms    13 ms  185.225.209.170

Kabel Deutschland (is not affected by packet loss)

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2    11 ms    12 ms     9 ms  ip4d1665fe.dynamic.kabel-deutschland.de [77.22.101.254]
  3    12 ms    11 ms    13 ms  83-169-175-206-isp.superkabel.de [83.169.175.206]
  4    14 ms    11 ms    13 ms  ip5886c222.static.kabel-deutschland.de [88.134.194.34]
  5    13 ms    11 ms     9 ms  145.254.3.136
  6    15 ms    14 ms    17 ms  145.254.2.215
  7    50 ms    17 ms     *     145.254.2.215
  8    12 ms    14 ms    14 ms  ae9-100-xcr1.hac.cw.net [195.89.99.1]
  9    20 ms    23 ms    20 ms  ae40-pcr1.fis.cw.net [195.2.2.138]
 10     *        *        *     Request timed out.
 11    21 ms    21 ms    21 ms  be2845.rcr22.fra06.atlas.cogentco.com [154.54.56.190]
 12    23 ms    28 ms    20 ms  be2851.nr21.b015759-0.fra06.atlas.cogentco.com [154.25.7.2]
 13    25 ms    24 ms    22 ms  185.225.211.254
 14    22 ms    19 ms    20 ms  185.225.211.252
 15    20 ms    18 ms    17 ms  185.225.209.170

This time there problematic node can be identified. The hop 154.54.37.30 is part of both routes affected by packet loss. Also, if you spam 154.54.37.30 with pings, about 15% of packets are lost. So with this one, the host of 185.225.209.170 should inform cogent of the unhealthy node.