Scoreboard |
ITB
02:00
DASH
0
ITB
00:02
TSM
0
MOUZ NXT
02:01
TSM
0
ITB
02:00
ALTERNATE
0
Falcons
02:00
Virtus.pro
1
FaZe
02:00
OG
0
Verdant
00:02
Anonymo
0
BIG
01:02
Virtus.pro
0
Falcons
02:01
Complexity
0
Revenant
00:02
ECSTATIC
0
OG
02:01
AMKAL
0
BIG
02:01
GamerLegion
0
Cloud9
00:02
paiN
1
Verdant
01:02
Revenant
0
Verdant
01:02
Sampi
0
Falcons
02:00
M80
0
Complexity
02:00
Metizport
0
Revenant
01:02
Alliance
0
Forum |
Forum |
Aide VPN / Faceit - 23 messages, 5245 vues
1er message |
|
|
Par Amad - 24/04/2020 17:10:23 - Modifié le 24/04/2020 18:13:56 |
Réponse #2 |
|
|
Par Hindrik - 24/04/2020 17:30:14 - Modifié le 24/04/2020 18:13:56 |
Réponse #3 |
|
|
Par Amad - 24/04/2020 17:38:30 - Modifié le 24/04/2020 18:13:56 |
https://support.faceit.com/hc/en-us/articles/208283275-CS-GO-Server-Lag-Issues- Hyperz et le fournisseurs des serveurs FaceIt. |
Réponse #4 |
|
|
Par Hindrik - 24/04/2020 17:40:08 - Modifié le 24/04/2020 18:13:56 |
Réponse #5 |
|
|
Par Amad - 24/04/2020 17:43:58 - Modifié le 24/04/2020 18:13:56 |
Sur la même plage horaire je n'ai aucun problème en matchmaking (50 de ping) ou de débit internet. Voila leurs message ou sa cloche : Hi, I'm experiencing bad network performance to/from this IP: PRIVER (and whole AS24940 and also other ASNs reached over LEVEL3) Apparently all my return traffic from that IP is experiencing congestions on PROXAD PNI with LEVEL3. I ask you to please investigate and restore a proper un-congested direct route to that destination network. You have been sent a peering request from AS24940 please follow up on that as an alternative in fixing the LEVEL3 congestion being experiencing by PROXAD. This is an example that shows the reverse routing issue I'm referring done from PRIVER : https://pastebin.com/raw/DHTh0Z5Y HOST: fr69.itcore Loss% Snt Last Avg Best Wrst StDev 1.|-- static.225.197.243.136.clients.your-server.de 0.0% 10 0.3 0.4 0.2 1.1 0.0 2.|-- core23.fsn1.hetzner.com 40.0% 10 12.0 16.4 6.2 29.4 10.2 3.|-- juniper5.nbg1.hetzner.com 0.0% 10 2.7 2.8 2.6 3.5 0.0 4.|-- ae5-710.nbg40.core-backbone.com 0.0% 10 2.7 2.8 2.7 2.9 0.0 5.|-- ae1-2003.fra20.core-backbone.com 0.0% 10 6.0 6.1 6.0 6.3 0.0 6.|-- 195.122.181.129 30.0% 10 6.3 6.3 6.3 6.5 0.0 7.|-- ae-2-3211.edge7.Paris1.Level3.net 0.0% 10 18.8 20.6 18.8 26.1 2.4 8.|-- free-pni-1.routers.proxad.net 0.0% 10 134.0 135.4 132.2 140.2 2.6 9.|-- deu95-1-v904.intf.nra.proxad.net 0.0% 10 137.5 135.7 130.3 144.7 3.9 10.|-- plb95-1-v910.intf.nra.proxad.net 20.0% 10 132.6 135.4 131.8 141.8 4.0 11.|-- 78.254.4.169 30.0% 10 135.8 133.7 130.1 139.5 3.4 12.|-- plb95-9-78-241-233-248.fbx.proxad.net 0.0% 10 157.5 155.7 150.5 164.8 4.0 as you can see their ping jumps to 137ms here: free-pni-1.routers.proxad.net |
Réponse #6 |
|
|
Par Amad - 24/04/2020 17:45:14 - Modifié le 24/04/2020 18:13:56 |
L'utilisation d'un VPN peut résoudre mon problème dans un message suivant. |
Réponse #7 |
|
|
Par AZIDOT - 24/04/2020 17:54:40 - Modifié le 24/04/2020 18:13:56 |
te connecter à un serveur étant hébergé à Paris me semble le mieux. |
Réponse #8 |
|
|
Par Amad - 24/04/2020 18:08:42 - Modifié le 24/04/2020 18:13:56 |
Merci Azidot, je teste ça ce soir ! |
Réponse #9 |
|
|
Par Morelax - 24/04/2020 18:28:11 |
Salut, je m'incruste ici aussi. Même problème que toi. J'ai des fois un ping de 130 sur certains serveurs, mais sans récurrence. En MM, RAS. Ça n'est que sur Faceit. Je vais aussi tester le VPN. |
Réponse #10 |
|
|
Par Hindrik - 24/04/2020 18:48:07 |
Sur la même plage horaire je n'ai aucun problème en matchmaking (50 de ping) ou de débit internet. Voila leurs message ou sa cloche : Hi, I'm experiencing bad network performance to/from this IP: PRIVER (and whole AS24940 and also other ASNs reached over LEVEL3) Apparently all my return traffic from that IP is experiencing congestions on PROXAD PNI with LEVEL3. I ask you to please investigate and restore a proper un-congested direct route to that destination network. You have been sent a peering request from AS24940 please follow up on that as an alternative in fixing the LEVEL3 congestion being experiencing by PROXAD. This is an example that shows the reverse routing issue I'm referring done from PRIVER : https://pastebin.com/raw/DHTh0Z5Y HOST: fr69.itcore Loss% Snt Last Avg Best Wrst StDev 1.|-- static.225.197.243.136.clients.your-server.de 0.0% 10 0.3 0.4 0.2 1.1 0.0 2.|-- core23.fsn1.hetzner.com 40.0% 10 12.0 16.4 6.2 29.4 10.2 3.|-- juniper5.nbg1.hetzner.com 0.0% 10 2.7 2.8 2.6 3.5 0.0 4.|-- ae5-710.nbg40.core-backbone.com 0.0% 10 2.7 2.8 2.7 2.9 0.0 5.|-- ae1-2003.fra20.core-backbone.com 0.0% 10 6.0 6.1 6.0 6.3 0.0 6.|-- 195.122.181.129 30.0% 10 6.3 6.3 6.3 6.5 0.0 7.|-- ae-2-3211.edge7.Paris1.Level3.net 0.0% 10 18.8 20.6 18.8 26.1 2.4 8.|-- free-pni-1.routers.proxad.net 0.0% 10 134.0 135.4 132.2 140.2 2.6 9.|-- deu95-1-v904.intf.nra.proxad.net 0.0% 10 137.5 135.7 130.3 144.7 3.9 10.|-- plb95-1-v910.intf.nra.proxad.net 20.0% 10 132.6 135.4 131.8 141.8 4.0 11.|-- 78.254.4.169 30.0% 10 135.8 133.7 130.1 139.5 3.4 12.|-- plb95-9-78-241-233-248.fbx.proxad.net 0.0% 10 157.5 155.7 150.5 164.8 4.0 as you can see their ping jumps to 137ms here: free-pni-1.routers.proxad.net Ahhhhhhhh, beh oui alors, ça se précise. |