Measuring now
The first round of checks is running.
Rechecks every 15 s while this tab is visible. Nothing here is estimated: a check that cannot be measured says unknown.
Requests your own browser makes right now. If these fail, the problem is between you and us, or with us.
Checks our API runs on itself and reports. Each is cached for a few seconds and carries its own timestamp.
Pulse lines plot the latency of this visit’s own samples, newest on the right, on a fixed 0 to 1.5 s scale. Red ticks are failed checks, hollow dots are unknowns. Nothing is drawn for time before you opened the page.
Two kinds of evidence appear on this page, and each row says which it is. Browser checks are requests your own device makes. Dependency checks are run by the API on its own host and handed to you. Open any row above to see exactly how it is judged.
The checks use real timeouts and real responses. When a check cannot run, for example because the API is unreachable, its row reads unknown. It is never defaulted to green.
What is not covered: the authenticated real-time event stream needs credentials, so it is not probed from a public page. The protocol gateway row shows that the router answers, not that stream events are flowing.
curl -s https://www.forticia.uk/api/healthcurl -s https://www.forticia.uk/api/status/checksThe second endpoint is public, read only and cached for a few seconds. It reports a state, a timestamp and a latency for each dependency, and nothing about the host.
| Check | Measured by | Method | Operational | Degraded | Down |
|---|---|---|---|---|---|
| Web application | Your browser | Your browser requests the site root without cache and reads the response headers. | An HTML document is returned with HTTP 200 in under 1.2 s. | The round trip takes longer than 1.2 s, or a non-200 success code is returned. | No response, no answer within 6 s, or an HTTP 5xx error. |
| API gateway | Your browser | Your browser requests GET /api/health and checks the body. | HTTP 200 with {"ok":true} in under 1.2 s. | The answer takes longer than 1.2 s, or the body is not what the endpoint documents. | No response, no answer within 6 s, or an HTTP 5xx error. |
| PolarisLink protocol gateway | Your browser | Your browser requests GET /api/polarislink/spec and checks that a JSON document naming the protocol comes back. | HTTP 200 and a JSON document with a protocol field, in under 1.2 s. | HTTP 429, a slower answer than 1.2 s, or a body without the expected field. | No response, no answer within 6 s, an HTTP 5xx error, or the route is missing (HTTP 404). |
| Database | Our servers | The API runs a trivial query over its own database connection and times it. | The query returns in under 750 ms. | The query succeeds but takes longer than 750 ms. | The query fails or does not return within 2.5 s. |
| Data archive | Our servers | The API opens the archive root and reads its first entry, then times it. | The root is readable, not empty, and answers in under 1 s. | The root is readable but empty, or answers slower than 1 s. | The root is missing or unreadable, or does not answer within 2.5 s. |
| Mail intake | Our servers | The API opens a TCP connection to the listener and reads its SMTP greeting. No message is sent. | A greeting starting with 220 arrives in under 1 s. | A greeting arrives but is unexpected or slower than 1 s. | The connection is refused, or no greeting arrives within 2.5 s. |
| Agent heartbeats | Our servers | The API counts heartbeat records from non-human nodes received in the last 5 minutes. | At least one agent heartbeat arrived in the last 5 minutes. | Not used. Silence cannot be told apart from idleness. | Not used. With no recent heartbeat the row shows as unknown instead. |
No incident history is recorded yet.
This page shows what can be measured at this moment. Past incidents, 30 day and 90 day uptime figures are not displayed because nothing stores the results of earlier checks. We would rather leave the space empty than publish a percentage we cannot back.
If something looks wrong while this page is green, tell us through the contact page. A check we do not run cannot show up here.