Platform status.
Not yet instrumented
We are not publishing live component health or trailing uptime figures, because
we are not yet measuring them in a way you could hold us to. The dedicated status
service at status.sumeru.systems is being provisioned; when it serves
real telemetry, this page redirects to it and this notice comes down.
Until then, what follows is what we have actually committed to in writing, and how we will tell you when something breaks. If you need availability evidence for a procurement review before the status service is live, ask us in the architecture review and we will walk you through the monitoring we run internally.
In the contract, not the copy.
Every figure below comes from the published SLA. Marketing pages on this site quote these numbers and are not permitted to quote tighter ones - see src/data/claims.ts.
Service credits on breach are tiered - see /legal/sla. Third-party platform outages (Shopify, Google, Meta) are reported to you but are not counted against Sumeru's SLA.
How you will hear about it.
Detection to notice
Critical incidents get a first notice within 30 min of detection, to the technical contacts on your account, whether or not we have a diagnosis yet.
During
Updates on a stated cadence until resolution, including what is degraded, what still works, and whether queued actions will replay or be dropped.
After
A written post-incident review for any Sev-1, covering cause, customer impact, and the specific change that prevents a repeat. Shared, not summarised.
What the live page will cover.
Nine components, reported independently. Listed here as scope - not as current health, because we are not measuring it yet.
Get on the incident list.
Tell us who on your side should receive incident notices and we will add them when the status service goes live. Email or webhook, filterable by service and severity.