Operations · Status
Public status, soon enough.
We don't publish a status page that says 'all systems operational' when production traffic is still ramping. That kind of decoration tells you nothing. The real surface launches with our first production customer, when there's something honest to report.
Public status page Q3 2026
When it launches
What the public page will cover.
The shape of what we're building, with enough detail to decide whether to wait for us or to design around the gap in the meantime.
- Component healthRetrieval API, ADT subscription, webhook delivery, sandbox environment, identity service. Per-component status and historical uptime.
- Incident timelineReal-time incident updates, including the actual root-cause writeup once an incident closes. We don't soften incident postmortems.
- Scheduled maintenanceAdvance notice of any deployment that affects partner-facing endpoints. Read across our customer status banners as well.
- Network upstreamsStatus of the upstream networks we depend on — CommonWell, Carequality, TEFCA participants, Surescripts. When their incidents become ours, you'll see it here.
In the meantime
Get early access or talk to an engineer.
Enterprise customers receive direct SLA-backed status reporting via their support channels today, including notifications of upstream network incidents before they become customer-visible.