System status

What we commit to publish

When HIBR goes live in October 2026, this page becomes a real-time dashboard. Specifically:

• Per-component status updated every 60 seconds — operational / degraded / partial outage / full outage
• Historical uptime — 30-day, 90-day, and 12-month rolling percentages per component
• Active incident feed — open incidents with timeline, impact scope, current mitigation
• Past incident archive — every incident kept publicly visible with root cause and resolution timing
• Scheduled maintenance calendar — published at least 72 hours in advance for any planned downtime
• RSS + webhook subscriptions — for ops teams to wire HIBR status into their own monitoring

Incident classification

Every incident is tagged with one of four severities. The classification governs response time, communication frequency, and SLA credit eligibility (see the SLA for credit details).

• SEV-1 — Critical: Full production outage affecting all customers, or data integrity at risk. Status update every 30 minutes minimum.
• SEV-2 — Major: Major function impaired (e.g., payment processing, VAT engine, or bank feeds offline). Status update every 60 minutes.
• SEV-3 — Minor: Limited function impacted or affecting subset of customers. Status update every 4 hours.
• SEV-4 — Cosmetic: Workaround available, low business impact. Status update at resolution.

Where incident notifications go

When an incident is declared:

• This page updates first, within 5 minutes of incident declaration
• Subscribers (email + RSS + webhook) receive notification within 10 minutes
• Customers actively in-product see an in-app banner within 15 minutes
• For SEV-1 / SEV-2 affecting an account specifically, the named contact receives an SMS within 30 minutes

Post-incident reviews

For every SEV-1 and SEV-2 incident, a public post-incident review (PIR) is published within 5 business days. The PIR documents what happened, root cause, customer impact, what we changed to prevent recurrence, and timeline. We do not delete or revise PIRs after publication.

Launch monitoring milestones

The road to a live status dashboard: