All of these are public and live under / (or under your own domain, see
Your Own Domain). They never show IP addresses, node addresses or server
identifiers. Names are the ones you chose in Components.
| Address | What it is |
|---|---|
/ | The page. Add ?lang=en or ?lang=es to force a language, and ?theme=name to preview a design. |
/ | The current status as JSON. |
/ | An RSS feed of incidents. |
/ | A small status badge. |
If you turn off Page is public in Settings, all of them answer 404.
The RSS feed
feed. lists open and recent incidents, one entry each, with its title, status, time and
latest message. It is for people and tools that read feeds: feed readers, a Discord or
Slack channel connected with an RSS tool, or an automation such as Zapier or n8n. A page
without incidents has an empty feed, which is normal.
The JSON summary
api/ is built for your own integrations. Its main parts:
{
"generated_at": "2026-10-14T03:13:52+00:00",
"overall": { "status": "operational" },
"groups": [
{
"name": "Frankfurt",
"components": [
{
"name": "Node FRA-1",
"status": "operational",
"uptime": { "90": 99.98 },
"bars": [{ "day": "2026-10-14", "state": "ok", "uptime": 100 }]
}
]
}
],
"incidents": { "active": [], "recent": [] },
"maintenances": []
}
overall. is one of operational, degraded, partial, major and maintenance.
Each bar state is ok, degraded, down, maintenance or none (no data that day).
Minecraft components also carry the player count and version. The summary is cached for a
few seconds.
The badge
badge. is a small image that says status | operational in a color that matches the
current state: green, orange, red or blue for maintenance. It is cached for one minute.
Embed it anywhere:
<img src="https://your-panel/status/badge.svg" alt="Status">
In Markdown:
Previous: Notifications · Next: The Uptime Tab for Customers