Service status: which components are answering right now.
Your browser probes the public API's liveness route every 30 seconds and this page reports what came back, alongside the component states the provenance read already publishes. It is a check of what is answering this second — not a health check of every internal component, and not an availability measurement: nothing here is retained across a reload.
| Component | State | Observed | What the state is read from |
|---|---|---|---|
| Public API | — | — | The liveness route, requested by this browser every 30 seconds. |
| Market data feed | REAL | 3 of 4 sources real-time | The provenance read — per-source detail on data sources. |
| Reasoning engine | REAL | online | The same provenance read: whether the engine behind extraction and AI-assisted narratives is configured and reachable. |
0 probes since you opened this tab · 0 failed. Counted in this tab only, and reset by a reload — which is exactly why no percentage is derived from them.
What this page does not measure
Every figure below is one a status page is expected to carry. None of them has a measurement behind it today, so each reads as an em dash with the reason rather than a number.
| Figure | Published | Why there is no number |
|---|---|---|
| Monthly uptime percentage | — | The liveness route is stateless and this tab retains nothing across a reload, so no probe history exists to divide. A percentage here would be invented. |
| Trailing 90-day availability | — | Same missing history. In the pipeline: a server-side probe that records every check; until it has run for 90 days this stays an em dash. |
| Mean time to recovery | — | No incident register is published, so there are no resolved incidents to average. |
| Incident history | — | Same register. When it exists, past incidents will be listed here with their start, end and cause. |
The availability target, the downtime formula, the exclusions and the service-credit schedule are published in advance on service levels, which also states what has to exist before any of it binds. Feed-by-feed provenance is on data sources, and the sealed audit chain underneath the published claims is on the data-status page.