Cache Purging Delays Affecting Requests Routed Through EEUR
This incident has been resolved.
The latest update from Cloudflare.
State
Resolved
Started
5 d ago
2026-10-27 15:10 UTC
Lasted
1 h 4 min
until 2026-10-27 16:14 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
52 min 81%
Monitoring
12 min 19%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Some single-file cache purge requests (purge by URL) submitted through the Dashboard or API and routed through our EEUR purge queues are experiencing delays of up to 30 minutes. Cache invalidation for these requests may be delayed across our global network. This also affects Always Online. We are working to resolve the issue. As a temporary workaround, you may use Purge Everything, but this may cause a surge in traffic to your origin server(s) More updates to follow.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
66
Median duration
1 h 15 min
This incident
About the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial outage that affects 20 locations, including Dallas, Frankfurt, Sydney, Nairobi, and Bangalore. Cloudflare is investigating the problem. The outage started at 21:45 UTC on 31 October 2026.
Cloudflare·Cache purge delays in Qingdao Shandong, China
This incident has been resolved.
Cloudflare·Increased Errors for Browser Run
This incident has been resolved.
Cloudflare·R2 Elevated Latency in Eastern Europe
This incident has been resolved.
Cloudflare·Increased Errors for Durable Objects and Downstream Services in Eastern North America (ENAM)
This incident has been resolved.
Follow Cloudflare
Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=cloudflare/feed subscribe https://outages.cc/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane