Why Are gats.io Servers Not Loading or Connecting?

Updated

If gats.io servers won't load or connect, the cause is usually on the game's side, not yours. The site itself has displayed a notice that the servers weren't loading because of a DDoS attack ("ik the servers aren't loading, some guy is ddosing us again"), and the stats page has shown as "Down for maintenance." In that situation the practical response is to wait and retry later, and to watch the changelog or the linked Discord for updates rather than changing your own setup.

What the site itself indicates

The gats.io page carries several signals that explain a failed load or connection:

  • A DDoS notice on the server list. The site has stated the servers weren't loading due to an ongoing DDoS attack. This is an attack on the game's infrastructure, so nothing on your device will fix it.
  • Stats marked "Down for maintenance." The stats view has shown this status, which means stat lookups can fail even when other parts of the site respond.
  • A Discord link for updates. The page references a Discord channel alongside the maintenance notice, which is where status updates are most likely to appear.
  • A changelog link. The page includes a "View Changelog" link, useful for confirming whether a fix or change has shipped.

What you can check on your end

Before assuming an outage, rule out the ordinary causes. These are general troubleshooting steps, not site-specific features:

  1. Reload the page and retry the connection. Use the page's reconnect option or reload the browser tab, then try joining again. Transient failures often clear on a second attempt.
  2. Confirm you're on a supported device. The site explicitly states that mobile devices are not supported by gats.io. If you're on a phone or tablet, the game itself won't run; the stats site at stats.gats.io is offered separately for mobile.
  3. Check whether the server list loads at all. If the public server list is empty or stuck on "Loading…", that points to the game's servers rather than your connection. If the list loads but a specific server won't connect, the problem may be that server.
  4. Try a different server or game type. The server browser lists Public, Custom, and Private servers across FFA, TDM, and DOM. If one entry fails, another may still connect.
  5. Check the changelog and Discord. These are the two places the site points to for status, so they're the fastest way to learn whether an outage is known and being worked on.

If you're hosting your own server

Custom and private servers are hosted from the site, and the host page notes that "Your server will automatically stop if it has been empty for a while," and that "A new server can be launched as soon as the old one has stopped." If your hosted server appears unreachable:

  • Check whether it has already stopped after being empty, and launch a new one if so.
  • Use the invite link shown after hosting to reconnect, or the manage panel to stop and restart it.
  • Remember that a new server can only start once the old one has fully stopped.

When to just wait

If the DDoS notice is showing or stats are down for maintenance, the failure is upstream. Retrying later, and checking the changelog or Discord in the meantime, is the only reliable path. Repeated reloading during an active attack won't help, and no local setting change will bring the servers back.