ORDENTRA goes live for design partners in Q2 2026. Until then, there’s no production traffic to report on — this page will become the live system status dashboard at GA, with per-region availability, p99 latency, incident history, and scheduled maintenance windows.
Infrastructure health is monitored internally during pre-launch. If you want to know when the live dashboard goes live, subscribe below.
A short preview of the surface that replaces this placeholder at GA. Every card below ships live with Q2 2026 general availability.
Live availability for every ORDENTRA service across every production region, refreshed from synthetic probes.
API, dashboard, webhook delivery and data pipeline latency at p50, p95 and p99, bucketed per region.
Every resolved incident with a written post-mortem — root cause, corrective action, and verification steps.
Forward-looking maintenance calendar with affected services, per-region windows, and subscriber notifications.
Four design principles we are engineering the ORDENTRA incident-response runbook against. These are design goals, not contractual commitments — the contractual side lives in the Trust centre.
Our target recovery-time objective for a customer-impacting incident is under 60 minutes. This is the design goal we are engineering against, not a contractual commitment.
Every incident — regardless of blast radius — gets a written post-mortem within five business days, covering root cause, corrective action, and verification steps.
Affected customers are notified directly, in addition to the status page, during and after an incident. Notification is part of our incident-response runbook, not an afterthought.
A customer-visible changelog accompanies every deploy that ships behaviour changes, integration updates, or security patches. Transparency is the default.
Looking for security posture, SLA terms, or the contractual side of incident response? Those live on the Trust page, not here.
Visit the Trust centre