The outage happened. Prove it.
SLA credits and downtime insurance claims stall on the same question: what actually happened, and says who? The provider's status page is the provider's own word, and it can be edited after the fact. Screenshots prove little. What survives the dispute is a signed, independently re-verifiable receipt of what the status surface and independent probes showed at the moment, retained in the signed archive. A record both sides can check, which is exactly why it works for either side.
A signed receipt for a service, right now.
Name a service. Dynamic Feed records what its public status surface and our own probes currently show, optionally cross-checks BGP routing visibility via RIPEstat, and returns one Ed25519-signed Decision Receipt produced by /v1/answer. Nothing is mocked and nothing is stored about you.
full signed receipt (JSON)
Downtime disputes are decided on records.
When you file for an SLA credit or a parametric downtime payout, the burden of evidence sits with you, and your best exhibit is usually the provider's own status page, captured after the incident, from the party with every incentive to minimise it. A contemporaneous record from an independent witness, signed at the moment, carrying its sources and observation times, and verifiable years later against a published key, changes the conversation: it is no longer your word against theirs. Dynamic Feed already runs continuous probes for its own reliability reporting; this page turns one moment of that visibility into a portable, signed exhibit. Our records work against us just as well as they work for you: anyone can re-check them, including the provider.
Evidence, not the SLA verdict.
Dynamic Feed is a neutral witness, not an arbiter. This receipt is a record of what public status surfaces, Dynamic Feed's own probes and RIPEstat BGP visibility showed at that moment. It is not the provider's contractual SLA measurement: SLA definitions, measurement windows and exclusions vary by contract, so check yours. A status indicator is the provider's own published state, and the BGP signal is routing visibility; neither alone proves or disproves an outage at your endpoint. Advisory evidence, tamper-evident not tamper-proof, zero personal data, and not legal advice.
One API call per incident window.
Ticketing systems, MSP tooling and parametric downtime products can mint a signed outage receipt the moment an incident opens, keyless to try, self-serve to scale.