Cloudflare outage on November 6, 2026: Fedramp Customers have Delayed Purges
Cloudflare has reported an incident affecting Cloudflare since 17:47 UTC on 6 November 2026 (1 hour 10 minutes so far).
Open
Official incident reported by Cloudflare
- Started
- 17:47
- 6 Nov 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 1h 10m
- 1 hour 10 minutes so far
- Impact
- Minor
- as rated by Cloudflare
- Updates
- 2
- posted by Cloudflare
Timeline
All times UTC.
Official incident from Cloudflare
Fedramp Customers have Delayed Purges
-
Official
Investigating
Cloudflare has identified a bug with our purge pipeline impacting fedramp customers. Stale content may be served until expired. Non-fedramp customers are not impacted.
-
Official
Identified
We are continuing to work on a fix for the issue.
"Official" rows are quoted from Cloudflare's public status page, www.cloudflarestatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test cloudflare.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Cloudflare status shows what our checks see right now.
Does your product depend on Cloudflare?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Cloudflare. Official updates are quoted from Cloudflare's public status page and remain Cloudflare's own words.