Status and incidents
Where to look when something is wrong, and what we commit to telling you.
status.digitalyser.io carries the live state, the incident history, and an RSS feed you can subscribe to.
What the probes actually test
A status page that pings hosts tells you the edge answered. Ours tests capabilities:
| Component | What is verified |
|---|---|
| MCP endpoint | A refusal still carries its re-authorisation challenge — not just that something replied |
| Authentication & OAuth | Discovery documents are served and still name an authorization server and S256 |
| API | The public readiness probe |
| Applications | Dashboard and site over their public hostnames |
| Certificates | Expiry, well before it becomes an incident |
Probes run against public URLs, from outside our own network. A probe living inside the infrastructure it watches stays green through an edge outage — which is precisely when you need it to be honest.
Third-party dependencies
Model providers, database, CDN. When one of them degrades, you will see it named on the status page with a link to their own status, because "it is not us" is not an answer you can act on.
Incidents
Every incident gets a timeline: what broke, what we know, what changed, and when it closed. If the cause was ours, the page says so.