When did the network stop being reachable? Signed.
SLA credits and interconnect disputes turn on two facts that both parties argue after the event: when a network's reachability started to degrade, and who observed it. Each operator points at its own dashboard, and the dashboards disagree. This page returns a signed, independently re-verifiable receipt of an autonomous system's live global BGP routing health from an outside vantage, plus the current public status of a named cloud or service, so the record is not one operator's screenshot against another's. A neutral third party observed it, timestamped it, and every reading Dynamic Feed serves is archived, so what the record said at time T stays re-checkable.
Global reachability for a network, right now.
Enter an autonomous system number (an ASN, for example AS13335 for Cloudflare) and, optionally, a named cloud or service. Dynamic Feed records the live global BGP routing reachability of that ASN from an independent vantage and the current public status of the named service, and returns one Ed25519-signed Decision Receipt produced by /v1/answer. Nothing is mocked and nothing is stored about you.
full signed receipt (JSON)
SLA disputes are decided on records.
When a network SLA reaches dispute, or a peering and interconnect disagreement escalates, the argument is rarely whether there was degradation; it is when it started, how long it lasted, and whose measurement to believe. Each side has its own NMS, its own status page, its own timestamps, and they do not line up. A contemporaneous record from an independent witness, observed from a global vantage outside either operator's network, signed at the moment, carrying its source and observation time, and verifiable years later against a published key, is corroboration both sides can check. Routing reachability is a strong signal because it is visible worldwide: a sharp drop in how many of RIPE's global route collectors see the network is an outage signal no single operator controls.
Evidence, not an SLA measurement.
Dynamic Feed is a neutral witness, not a carrier, regulator or adviser. Routing health is global BGP visibility via RIPEstat (RIPE NCC), an external control-plane signal, not a packet-loss or latency measurement inside either network, and it does not localise a fault to a specific link or region. Service status reflects the public status surface plus Dynamic Feed probes for the named service. This is a live-now receipt: it records what these sources reported at the moment you request it, not a reconstruction of a past outage window. It does not compute the contractual SLA figure, does not interpret the agreement, and SLA terms, measurement methods and credit formulas vary by contract, carrier and jurisdiction. Advisory evidence for a dispute file, tamper-evident not tamper-proof, zero personal data, not a certification or a compliance ruling, and not legal advice.
One API call per incident file.
Network operations and SLA platforms can mint a signed reachability-and-status receipt the moment an incident opens, keyless to try, self-serve to scale.