No canonical incident/history feed.
The frontend has no authoritative incident chronology, uptime percentage, SLA window, or maintenance feed to publish. Nothing is inferred from absence.
Status / observed 2026-08-11T08:48:34.576Z
Current truth without marketing interpretation.
This page reports the latest generated observation available to the website. It does not infer uptime, incident-free history, or a service-level agreement from a successful probe.
Observed snapshot
Lifecycle and proof stay separate.
A family can serve requests while having demonstrated only a returned quote. The status surface never collapses those facts into one green label.
- Public callable
- observed yes
- Families serving
- 5 / 6
- Routes answering
- 88
- Incident history feed
- not bound
Family health
Six permanent families. Current observed state.
Source: packages/catalog/live-registry.json. Permanent product names stay frozen even when generated registry labels differ.
SESearchpaid outcome verifiedliveno current reason published
AIAIpaid outcome verifiedliveno current reason published
SBSecure Sandboxpaid outcome verifiedliveno current reason published
RPMulti-chain RPCnothing demonstratedunavailablecommercial rights blocked
PRPredictionquote observed, unpaidliveno current reason published
CICrypto Intelligencequote observed, unpaidliveno current reason published
Incidents and limitations
No history feed means no invented history.
A current probe is not an uptime series. Without a canonical incident/history source, this page cannot truthfully say “zero incidents” or “all systems operational.”
Observed constraints remain visible.
1 families are currently unavailable in observed truth; 1 routes are supply paused; First Revenue Release readiness is not ready.