Service status

The checks above run in your browser against the public endpoints, so they reflect what your network can reach, which may or may not reflect what your server can reach. See minsec-sync(1) for ineracting with minsec.io services from your server(s).

What runs where

The site and the API are deliberately independent: documentation staying up when the API is down is a feature, not an accident.

If the API is unreachable

Nothing on your server stops working. minsec itself never talks to the network — only minsec-sync does, and it is on a timer, not a daemon. A failed run:

• leaves your existing crowd4/crowd6 sets in place, unchanged;
• leaves unreported bans in the events log, to be sent on the next successful run;
• retries in five minutes.

A 503 feed_not_ready or 503 zone_not_ready means the backend is up but has not finished building a snapshot — usually the minute or two after a deployment. Retry; do not treat it as an empty list.

Reporting a problem

Mail delist@minsec.io for a wrongly listed address, or open an issue at the minsec repository for anything else. Include the output of minsec-sync status if the problem is multiplayer-related; it contains cursors and enrollment state, no log content.