Wide Cloudflare service outage lasting 121 minutes
Your team operates a large edge platform that provides Workers compute, Zero Trust access, and CDN control-plane functions to millions of customers. On the morning of January 24, 2023, a wide cross-section of these products simultaneously becomes unavailable or severely degraded. The incident lasts 121 minutes before recovery. No targeted infrastructure component appears to be failing in isolation — alerts fire across Workers, Zero Trust, and CDN control-plane simultaneously. On-call engineers notice the timing of the outage correlates precisely with a recent code release. Customers report authentication failures, broken Workers invocations, and inability to update CDN configuration. The platform's data-plane traffic continues to flow for cached content, but any action requiring a control-plane call or authenticated token fails. Teams scramble to identify a common dependency shared by all three affected product lines. What architectural safeguard would you implement before the next platform release to prevent a single shared component from taking down all three product lines?