Status
Service status
What is running, what is degraded, and how we tell you when something breaks.
Everything is working
Checked 16 Oct 2026, 09:50
Website and application
The pages themselves, in every language and on every device.
OperationalSign-in
Signing in, verification, password reset, and invitations.
OperationalData processing
Baselines, monitoring runs, scoring, and everything queued behind them.
OperationalExternal source coverage
Our ability to read the public review platforms a clinic is listed on. A platform can be unavailable to us while everything else works.
OperationalReports
Weekly and monthly reports, their PDFs, and shared links.
OperationalEmail
Alerts, reports, and every transactional message we send.
OperationalBilling
Checkout, subscriptions, invoices, and the customer portal.
Operational
Each component is checked every five minutes against the records the work itself writes. We publish four states and no numbers: what a customer needs to know is whether they can use it.
How incidents work
What to expect
When a component is degraded or unavailable, the status page will name the component, the impact, the time it started, and the current state. Updates continue until the incident is resolved, and a short summary is published afterwards.
Delayed data collection is treated as an incident, not a silent state: where a clinic's intelligence is stale because collection failed, the product says so on the affected screens rather than showing old numbers as if they were current.