☰

Timed Out

Players are disconnected with a timeout, or the client reports the server stopped responding. Either the network connection between client and server is unstable, or the server froze long enough to miss keep-alive packets.

What does this error mean?
Client and server exchange keep-alive packets. If too much time passes without a reply, the connection is dropped as 'Timed out'. The cause is either a network problem or a server-side freeze (a long tick or GC pause) that stops it answering in time. 
Timed out
Most Common Causes
  • Network instability, packet loss, or poor routing.
  • A server-side freeze or long garbage-collection pause.
  • An overloaded CPU missing keep-alive responses.
  • A bad client-side connection or Wi-Fi.
  • A restrictive firewall interfering with the connection.
How To Diagnose
  1. Check whether one player or everyone times out, everyone points to the server.
  2. Look for freeze/GC pauses in the console around the disconnect.
  3. Test latency and packet loss with a ping/MTR to the server.
  4. Watch CPU usage for spikes coinciding with timeouts.
Recommended Fixes
  • Stabilize the server
    Fix TPS lag and GC pauses (Aikar's flags, profiling) so it always answers keep-alives.
  • Investigate the network
    Resolve packet loss or routing issues between players and the host.
  • Add CPU headroom
    Reduce load or upgrade hardware so the main thread never stalls.
  • Check firewalls
    Ensure no firewall or anti-DDoS layer is dropping legitimate traffic.
Analyze My Log
Frequently Asked Questions

If everyone times out together, it is the server. If only you do, suspect your own network.

Yes, a long freeze stops the server replying to keep-alives, which the client reads as a timeout.

Run an MTR or continuous ping to the server IP and watch for dropped packets.