Hello !
Depuis 2 semaines environ j'ai des problèmes fréquents de connexion aux serveurs de Zwift, une plate-forme d'entraînement cycliste multiplayer en ligne.
Zwift est hosté chez AWS, en particulier dans la région us-west-2 (Portland, Oregon) et comme je suis client FTTH Free, le transit passe par Cogent (voir traceroute ci-dessous, apparemment les serveurs AWS ne répondent pas au ping).
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| FREEBOX-SERVER - 0 | 10 | 10 | 0 | 0 | 4 | 0 |
| 194.149.169.89 - 0 | 10 | 10 | 8 | 8 | 9 | 8 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| be2102.ccr41.par01.atlas.cogentco.com - 0 | 10 | 10 | 8 | 8 | 9 | 9 |
| be2315.ccr31.bio02.atlas.cogentco.com - 0 | 10 | 10 | 21 | 21 | 21 | 21 |
| be2331.ccr41.dca01.atlas.cogentco.com - 0 | 10 | 10 | 88 | 88 | 89 | 88 |
| be2112.ccr41.atl01.atlas.cogentco.com - 0 | 10 | 10 | 99 | 114 | 140 | 99 |
| be2687.ccr41.iah01.atlas.cogentco.com - 0 | 10 | 10 | 112 | 112 | 113 | 113 |
| be2927.ccr21.elp01.atlas.cogentco.com - 0 | 10 | 10 | 128 | 129 | 130 | 129 |
| be2930.ccr32.phx01.atlas.cogentco.com - 0 | 10 | 10 | 137 | 137 | 137 | 137 |
| be2932.ccr42.lax01.atlas.cogentco.com - 0 | 10 | 10 | 148 | 148 | 149 | 149 |
| be3360.ccr41.lax04.atlas.cogentco.com - 0 | 10 | 10 | 148 | 148 | 149 | 149 |
| 38.142.35.250 - 0 | 10 | 10 | 148 | 149 | 151 | 148 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| 54.239.44.22 - 0 | 10 | 10 | 168 | 169 | 171 | 169 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Si je ping le serveur d'authentification (secure.zwift.com) sur le port TCP:443, j'obtiens une perte de paquets de l'ordre de 15 à 20%, ce qui est énorme, et impacte sérieusement l'application : difficulté au login, disparitions/réapparitions fréquentes de vélos à l'écran, etc.
tcping.exe -n 1000 -d -i 1 -w 1 -4 --tee secure.zwift.com.log secure.zwift.com 443
date: 2020:12:07 11:27:35
tcping.exe v0.39: http://www.elifulkerson.com/projects/tcping.php
Ping statistics for 35.165.148.208:443
1000 probes sent.
817 successful, 183 failed. (18.30%% fail)
Approximate trip times in milli-seconds (successful connections only):
Minimum = 166.546ms, Maximum = 212.348ms, Average = 168.342ms
Est-ce que par hasard d'autres personnes auraient remarqué des problèmes similaires sur Zwift ou d'autres applis temp réel hébergées sur AWS?
Transit IP