ID:2932975
 
(See the best response by Lummox JR.)
Operating System: Windows 10

Attempted method:
- Clear cache
- Switched to wired connection
- delete user directory
- Reinstalling byond
- Reboot router

Summary:
At first started as unusually high ping spike (From usually ~270 ms to ~400 ms)
Then connection failed handshake

This started around May 25 last month, before that there is never ping spike this high before and now the dreamseeker don't even start up.

This could be problem on my end but after using wireshark dreamseeker seem to be freeze and not taking any connection at all (Dreamseeker.exe even show 0mbps on task manager)

If you need more infromation please let me know

Edit: Founded solution(prehaps temporary?):
Turning on vpn and then join the server then disable vpn for some reason seem to bypass the issue, although high ping still existed but atlease I can join the server now
Best response
What you haven't shared is the error message you got: whether this was before, during, or after handshake, and what error code you got. Newer builds show an error code that should indicate if there was a problem with the networking.

If the error code was 0, your connection was shutdown by the remote server or something upstream from you. That would be something outside of our control. I know several SS13 servers have run into this, especially ones in Russia due to the ongoing conflict and how various agencies have responded. A VPN might potentially help solve those issues, but that's hard to say.
In response to Lummox JR
Yea it's was error code 0, My mistake for not sending the error code and it's during handshake. The server load the chat and some part of status windows before it's load anymore, I think it's safe to say that my remote connection was shutdown either by remote server or something upstream. I will try to use VPN to see if the problem will be solve or not
Hey please mark this as solve please I have found solution and edited into my post