Skip to content

Incident and Status Page

Ankit Upadhyay edited this page Jul 24, 2026 · 2 revisions

Incident and Status Page

How platform health is surfaced and how incidents are communicated.

Status page

Platform status is published via a status page (OpenStatus). It gives users and integrators a single place to see uptime and any ongoing incidents.

Automating incident creation

Today, incidents are largely posted manually. Issue #1608 tracks automating status-page incidents via an OpenStatus agent webhook — so a detected outage opens (and updates) an incident without a human copy-pasting. This closes the loop between monitoring and public communication.

Related monitoring

  • Application quality/security signals flow through SonarCloud, CodeQL, and Aikido — see Code Quality Gates and Security.
  • Realtime/backend health during an incident: see Realtime Setup for what is actually wired today (Stream chat, BullMQ workers) versus designed-only.

Reporting a security incident

Security vulnerabilities are not handled through the status page — follow the confidential process in Security.

Related

Product & Domain
Architecture
Applications
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Roadmap
Operations
Meta

Canonical code & docs: main repo · Auto-generated companion: DeepWiki

Clone this wiki locally