Public Status Page
Last updated: 26 August 2026
The platform exposes a public status endpoint that reports whether the service is healthy. It's the endpoint a studio (or its players) can check during an incident, and the one an external uptime monitor or a shared status dashboard can poll — no credentials required.
The status endpoint is unauthenticated by design. It reports platform health only — it never exposes project data, and it's safe to link from a public game or support page.
What it reports
The status surface has three read-only views:
| View | What it returns |
|---|---|
Current (/status) | The platform's health right now. |
History (/status/history) | Recent health over time, for spotting a recent dip or a resolved incident. |
Federation (/status/federation) | The set of related status origins, so several status pages can point at one another. |
Health is self-reported by the platform's own monitoring and rolled up on a schedule, so the current view reflects the most recent poll rather than a live per-request probe.
Using it
Because the endpoint is public, checking it is a plain unauthenticated GET — from a browser, an uptime monitor, or a support page. The current view is the one to poll for a simple up/down signal; the history view backs a small "recent status" widget; the federation view lets a multi-region or multi-tenant setup present a combined picture.
Treat the status endpoint as a coarse health signal for humans and monitors, not as a data API. For per-function health inside your own project, use the health dashboard in Functions.
Next steps
- Functions — the per-function, per-environment health dashboard inside your project
- Alerts & Notifications — get told when health changes instead of polling