Latency/Packet Loss Issues [Chaos Datacenter]

[Kuroka]

Hello Everyone,

You are welcome, We will continue to provide information/updates as we receive them. Thank you for your understanding.

Thank you for the information^^

[Ariellendera]

Thank you for the information^^

You are welcome!

[Agidelle]

Started lag after the patch. Getting disconnects from the server and lags.

Sorry for my bad English.
Time: 18:00 GMT

Tracing route to 195.82.50.48 over a maximum of 30 hops

2 * * * Request timed out.
3 9 ms * 5 ms 238.232.vsd-net.ru [77.247.232.238]
4 7 ms 9 ms 8 ms 238.232.vsd-net.ru [77.247.232.238]
5 10 ms 24 ms 25 ms 193.232.vsd-net.ru [77.247.232.193]
6 12 ms * 11 ms 87.229.218.53
7 30 ms 31 ms 28 ms mx01.Stockholm.gldn.net [79.104.225.6]
8 32 ms 30 ms 28 ms 212.73.250.45
9 60 ms 60 ms 60 ms ae-2-3207.edge5.Frankfurt1.Level3.net [4.69.163.
22]
10 69 ms 56 ms 65 ms 212.162.4.98
11 57 ms 57 ms 63 ms 195.82.60.29
12 56 ms 66 ms 56 ms 195.82.61.14
13 58 ms 56 ms 56 ms 195.82.50.234
14 56 ms 56 ms 57 ms 195.82.50.48

Trace complete.

Thank you in advance.

[KarstenS]

Did something got changed?

For me this week was currently without noticeable Lags. But I feel a high overall latency.

Provider: Deutsche Telekom
Connection is DSL/LTE Bonding Hybrid (66MBit/s down, 12MBit/s up)

My physical distance to the data center is very low.



Ping and tracert (DSL Only, LTE Disabled, direct connection without bonding tunnel) confirms observation.

Ping wird ausgeführt für 192.82.50.52 mit 32 Bytes Daten:
Antwort von 192.82.50.52: Bytes=32 Zeit=126ms TTL=57
Antwort von 192.82.50.52: Bytes=32 Zeit=126ms TTL=57
Antwort von 192.82.50.52: Bytes=32 Zeit=126ms TTL=57
Antwort von 192.82.50.52: Bytes=32 Zeit=126ms TTL=57

Ping-Statistik für 192.82.50.52:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 126ms, Maximum = 126ms, Mittelwert = 126ms

Routenverfolgung zu 192.82.50.52 über maximal 30 Hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.188.1]
2 1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
3 20 ms 18 ms 20 ms 62.155.246.40
4 21 ms 23 ms 21 ms 217.239.45.42
5 * * * Zeitüberschreitung der Anforderung.
6 * * * Zeitüberschreitung der Anforderung.
7 41 ms 42 ms 41 ms 62.67.34.66
8 71 ms 67 ms 69 ms anc-cr03-ae2.149.ff.stream-internet.net [212.188.1.205]
9 67 ms 68 ms 68 ms leo-cr02-be6.80.kiev.stream-internet.net [212.188.55.170]
10 68 ms 68 ms 68 ms pbd-cr01-be1.80.kiev.stream-internet.net [212.188.55.165]
11 61 ms 62 ms 63 ms 212.188.41.154
12 67 ms 67 ms 68 ms atm-ic-326261-war-b1.c.telia.net [80.239.167.45]
13 68 ms 68 ms 68 ms 185.200.121.6
14 126 ms 126 ms 126 ms 192.82.50.52

Back in good old days after the launch of the Frankfurt data center I had pings of around 7ms to Odin and now its close to 130ms.

[Ariellendera]

Did something got changed?

For me this week was currently without noticeable Lags. But I feel a high overall latency.

Provider: Deutsche Telekom
Connection is DSL/LTE Bonding Hybrid (66MBit/s down, 12MBit/s up)

My physical distance to the data center is very low.



Ping and tracert (DSL Only, LTE Disabled, direct connection without bonding tunnel) confirms observation.





Back in good old days after the launch of the Frankfurt data center I had pings of around 7ms to Odin and now its close to 130ms.

Thank you for your input on this thread. I cannot confirm if anything has changed. I will be passing this information along.

[KarstenS]

Thank you for your input on this thread. I cannot confirm if anything has changed. I will be passing this information along.

I did a little mistake in numbers. Used a 192.x.x.x instead of 195.x.x.x.

Please forget the ping and tracert of my last post and use these instead (3:30am CET):

TraceRT

Routenverfolgung zu 195.82.50.52 über maximal 30 Hops

  1     3 ms    <1 ms    <1 ms  fritz.box [192.168.188.1]
  2     1 ms     1 ms    <1 ms  speedport.ip [192.168.2.1]
  3    19 ms    19 ms    19 ms  62.155.246.40
  4    21 ms    21 ms    21 ms  217.239.45.190
  5    21 ms    21 ms    21 ms  ffm-b4-link.telia.net [213.248.93.186]
  6    22 ms    22 ms    22 ms  ffm-bb3-link.telia.net [62.115.125.224]
  7    21 ms    30 ms    22 ms  ffm-b1-link.telia.net [62.115.141.241]
  8    20 ms    20 ms    20 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
  9    21 ms    20 ms    21 ms  195.82.61.14
 10    21 ms    22 ms    21 ms  195.82.50.234
 11    21 ms    20 ms    20 ms  195.82.50.52

Ping

Ping wird ausgeführt für 195.82.50.52 mit 32 Bytes Daten:
Antwort von 195.82.50.52: Bytes=32 Zeit=21ms TTL=56
Antwort von 195.82.50.52: Bytes=32 Zeit=20ms TTL=56
Antwort von 195.82.50.52: Bytes=32 Zeit=20ms TTL=56
Antwort von 195.82.50.52: Bytes=32 Zeit=20ms TTL=56

Ping-Statistik für 195.82.50.52:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 20ms, Maximum = 21ms, Mittelwert = 20ms

[Kusanagi7]

19/3/18 12:16pm

traceroute to 192.82.50.9 (192.82.50.9), 30 hops max, 64 byte packets
1 * * *
2 82.13.126.17 20.000 ms 10.000 ms 100.000 ms
3 * * *
4 62.254.42.242 20.000 ms 30.000 ms 20.000 ms
5 62.254.85.86 30.000 ms 30.000 ms 30.000 ms
6 * * *
7 84.116.136.98 20.000 ms 20.000 ms 30.000 ms
8 213.46.174.170 20.000 ms 20.000 ms 30.000 ms
9 * * *
10 62.67.34.66 50.000 ms 30.000 ms 40.000 ms
11 212.188.1.205 70.000 ms 80.000 ms 60.000 ms
12 212.188.55.170 70.000 ms 60.000 ms 60.000 ms
13 212.188.55.165 60.000 ms 60.000 ms 70.000 ms
14 212.188.41.154 70.000 ms 60.000 ms 60.000 ms
15 212.40.44.70 90.000 ms 90.000 ms 90.000 ms
16 185.200.121.6 100.000 ms 90.000 ms 80.000 ms
17 192.82.50.9 130.000 ms 130.000 ms 130.000 ms
Traceroute complete.

ISP: Virgin Media

Platform: Playstation 4

still getting lag and either error 90002 or 90001

[Agidelle]

Hi! After my last post and transfer the data to the department, the lags almost disappeared for 2 days. But since yesterday the lag and the disconnects resumed in the same form, lags of 30-100+ seconds. Make a new trace. Thank you in advance.

Time 20:00 GMT

Tracing route to 195.82.50.48 over a maximum of 30 hops

  2 * * * Request timed out.
  3     5 ms     5 ms     4 ms  238.232.vsd-net.ru [77.247.232.238]
  4     5 ms     5 ms     4 ms  238.232.vsd-net.ru [77.247.232.238]
  5    10 ms    10 ms    10 ms  193.232.vsd-net.ru [77.247.232.193]
  6    11 ms    11 ms    10 ms  87.229.218.53
  7    31 ms    33 ms    32 ms  mx01.Stockholm.gldn.net [79.104.225.6]
  8     *        *       31 ms  212.73.250.45
  9    58 ms    58 ms    58 ms  ae-2-3207.edge5.Frankfurt1.Level3.net [4.69.163.
22]
 10    60 ms    56 ms    60 ms  212.162.4.98
 11    71 ms    65 ms    59 ms  195.82.60.29
 12    56 ms    57 ms    56 ms  195.82.61.14
 13    62 ms    60 ms    59 ms  195.82.50.234
 14    56 ms    56 ms    56 ms  195.82.50.48

Trace complete.

[Karan_Vess]

Just coming by to drop another trace. This is from o7s, where I get the worst lags and that very frequently.

Tracing route to 195.82.50.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 6 ms 5 ms 5 ms dus1901aihr001.versatel.de [62.214.63.82]
3 * 11 ms 13 ms 62.214.36.97
4 20 ms 20 ms 19 ms 62.214.37.158
5 23 ms 23 ms 23 ms 213.242.108.153
6 37 ms 37 ms 36 ms ae-2-3207.edge5.Frankfurt1.Level3.net [4.69.163.22]
7 26 ms 26 ms 26 ms 212.162.4.98
8 30 ms 29 ms 38 ms 195.82.60.29
9 36 ms 26 ms * 195.82.61.14
10 30 ms 30 ms * 195.82.50.234
11 26 ms 25 ms 25 ms 195.82.50.9

Trace complete.