What this page checks
Database
Your records, the audit log and AI history.
Live check: a query runs each time this page loads.
OperationalAI engine
eAvy and the specialist agents.
Configuration check: the provider is set up, not called. An incident we declare shows here too.
Not reportedBackground jobs
Notifications, escalations, digests and webhooks.
Configuration check: the job runner is set up. An incident we declare shows here too.
Not reportedSign-in and storage
Sessions, single sign-on and file storage.
Configuration check: the service is set up. An incident we declare shows here too.
Not reportedWe publish no uptime figure until we measure one.
Incident history
Past incidents
The incident log starts with this page, on 13 October 2026. Each incident is written here as it happens, kept with its updates, and published as a feed you can follow.
Follow the incident feed (RSS)Monitor it yourself
Point your monitor at the health endpoint. It always answers 200, with a status of ok or degraded and a database check in the body.
https://app.eaviora.com/api/health
Something wrong on your side?
Customers can write to contact@eaviora.com with their organisation’s name.