Ping lag FIX IDEAS PLEASE?

[𝕬𝖗𝖙𝖍𝖚𝖗]

I have played brawlhalla on my old pc a lot and had good ping,all was fine.I bought my new pc,for a month it worked fine,but after that it started teleporting me and my opponent.I don't have ping problems in other games except for this one and sometimes in LoL.I want to know if there are some ways to fix it because it's really unplayable when your character is teleporting at different locations on the map,or when you pick a weapon first,but after a second you don't have it but your opponent does.If someone finds a solution that works i will be thankful :)

[୨ಠ ͜つಠ୧]

have you tried to check this thread https://steamcommunity.com/app/291550/discussions/0/617319460923516233/ ?

also if you post the results of your ping test here we can help (maybe)

[𝕬𝖗𝖙𝖍𝖚𝖗]

I checked it and the link for ping on servers is not working for some reason.Anything else?

[୨ಠ ͜つಠ୧]

x)

you don't have to click it
type "ping pingtest-ams.brawlhalla.com -n 100" without " in your command prompt (and replace "pingtest-ams.brawlhalla.com" with the link of your region of course)

[KsYrilL]

Originally posted by ʢꔸᨓꔸʡ:

x)

you don't have to click it
type "ping pingtest-ams.brawlhalla.com -n 100" without " in your command prompt (and replace "pingtest-ams.brawlhalla.com" with the link of your region of course)

What does this result mean?
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 461ms, Average = 126ms

[𝕬𝖗𝖙𝖍𝖚𝖗]

and how do i do that if my region is europe?

[Lychee]

Originally posted by Colea03:

and how do i do that if my region is europe?

By using the pingtest link dedicated for the European server, which is pingtest-ams.brawlhalla.com. Doing both a pingtest and tracert with it is preferrable.

Do not try to open the link. In a command prompt (cmd for short), use these two commands:
ping -n 100 pingtest-ams.brawlhalla.com
tracert pingtest-ams.brawlhalla.com

After that, paste only the results back here, then we might be able to help.

[୨ಠ ͜つಠ୧]

Originally posted by Colea03:

and how do i do that if my region is europe?

Originally posted by sKyrill:

What does this result mean?
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 461ms, Average = 126ms

you didn't lose any packet and that's good (in brawlhalla if you lose packets you lose synchronization with the server much more than in other games ,but you didn't lost any of them so it's fine)
but eehhh your ping is horrible ,the time that passes between when you say something to the server and when you get a response is 126 milliseconds usually (which is already pretty bad for online gaming) and in those few moments in which your ping was 461 milliseconds you may have seen some teleports (if you were playing)

did you use the link of your region ?
those are the links for every region
1) US: pingtest-atl.brawlhalla.com
2) Europe: pingtest-ams.brawlhalla.com
3) SE Asia: pingtest-sgp.brawlhalla.com
4) US-West: pingtest-cal.brawlhalla.com
5) Australia: pingtest-aus.brawlhalla.com
6) Brazil: pingtest-brs.brawlhalla.com

oh and do a ping test with "google.com" too so we can see if there is a problem with your connection to brawlhalla servers or your connection with everything

[KsYrilL]

Originally posted by ʢꔸᨓꔸʡ:

you didn't lose any packet and that's good (in brawlhalla if you lose packets you lose synchronization with the server much more than in other games ,but you didn't lost any of them so it's fine)
but eehhh your ping is horrible ,the time that passes between when you say something to the server and when you get a response is 126 milliseconds usually (which is already pretty bad for online gaming) and in those few moments in which your ping was 461 milliseconds you may have seen some teleports (if you were playing)

did you use the link of your region ?
those are the links for every region
1) US: pingtest-atl.brawlhalla.com
2) Europe: pingtest-ams.brawlhalla.com
3) SE Asia: pingtest-sgp.brawlhalla.com
4) US-West: pingtest-cal.brawlhalla.com
5) Australia: pingtest-aus.brawlhalla.com
6) Brazil: pingtest-brs.brawlhalla.com

oh and do a ping test with "google.com" too so we can see if there is a problem with your connection to brawlhalla servers or your connection with everything

I tried it all over again. The 1st result I posted was from the sea link since this is my region. Tried all other servers and have an avg of 300+.

Google.com
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 241ms, Average = 52ms

sgp.brawlhalla.com
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 176ms, Average = 117ms

Also what should the avg be for a game like brawlhalla?

[୨ಠ ͜つಠ୧]

Originally posted by sKyrill:

I tried it all over again. The 1st result I posted was from the sea link since this is my region. Tried all other servers and have an avg of 300+.

Google.com
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 241ms, Average = 52ms

sgp.brawlhalla.com
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 176ms, Average = 117ms

:/ your connection with google is good (except that spike at 241 ms and maybe a few other more spikes) so i guess that the problem is your brawlhalla server (also cause a lot fo people complain about that server on the forums) and there is no way to fix that ,sorry :C

Also what should the avg be for a game like brawlhalla?

it depends from your skill level ,consider that there is a delay of 117 milliseconds between you and the server so you may have some input delays (you should not have teleports when you don't have a huge ping spikes though)
better connections are always good obviously but i can't say if your connection is good enough for you ,117 ms is probably good enough to play casually also low rank players won't even notice it but at high ranks it is a bad problem

[KsYrilL]

Originally posted by ୨ಠ ͜つಠ୧:

it depends from your skill level ,consider that there is a delay of 117 milliseconds between you and the server so you may have some input delays (you should not have teleports when you don't have a huge ping spikes though)
better connections are always good obviously but i can't say if your connection is good enough for you ,117 ms is probably good enough to play casually also low rank players won't even notice it but at high ranks it is a bad problem

Playing against scythe is a nightmare and when it starts lagging in ranked I get really tilted. Hope I can reach plat this season though. Thanks anyways.
And OP sry for hijacking your thread.

[𝕬𝖗𝖙𝖍𝖚𝖗]

so i tried that command thing in cmd and here are the results:
Pinging pingtest-ams.brawlhalla.com [172.98.83.57] with 32 bytes of data:
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=56ms TTL=112
Reply from 172.98.83.57: bytes=32 time=61ms TTL=112
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=58ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=58ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=58ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=59ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=50ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=57ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=55ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=78ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=52ms TTL=112
Reply from 172.98.83.57: bytes=32 time=51ms TTL=112
Reply from 172.98.83.57: bytes=32 time=57ms TTL=112
Reply from 172.98.83.57: bytes=32 time=54ms TTL=112
Reply from 172.98.83.57: bytes=32 time=53ms TTL=112

Ping statistics for 172.98.83.57:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 78ms, Average = 53ms

and for the second command:

Tracing route to pingtest-ams.brawlhalla.com [172.98.83.57]
over a maximum of 30 hops:

1 1 ms 7 ms 3 ms 192.168.0.1
2 40 ms 19 ms 32 ms 1-118-149-89.orange.md [89.149.118.1]
3 11 ms 12 ms 11 ms static.217.12.120.241.tmg.md [217.12.120.241]
4 14 ms 13 ms 10 ms static.77.89.192.34.tmg.md [77.89.192.34]
5 13 ms 11 ms 12 ms edge-mm-mm-d.orange.md [77.89.192.9]
6 16 ms 19 ms 18 ms adsl86-34-131-1.romtelecom.net [86.34.131.1]
7 21 ms 17 ms 17 ms 10.0.252.149
8 * * * Request timed out.
9 49 ms 47 ms 46 ms 10.0.200.166
10 47 ms 47 ms 46 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
11 * * * Request timed out.
12 58 ms 57 ms 57 ms UK2-LIMITED.ear3.Amsterdam1.Level3.net [213.19.197.70]
13 * * * Request timed out.
14 53 ms 53 ms 52 ms 172.98.83.57

Trace complete.


anything useful?

[𝕬𝖗𝖙𝖍𝖚𝖗]

Originally posted by sKyrill:

Originally posted by ୨ಠ ͜つಠ୧:

it depends from your skill level ,consider that there is a delay of 117 milliseconds between you and the server so you may have some input delays (you should not have teleports when you don't have a huge ping spikes though)
better connections are always good obviously but i can't say if your connection is good enough for you ,117 ms is probably good enough to play casually also low rank players won't even notice it but at high ranks it is a bad problem

Playing against scythe is a nightmare and when it starts lagging in ranked I get really tilted. Hope I can reach plat this season though. Thanks anyways.
And OP sry for hijacking your thread.

it's ok but don't do that anymore

[Lychee]

Originally posted by Son Gokū:

so i tried that command thing in cmd and here are the results:
Pinging pingtest-ams.brawlhalla.com [172.98.83.57] with 32 bytes of data:

Ping statistics for 172.98.83.57:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 78ms, Average = 53ms

and for the second command:

Tracing route to pingtest-ams.brawlhalla.com [172.98.83.57]
over a maximum of 30 hops:

1 1 ms 7 ms 3 ms 192.168.0.1
2 40 ms 19 ms 32 ms 1-118-149-89.orange.md [89.149.118.1]
3 11 ms 12 ms 11 ms static.217.12.120.241.tmg.md [217.12.120.241]
4 14 ms 13 ms 10 ms static.77.89.192.34.tmg.md [77.89.192.34]
5 13 ms 11 ms 12 ms edge-mm-mm-d.orange.md [77.89.192.9]
6 16 ms 19 ms 18 ms adsl86-34-131-1.romtelecom.net [86.34.131.1]
7 21 ms 17 ms 17 ms 10.0.252.149
8 * * * Request timed out.
9 49 ms 47 ms 46 ms 10.0.200.166
10 47 ms 47 ms 46 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
11 * * * Request timed out.
12 58 ms 57 ms 57 ms UK2-LIMITED.ear3.Amsterdam1.Level3.net [213.19.197.70]
13 * * * Request timed out.
14 53 ms 53 ms 52 ms 172.98.83.57

Trace complete.


anything useful?

Pingtest looks good. No packets have dropped.

I couldn't quite read the trace first, but it looks like those data packets are having trouble reaching the server. Tracert basically "traces" your packets to see where they're going, but it's timing out in some places.

You don't want your connection doing that to you. Maybe call your ISP about it.