Status

How we report reliability

We do not publish an uptime percentage. We do not yet run the independent monitor that would make one worth reading, and a figure we calculate about our own availability, with no third party checking it, is marketing rather than evidence. When that monitor is in place, its number will appear here with a link to the source.

What we publish instead is the thing an uptime figure is a proxy for: every incident that affected customers, posted here with what happened, when it started, when it ended, and what we changed. Incidents are never removed from this page once posted.

The check above runs from your browser against our API each time you open this page. It is a live signal, not a history — a failed check can be your network as easily as ours, which is why it never on its own changes the status above.

Incident history

No incidents reported.

This log starts 4 August 2026, when we published this page. An empty list means nothing has been reported since that date — not that nothing ever happened before it.

Something wrong on your side?

If the product is misbehaving and nothing is posted here, we probably do not know yet — tell us through our contact page and we will look. For a suspected vulnerability, use the reporting route on our security page rather than this one.