Cloudflare: Cache Purging Delays in Amsterdam
Affected components: CDN Cache PurgeCDN & Performance - CDN Cache Purge
Timeline of updates
- investigating
Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API is delayed in Amsterdam. We are working to resolve this issue as soon as possible. Until then you may use the Purge Everything feature but do be aware it may cause a surge in traffic to your origin server(s). More updates to follow.
- identified
The issue has been identified and a fix is being implemented.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on www.cloudflarestatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Cloudflare, started 2026-11-20 18:00 UTC, resolved after 1.7 h, 4 update(s); edited after publishing.
- Title
- Cache Purging Delays in Amsterdam
- Vendor
- Cloudflare
- Date
- URL
- https://rewindex.com/company/cloudflare/incidents/xsgbfncq7of7
Cloudflare profileRecent Cloudflare incidentsAll outages on November 20, 2026Cloudflare in November 2026MarkdownJSON