Live / Cloudflare / Incident
Cloudflare: Fedramp Customers have Delayed Purges
Cloudflare · cloudflare.comMinor incidentResolved2026-11-12 16:36 UTC
Public — what happened
Summary
Cloudflare said that customers on its FedRAMP offering were seeing delays when clearing cached content, a process it calls purging. The company reported that old versions of content might keep being served until they expired on their own, and that customers outside FedRAMP were not affected. It said on November 6 that it had found a bug in its purge system and was working on a fix. Cloudflare marked the incident resolved on November 12 without giving further detail.
Affected
CDN Cache Purge
Timeline
- Started — 2026-11-06 17:47 UTC
- Investigating — 2026-11-06 17:47 UTC
- Identified — 2026-11-06 17:59 UTC
- Resolved — 2026-11-12 16:36 UTC · 6 days after it started
What SquidGrid measured
SquidGrid measured 276 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.