Status
Is StoneReason working?
Operational Every component this deployment measures is answering its check; one component is not measured at all
Components last checked 2026-09-12 12:34 UTC. The page itself is rendered when you load it and is never cached; the components are looked at every ten seconds, so the time above is when they were last seen rather than when you asked.
Components
Each row says what was checked. A component that is operational over “the process answered” is a weaker statement than one that is operational over “a request was served end to end”, and you should be able to tell which you are reading.
| Component | State | What was checked |
|---|---|---|
| Website stonereason.com and the documentation | Operational | you are reading a page it served |
| Accounts sign-up, sign-in and the dashboard | Operational | this page was rendered by the account service itself |
| API the request path: balance reads and network status | Operational | the developer surface answered a status request over loopback |
| Payments watching for a payment and settling it | Operational | the acquisition runner is following 9 networks |
| Monitor and webhooks arbitrary watches and event streams | Not deployed here | the Data plane this needs is not attached to this deployment |
| Verify answering what a claim is worth | Not deployed here | no capability row on this deployment is commercially available |
| MCP the Model Context Protocol surface | Not deployed here | not deployed here |
| Payment networks the chains a payment watch can be opened on | Operational | the acquisition runner holds routes for 9 networks and has read a head from 9 |
| Access networks the chains an API key can be scoped to | Not checked | nothing on this deployment probes the access engines periodically, and reading their lifecycle takes a customer key this page does not have |
Incident history
No incident has been published on this deployment. That is not a measurement of uptime — nothing here measures availability, and the absence of an incident means only that nobody has published one.
What this page cannot tell you
There is no uptime figure. Nothing on this deployment measures availability, so any percentage here would be invented. The absence of an incident is a fact about what an operator published, not about what happened.
This page runs on the host it reports on. There is one host. If it is gone, so is this page — it cannot report its own outage. A page you cannot reach has told you something.
Incidents are published by a person. Nothing here is written by a monitor. An internal alarm is not a public statement, and a monitor that could publish would eventually publish something wrong to everybody at once.
There is no SLA. Free Beta makes no availability commitment, and this page reports what was observed rather than what was promised.