Forum Discussion

MiniMized_HiRO's avatar
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 this server twice and had packet loss both times., while "buddy 2" had no issues.

Another time, I used my phones hotspot and didn't have packet loss on this server, while "buddy 1" was affected by it. So it is obviously caused by a network issue. However: pinging the server directly never gives any of us any lost packets. Traceroutes show that the internal routing at hetzner.com is always a bit different, but we can't find a common hop that seems to cause the issue.

Playing with these ISPs gave packet loss on the server:

  • Telekom Deutschland
  • Wingo (Fiber)

While playing the game with these ISPs didn't give packtet loss:

  • Kabel Deutschland
  • Swisscom (LTE)

This is the IP of the server in question: 148.251.75.175 (static.175.75.251.148.clients.your-server.de)

Here are some traceroutes of clients that either do, or do not experience packet loss when playing on this server.

Telekom Deutschland (is affected by packet loss)

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2     9 ms     8 ms    8 ms  p50928109.dip0.t-ipconnect.de [80.146.129.9]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    19 ms    18 ms    18 ms  ex9k2.dc11.fsn1.hetzner.com [213.239.229.10]
  8    19 ms    18 ms    17 ms  static.175.75.251.148.clients.your-server.de [148.251.75.175]

Wingo (is affected by packet loss)

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2    <1 ms    <1 ms    <1 ms  [redacted]
  3     4 ms     3 ms     5 ms  138.187.22.41
  4     2 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     2 ms     2 ms     2 ms  i79zhb-015-ae5.bb.ip-plus.net [193.5.122.0]
  7    30 ms     3 ms     2 ms  i79tix-025-ae11.bb.ip-plus.net [138.187.130.38]
  8     7 ms     7 ms     *     100ge0-36.core2.zrh3.he.net [184.104.193.133]
  9     6 ms     7 ms     7 ms  100ge8-1.core1.zrh2.he.net [72.52.92.129]
 10     *        *     2950 ms  100ge0-66.core3.fra1.he.net [184.105.65.30]
 11     *       10 ms    10 ms  decix2-gw.hetzner.com [80.81.193.164]
 12    25 ms    12 ms    12 ms  core24.fsn1.hetzner.com [213.239.203.150]
 13    12 ms    12 ms    13 ms  ex9k2.dc11.fsn1.hetzner.com [213.239.229.14]
 14    12 ms    12 ms    12 ms  static.175.75.251.148.clients.your-server.de [148.251.75.175]

Kabel Deutschland (is not affected by packet loss)

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2    13 ms     9 ms    10 ms  ip4d1665fe.dynamic.kabel-deutschland.de [77.22.101.254]
  3    10 ms    10 ms     9 ms  83-169-175-206-isp.superkabel.de [83.169.175.206]
  4    11 ms    13 ms    13 ms  ip5886c222.static.kabel-deutschland.de [88.134.194.34]
  5    12 ms    12 ms     9 ms  145.254.3.136
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    16 ms    20 ms    16 ms  static.213-133-113-9.clients.your-server.de [213.133.113.9]
  9     *       23 ms    21 ms  core24.fsn1.hetzner.com [213.239.229.78]
 10    22 ms    22 ms    21 ms  ex9k2.dc11.fsn1.hetzner.com [213.239.229.14]
 11    21 ms    19 ms    31 ms  static.175.75.251.148.clients.your-server.de [148.251.75.175]

Swisscom (LTE) (is not affected by packet loss)

  1     2 ms     1 ms     1 ms  [redacted]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    27 ms    46 ms    30 ms  i69lss-015-ae2.bb.ip-plus.net [193.134.95.230]
  9    34 ms    26 ms    27 ms  i68gem-015-ae1.bb.ip-plus.net [138.187.130.162]
 10    91 ms     *       37 ms  e0-33.core2.gva1.he.net [184.104.203.61]
 11     *       49 ms    38 ms  port-channel6.core2.zrh3.he.net [184.104.203.57]
 12    27 ms    42 ms    77 ms  100ge8-1.core1.zrh2.he.net [72.52.92.129]
 13     *        *     2722 ms  100ge0-66.core3.fra1.he.net [184.105.65.30]
 14     *       30 ms    74 ms  decix2-gw.hetzner.com [80.81.193.164]
 15     *        *        *     Request timed out.
 16    43 ms    42 ms    44 ms  ex9k2.dc11.fsn1.hetzner.com [213.239.229.10]
 17    39 ms    44 ms    39 ms  static.175.75.251.148.clients.your-server.de [148.251.75.175]

Please remember, pinging 148.251.75.175 never gives any of us any packet loss (even when pinging 10x a second). So while the problem definitely is affected by which network the client is coming from (see "buddy 2" not experiencing packet loss in the same game), the packet loss cannot be reproduced by spamming the IP with icmp ping packets. Any ISP that looks at this will firmly put any blame on whoever is hosting 148.251.75.175.

Desired outcome of this post: EA contacts your-server.de about the server with 148.251.75.175 on Monday, 3 January 2022 (CET) 21:00 to determine the cause of this issue.

I'll be happy to answer any questions that help with troubleshooting this further.

2 Replies

  • 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's avatar
    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.