SEVERITY

Severity 0 (Critical)

Critical emergency. The system is completely unusable for a significant portion of users, or data integrity is at risk.

SEV0

Critical emergency. The system is completely unusable for a significant portion of users, or data integrity is at risk.

"Everything is on Fire"

SEV0 (Severity 0) is the highest level of emergency. It means the core product is completely broken, detailed user data is being deleted, or a security breach is active.

Criteria

  • Availability: Critical user flows (Login, Checkout) are failing for >10% of users.
  • Data: Data corruption or loss is occurring.
  • Security: Active intruder or public leak of PII.

The Response Mode

During a SEV0, normal change controls may be shortened through a documented break glass process. Move quickly, but keep an audit trail and verify that the mitigation is safer than the ongoing impact.

ExThe Black Friday Crash

An eCommerce site went down completely at 9am on Black Friday due to traffic load.

Impact
Lost $100k revenue per minute.
Resolution
Team provisioned 500 extra servers in 10 minutes, bypassing all cost controls. Revenue recovered.

Why SEV0 Matters

Every second of SEV0 equals lost revenue and trust.

Requires immediate "all hands on deck" response.

May require approved "break glass" procedures to bypass normal change controls safely.

Common Pitfalls

Analysis Paralysis
Debating "is this really SEV0" while the system burns. Declare first, downgrade later.
Solo Heroics
Trying to fix a SEV0 alone. Page the right responders immediately.
Silent Fixing
Fixing the issue without telling anyone, so no one knows *why* it recovered.

How to Use SEV0

🚨
Automated Paging: Ensure PagerDuty/Opsgenie wakes people up.
📢
Status Page: Update status within 5 minutes. Silence breeds panic.
👥
War Room: Open a voice bridge/Zoom immediately.

Frequently Asked Questions

Put this into practice.