Service status
- Status
- Current
- Updated
- 2026-09-13
- Scope
- ZaunEkko Status
ZaunEkko Status answers one question: can these services be used right now.
It does not explain how to integrate with them — that is this site's job — and it does not explain why something broke.
Four states
State is carried by text, shape and colour together, never colour alone:
| State | Shown as | Meaning |
|---|---|---|
OPERATIONAL | Operational | The probe succeeded |
DEGRADED | Degraded | Reachable but behaving abnormally |
UNAVAILABLE | Unavailable | The probe failed |
UNKNOWN | Unknown | No usable sample yet |
A four-colour legend sits at the bottom of the page, so the status bars explain themselves on a first visit.
The 90-day bar
Below each component is a bar of daily aggregates covering 90 days. Hover, touch, or use the left and right arrow keys to select a cell and see that day's date, state and actual sample count.
"No data" and "operational" are not the same thing, and the bar distinguishes them. Days before this site existed have no samples and are not filled in green — painting untested days as healthy misleads more than leaving them blank.
Refresh interval
The page refreshes every 30 seconds. If a refresh fails it keeps the last successful result and says plainly that it cannot update right now — stale data is never dressed up as current.
Subscribing to incidents
/feed.atom is an Atom feed of incidents. Any feed reader can consume it.
Public JSON
Two anonymous, cross-origin readable endpoints:
| Path | Contents |
|---|---|
/api/v1/status | Current state |
/api/v1/history | 90-day daily aggregates |
No credentials required. They return exactly what the page shows — nothing more.
What this site does not provide
The page and the JSON both answer "is it usable", not "why". Response latency, HTTP status codes, error text and diagnostic entry points are not among them — do not write a parser expecting those fields.
To investigate your own calls, use receipts and error codes: Authentication and calls.
Versus the summary on the main site
ZaunEkko carries a small status summary too, but it is only a hint. Full component state, history and incidents live on the status site, which is the one to trust.