ProductReliability Center
A reliability record your customers can check.
Commitments with their attainment, uptime, incidents and the method behind every number, on your status page's own address. Each customer can open their own contract view.
Commitments, uptime and incidents
How Acme measures and reports its reliability: published targets with their attainment, 90 days of uptime, recent incidents with postmortems, and the services it depends on.
Published targets
Attainment is the share of measured time each service met its target, with scheduled maintenance and disclosed exclusions removed. It is not the uptime figure below.
97.8%uptime
All services, Jul 9 to today
- Outage days
- 2
- Degraded days
- 7
- Measured downtime
- 46m
Uptime over the last 90 days, all services: 97.8%. 2 days with an outage. 7 days degraded. 46m of measured downtime.
Bars show the last 30 days; the figures above cover all 90.
- Operational
- Degraded
- Outage
- No data
- Incident or maintenance reported
- July (23 days)95.7%1 outage day
- August100%4 degraded days
- September96.7%1 outage day, 2 degraded days
- October (6 days)100%1 degraded day
Last 90 days
2 published incidents. Postmortems are linked where one was written.
The change was rolled back. Error rate is back under 0.1%.
Replication caught up after the storage volume was resized.
Declared, not monitored
Services Acme relies on, as declared by Acme. Observer does not monitor them, so no live status is shown here.
Methodology
Observer records the status of each check behind a published target. Attainment counts the samples that met the check's thresholds; degraded counts as up, scheduled maintenance and disclosed exclusion windows are removed, and how unobserved time is treated is disclosed with each figure. A target is met when attainment is not below it; figures are truncated, never rounded up. Uptime counts days instead, and is shown separately.
Commitments, uptime and incidents
How Acme measures and reports its reliability: published targets with their attainment, 90 days of uptime, recent incidents with postmortems, and the services it depends on.
Contract: Enterprise SLA 2026
Attainment so far this period against your contracted targets, measured in Europe/London.
Signed monthly statements
Each statement is signed. Download it, then check it on the verify page.
Published targets
Attainment is the share of measured time each service met its target, with scheduled maintenance and disclosed exclusions removed. It is not the uptime figure below.
97.8%uptime
All services, Jul 9 to today
- Outage days
- 2
- Degraded days
- 7
- Measured downtime
- 46m
Uptime over the last 90 days, all services: 97.8%. 2 days with an outage. 7 days degraded. 46m of measured downtime.
Bars show the last 30 days; the figures above cover all 90.
- Operational
- Degraded
- Outage
- No data
- Incident or maintenance reported
- July (23 days)95.7%1 outage day
- August100%4 degraded days
- September96.7%1 outage day, 2 degraded days
- October (6 days)100%1 degraded day
Last 90 days
2 published incidents. Postmortems are linked where one was written.
The change was rolled back. Error rate is back under 0.1%.
Replication caught up after the storage volume was resized.
Declared, not monitored
Services Acme relies on, as declared by Acme. Observer does not monitor them, so no live status is shown here.
Methodology
Observer records the status of each check behind a published target. Attainment counts the samples that met the check's thresholds; degraded counts as up, scheduled maintenance and disclosed exclusion windows are removed, and how unobserved time is treated is disclosed with each figure. A target is met when attainment is not below it; figures are truncated, never rounded up. Uptime counts days instead, and is shown separately.
The public page
What a buyer asks for, before they ask.
Turn it on per status page in the page builder. Everything on it is read from the page's own metrics and incidents, and each customer can be given a private view of their own contract.
Commitments
Targets, with their attainment.
ProEach SLO you publish, with its attainment for the month to date and the three months before, and whether the target was met.
Uptime
Ninety days, counted in days.
A 90-day calendar of the page's status, shown apart from attainment so the two are never mixed up.
Incidents
With their postmortems.
The page's public incidents from the last 90 days, each with its postmortem when you wrote one.
Dependencies
Declared, not monitored.
The services the page relies on, as you declare them in the page builder, with no live status implied.
Address
On your status page's domain.
At /reliability on the page's subdomain or custom domain, linked from its footer. A private page keeps its password, IP or JWT access.
Customer view
Their targets, their numbers.
BusinessA private link per customer and page adds their contract lines, their attainment so far this period and every statement delivered to them. The link is shown once and never stored, expires after 90 days by default and can be revoked.
SLA Ledger
Credits calculated, not argued.
When a month closes, every contract line gets its attainment and the credit its tiers give, with the arithmetic printed on the statement. On the Business plan and above.
Statement
Globex, September 2026
Enterprise SLA 2026
- Target
- 99.9%
- Attainment
- 99.751%
- Result
- Missed
- Coverage
- 99.79%
43,003 ÷ (43,003 + 107) × 100 = 99.751%
Below the 99.9% tier: 10% credit.
Daily attainment, September 2026
| Day | Attainment | Available | Down | Unknown | Excluded | Coverage |
|---|---|---|---|---|---|---|
| 2026-09-01 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-02 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-03 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-04 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-05 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-06 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-07 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-08 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-09 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-10 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-11 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-12 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-13 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-14 | 93.389% | 1342 | 95 | 3 | 0 | 99.79% |
| 2026-09-15 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-16 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-17 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-18 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-19 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-20 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-21 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-22 | 99.164% | 1425 | 12 | 3 | 0 | 99.79% |
| 2026-09-23 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-24 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-25 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-26 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-27 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-28 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-29 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
| 2026-09-30 | 100.000% | 1437 | 0 | 3 | 0 | 99.79% |
The Ledger in the console: every statement for the period, what waits for a person, and the credits owed.
01Contract
The terms, per customer.
SLO lines with their targets, credit tiers, a cap and the monthly fee. Each statement freezes the contract it was computed under.
02Calculate
Credits from the tiers, not by hand.
When a period closes, each line gets its attainment and the credit its tier gives. Exactly on a threshold earns nothing, and a line with too little data is flagged for review instead of credited.
03Approve
Draft, review, approved.
Statements can wait for approval, and the approver can be required to differ from whoever prepared it. A correction is a new revision; the old one is kept.
04Deliver
Signed, in three formats.
The customer gets an email with the figures and, when the Reliability Center is on, a link to their view. Every statement downloads as PDF, CSV or JSON, hashed and signed.
Verification
Anyone holding a statement can check it.
Paste a statement's JSON on the verify page. The hash is recomputed and the Ed25519 signature checked against the published keys. Nothing is looked up, so a changed figure cannot pass.
Paste
The statement JSON
- customer
- Globex
- period
- September 2026
- lines[0].attainment_pct
- 99.751797
- summary.credit_pct
- 10
- sha256
- b5ae902ab6…fea4d2
- signature
- /qyj17S3…ayDA==
- signing_key_id
- demo-2026-10
The check
- sha256 of the payload, recomputed
- b5ae902ab62ed46153367ffe55a64014a7effbba61197dcee2451d3a61fea4d2
- Matches the statement's sha256
- Yes
- Ed25519 signature
- Valid, published key
Verified
This sample
The real check, on a sample statement.
The statement above was signed for this page with a throwaway key, and each result is what the verify function returned for it. Real statements are signed with Observer's published key.
Methodology
How it is measured.
Degraded counts as up unless the contract says otherwise, scheduled maintenance and disclosed exclusions are left out, and figures are truncated, never rounded up. Each statement names the methodology version it used.
Read the SLA methodologyPlans
Public on every plan.
What each plan adds
The page itself has no plan gate. What fills it grows with the plan.
Every plan
The public page.Uptime, incidents, dependencies and the methodology.
Pro
Published commitments.Public SLOs with their attainment, month by month.
Business
Access links and the SLA Ledger.Contracts, calculated credits and signed statements.