These events are not evidence that all managed services are untrustworthy. They show why claims of “fully managed,” “secure,” or “automatic updates” must be tested against change control, customer visibility, recovery rights and access to evidence.
DOCUMENTED VENDOR POSTMORTEM
CrowdStrike / July 2024
What failed: A content-configuration update triggered widespread Windows crashes.
Operator lesson: Stage and validate updates; bound rollout scope; retain rollback and independently observable health signals.
Boundary: A Clawsolator manager could not have prevented this Windows sensor failure.
Source: Read the primary incident report ↗
DOCUMENTED VENDOR POSTMORTEM
Cloudflare / November 2025
What failed: A permissions change altered generated Bot Management data and affected network-wide traffic.
Operator lesson: Use change validation, configuration size checks, control-plane health tests, blast-radius segmentation and alternative paths.
Boundary: Self-hosting does not make an upstream connectivity provider immune to outages.
Source: Read the primary incident report ↗
DOCUMENTED VENDOR POSTMORTEM
Atlassian / April 2022
What failed: A script operated with the wrong IDs, removing customer sites; restoration took days.
Operator lesson: Require object identity, script scope, deletion mode, dry-runs, dual review and recovery plans.
Boundary: Human approval alone would not prove the target IDs were correct.
Source: Read the primary incident report ↗
DOCUMENTED VENDOR POSTMORTEM
Okta / September–October 2023
What failed: Files accessed through a support system included tokens usable for session hijacking.
Operator lesson: Redact support exports, scope support access, avoid uploading reusable secrets and rotate compromised credentials.
Boundary: A local container does not protect sessions already exposed via a support workflow.
Source: Read the primary incident report ↗