Capability
SLA evidence & outage proof
When a vendor fails, bring a timestamped, independently measured record to the credit conversation - not screenshots.
Who this is for
Anyone who pays for a vendor SLA - SaaS operators, platform teams, agencies billing clients for reliability - and has learned that claiming credits with “the site was down for a while” goes nowhere.
Why vendors honor structured evidence
Credit decisions belong to the vendor and your contract. What changes the outcome is the quality of the record: per-minute observations from regions the vendor does not control, an exact degradation window in UTC, correlated customer impact, and a checksum binding the report to your organization.
What a report contains
- Dependency, failure window (UTC), and severity.
- Per-region observation timeline: latency, status codes, outcomes.
- Quorum verdict and methodology reference.
- Correlated customer impact from your incident history.
- Computed credit figure under your plan’s SLA clause.
- SHA-256 checksum and public verification reference.
What verification discloses - and what it never does
The public verification endpoint confirms a report exists and matches its checksum. It never discloses endpoints, headers, credentials or account details. Reports belong to the organization that generated them and are exposed publicly only through explicit share links.
Honest scope
Evidence documents observed behavior; it is not by itself a legal determination of fault or a contractual credit - those remain governed by your agreements. RELIASTRA reports correlation and leaves causation to the engineers reading the timeline.
What to do next
Read the evidence docs, see how attribution works, or upgrade to Pro to generate reports.
Know when your dependencies fail. Prove what happened.
Monitor the external APIs your product relies on, correlate their failures with your incidents, and generate verifiable evidence when a vendor causes downtime.