Why this page cannot answer “down right now” with a badge
This is a November 9, 2026 evidence snapshot, not an uptime service. We do not probe every game world or inspect your connection. A historical incident, a player’s failed entry and a current developer maintenance announcement are different kinds of evidence. Only the last can establish what the developer has announced for the named time and region; it still needs a date and a clear scope.
Official: Kefir’s community-contact help lists its Discord and social channels. The Steam news hub provides dated developer posts. Use those destinations rather than an unofficial status headline with no timestamp. We found no verified universal maintenance calendar or restart interval in the sources reviewed here, and we have not confirmed a dedicated real-time status endpoint. An absence of a notice is not proof that every server is healthy.
Step by step: check scope, time and your symptom
Open the official news hub and the communities linked by Kefir. Find the newest relevant notice and compare its date, time zone, region and affected service with your own case. A fresh-server announcement is not a recovery notice. Read whether an update announces a plan, an active issue or a completed recovery; do not convert one into another simply because it is the latest post.
Then record what failed for you: launching the application, reaching the server list, entering Looty Bay or entering only one base. Include your region and server identifier if visible. Our suggestion is to compare reports only when they describe the same destination and time. Friends failing together is useful evidence for a report, but it is not a direct measurement of every region’s availability.
If there is no matching announced incident, follow the relevant official help instead of repeatedly changing networks or reinstalling. Kefir’s loading article supplies connectivity, restart, driver and file-verification checks. A specific error code can narrow that path. Completing a local check does not prove the remote service is up, and a retry succeeding establishes only that your own attempt worked at that moment.
If there is still no clear answer
Send support a concise description with the exact message, the attempt time and time zone, region, destination and checks already tried. Use a screenshot with private information hidden. Avoid saying “all servers are down” when you have only tested one. If you are citing another report, preserve its timestamp and region rather than merging several different failures into one supposed outage.
We do not promise a recovery time, automatic compensation or account restoration. A comment that someone waited successfully is not a service guarantee. If the developer gives an estimated return time, treat it as the developer’s dated estimate and check for later updates. Our editorial page cannot substitute for a current operational notice or inspect whether your particular world has resumed normal service.
Opening schedules are not downtime schedules
Official: the November 4 First Changes announcement describes fresh daily server openings in EU and East US, with additional worlds opening as needed. It does not turn those opening plans into recurring maintenance or a simultaneous global restart. The wipe-schedule guide covers progression resets separately. Keeping opening, wiping, maintenance and unexpected failure distinct prevents an old schedule from becoming a false “servers return at” prediction.