A condition that made it worse or let it through, such as a missed review.
default-config-unchanged47 cases · 2017 to 2026
monitoring-blind-spot43 cases · 2017 to 2026
assumption-unverified35 cases · 2017 to 2026
blast-radius-too-wide32 cases · 2017 to 2026
automation-amplified29 cases · 2017 to 2026
single-point-of-failure29 cases · 2017 to 2026
limit-unknown18 cases · 2019 to 2026
retry-storm16 cases · 2019 to 2026
early-signal-ignored14 cases · 2017 to 2025
overlapping-failures14 cases · 2017 to 2026
staging-not-representative14 cases · 2019 to 2026
manual-action-worsened13 cases · 2017 to 2026
limited-debug-access13 cases · 2019 to 2025
no-spare-capacity13 cases · 2019 to 2026
no-staged-rollout13 cases · 2020 to 2025
no-alert-on-limit12 cases · 2019 to 2026
no-safeguard-on-destructive-change12 cases · 2019 to 2026
delayed-effect-change11 cases · 2019 to 2026
no-runbook10 cases · 2021 to 2026
known-bug-unpatched9 cases · 2018 to 2025
review-missed7 cases · 2019 to 2026
no-capacity-planning7 cases · 2019 to 2025
no-config-tests7 cases · 2020 to 2023
no-resource-limits7 cases · 2019 to 2025
skipped-upgrades6 cases · 2022 to 2026
revert-did-not-restore4 cases · 2017 to 2025
no-caching4 cases · 2019 to 2025
no-health-probe4 cases · 2018 to 2025
partial-rollout3 cases · 2019 to 2024
failure-delayed-by-cache2 cases · 2024 to 2025
change-in-peak-hours2 cases · 2025 to 2026
credential-coupled-to-config2 cases · 2023 to 2024
probe-depends-on-dependency2 cases · 2025 to 2026
backup-unverified2 cases · 2021 to 2023
config-not-in-code1 case · 2023
test-coverage-gap1 case · 2023
paging-failed1 case · 2022
shared-credential1 case · 2023
unpinned-version1 case · 2024