Cloudflare reports roughly 25 minutes of disruption affecting approximately 28% of HTTP traffic.
Cloudflare · inspect the source ↗INCIDENT BRIEF / SERVICE OUTAGE
Cloudflare December outage: a secondary configuration change can dominate the rollout
A gradual software rollout provides limited protection if a related operational flag changes everywhere immediately. Map every change channel used during mitigation, including internal testing controls. Decide the acceptable failure behavior explicitly; do not generalize this incident into advice to disable security checks. Use the preserved provider account below to distinguish reported facts from the proposed review exercise.
01 / SOURCE-ATTRIBUTED REPORTING
What the evidence establishes.
The provider distinguishes a gradual buffer-size rollout from a second global change disabling an internal WAF testing tool.
Cloudflare · inspect the source ↗Cloudflare says the affected combination was its older FL1 proxy with the Cloudflare Managed Ruleset; its China network was excluded.
Cloudflare · inspect the source ↗02 / KEEP THE SEQUENCE
A dated record.
Reported incident date
Cloudflare reports roughly 25 minutes of disruption affecting approximately 28% of HTTP traffic.
Source reference ↗
Dates and time zones follow the cited report where specified. A report date is distinct from the incident date and from our review.
03 / GOVERNATLAS EDITORIAL ANALYSIS
Make the lesson useful.
These are proposed review and trial activities inspired by the reported event. They are not completed tests or claims that a particular control guarantees prevention.
Include operational flags in release safety
A gradual software rollout provides limited protection if a related operational flag changes everywhere immediately. Map every change channel used during mitigation, including internal testing controls. Decide the acceptable failure behavior explicitly; do not generalize this incident into advice to disable security checks.
BRING THIS INTO YOUR REVIEW
Open the working guide ↗Rehearse an authorized configuration-only rollback on representative proxy and policy combinations. Record which deployment mechanism carries each flag, the canary boundary and a workload-level stop condition.
FROM READING TO A REVIEW YOU CAN OWN
What will you examine next?
A reported failure is a reason to ask a precise question about your own service. It does not establish that your configuration shares the same weakness. Start with the workflow, deployment and dependencies you can identify, then decide which proposed activity is relevant.
For each relevant lesson, name an accountable role, describe the evidence you would request and define an authorized trial before performing it. Keep “not checked” distinct from a recorded observation. If a check reveals a gap, retain its scope and next action rather than converting the observation into a supplier-wide verdict.
Use this portable record in a review, renewal discussion or continuity exercise. A material configuration change, a revised incident account or the completion of an action can trigger your next review. Your entries remain your working notes; publication evidence and your own acceptance decision are separate records.
Use non-sensitive roles and evidence references. Entries stay in this open page and reset on reload; download before leaving. This tool performs no tests and produces no readiness score.
1 unassigned owner · 1 activity not checked
Define a safe, measurable rehearsal
Record the normal result before changing anything. Agree an authorized test boundary, an observable stop condition and who can stop the exercise. Check restored configuration and unfinished work separately. These entries are your plan, not permission to test a service.
04 / LEAVE UNCERTAINTY VISIBLE
What this record does not establish.
This is an attributed review of a preserved provider account, not an independent reconstruction or a finding about current reliability.
Customer-specific losses, exposure and recovery outcomes are not established by these passages. The proposed exercise has not been performed by GovernAtlas.
Geography: The report describes service scope below. No single affected-user location is inferred from infrastructure, company headquarters or routing origin.
05 / THE EVIDENCE RECORD
Sources & editorial review.
Cloudflare outage on December 5, 2025 ↗
Cloudflare · captured 2026-10-17 (UTC)
Inspect preserved provenance
- Source
- 15ea93fd-8edb-4eeb-bd9f-301f256e5db3
- Observation
- ba9884f8-aa8d-4d9e-95e9-e8fb157d8b5f
- SHA-256
- 3fc05dc49866f83d3b2302b3f2d515ec280b9dc850e3bc69554c6ef4dd6e05e8
Reporting and proposed methods by GovernAtlas editorial. Published review: 2026-10-17 (UTC). Revision 1. Preserved source bytes identify the material reviewed; they do not independently verify the provider’s account.
Submit a correction with supporting evidence ↗