Sample inputs
Sample working view
Outage Duration85 mins
SLA CommitmentBREACHED (99.95%)
Financial SLA Liability$11,250.00
Preventative Actions3 items
3 sample rows
| Action ID | Preventative Remediation | Single-Threaded Owner | Due Date | Definition of Done | Status |
|---|---|---|---|---|---|
| ACT-01 | Add automated multi-tenant load tests to CI gate | Priya S | 2026-11-15 | CI fails if connection pool > 80% | OPEN / ASSIGNED |
| ACT-02 | Implement circuit breaker on token validation | David K | 2026-11-10 | Graceful fallback to replica read | OPEN / ASSIGNED |
| ACT-03 | Audit all queries for connection pool release | Marcus T | 2026-11-20 | Zero unindexed lookups in codebase | OPEN / ASSIGNED |
Read the sample report
BLAMELESS SRE POST-MORTEM & INCIDENT REPORT Incident: Production API Gateway 502 Bad Gateway Outage Severity Tier: P1-Critical | Outage Duration: 85 minutes Contractual SLA & Financial Liability Analysis: - Contractual Monthly Billing: $45,000.00 | Committed Uptime: 99.95% - Permissible Monthly Downtime: 21.6 minutes | Excess Downtime: 63.4 minutes - SLA Status: BREACH OF CONTRACT (25% credit penalty tier) - Total Customer SLA Refund/Credit Liability: $11,250.00 Root-Cause Five-Whys Investigation: Why 1: Why 1: API gateway instances failed health checks and refused traffic. Why 2: Why 2: Redis connection pool was exhausted by a spike in unindexed lookups. Why 3: Why 3: A newly merged feature bypassed read-replica caching for tenant tokens. Why 4: Why 4: Load tests only covered single-tenant scenarios prior to release. Why 5: Why 5: Staging CI/CD pipeline lacks automated multi-tenant concurrency tests. Remediation & Reliability Commitments: 3 single-owner action items committed to prevent repeat failures. All items tracked with strict due dates.
SLA penalty calculation uses standard tiered credit schedules. Individual master service agreements (MSAs) may specify custom penalty caps.