SYSTEM STATUS
Component checks, run against the live platform at the moment you loaded this page. What is checked, how, and what we do not measure is set out below.
What this page measures
No uptime percentage is published on this page. Nothing in this platform records availability history, so there is no thirty-day or ninety-day figure that could be honestly calculated. Two cards used to sit here, a thirty-day and a ninety-day figure. Both were typed into a file by hand rather than measured, and both have been removed rather than restated. They will come back when a monitor exists to produce them, with a link to the monitor.
What you can see is the check below. The database figure is a real round trip made when you loaded the page. The remaining components report whether they are configured on this deployment, which is a weaker claim than a probe, and they say so on each row rather than showing a green tick that means something else.
The availability target we contract to, and the service credits attached to it, are in Terms §10 and on the support page. A target is not a measurement and this page will not present one as the other.
Components
Incident log
How you find out
Major incidents are emailed to account admins. That is the notification path that exists. There is no public subscribe list on this page and no form to join one — if you have been told otherwise, that claim has been removed.
For anything urgent, email support@accolade.live. Your plan's first-response target and the P1/P2/P3 severity definitions are published on /support.
Thinking about running your awards on Accolade?
The Free plan runs a full event on the same codebase and the same database as every paid tier. No card, no sales call to get in.