Service status
No ORVEXIA product is in general availability yet, so there is no live uptime to report. This page explains what will appear here, how we classify an incident and how you will hear about one.
Where each service stands today
These are the services this page will monitor once they are live. Until then the only honest status is the one below.
What this page will show
Component status
One row per service, updated as its state changes: operational, degraded, partial outage or major outage.
Uptime history
Measured availability over a rolling window, published from our own monitoring rather than a figure we choose.
Incident timeline
Every incident with its start, its updates and its resolution, kept online afterwards instead of quietly deleted.
How we will classify an incident
So that the words on this page mean the same thing every time.
How you will hear about it
This page first
An incident is posted here as soon as we have confirmed it, not once it is fixed. Updates follow while it is open, and the page states plainly when we do not yet know the cause.
Direct email for affected customers
If an incident affects your data or your access specifically, we contact you directly. We do not rely on you noticing a status page.
A written follow-up
After a significant incident we publish what happened, what the impact was and what we changed so it does not happen the same way again.
Security is separate
A security issue follows the process in our Trust Center and our security.txt, not this page alone.
Incident history
There is no incident history because there are no production services yet. We are not going to fill this space with a clean record we have not earned. The first entry will appear the first time something goes wrong after launch.