Cache Purging Delays in Amsterdam
Cloudflare single-file cache purging by URL through the Dashboard or API was delayed in Amsterdam. Cloudflare reported the incident as resolved. It lasted 1 hour and 41 minutes.
State
Resolved
Started
Lasted
1 h 41 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 41 min 100%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
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.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
126
Days with an incident
85
Median duration
1 h 30 min
This incident
About the median
Other Cloudflare incidents
All incidentsCloudflare·Cloudflare Dashboard and Cloudflare API service issues in EU region
The Cloudflare Dashboard and Cloudflare API have service issues in the EU region. Cloudflare reports that the incident is resolved and that it lasted 29 minutes. Cached file delivery through the Cloudflare CDN and the security features at the Cloudflare Edge were not affected.
Cloudflare·Network Performance Issues in Miami
Network performance is degraded in Miami, United States (MIA). Cloudflare reports that the incident is resolved. It lasted about 9 hours and 27 minutes.
Cloudflare·R2 and Durable Objects availability issues
R2 and Durable Objects had intermittent errors and failed requests in Eastern North America. Cloudflare implemented a fix and monitored the results. Cloudflare reports that the incident is resolved and it lasted 102 minutes.
Cloudflare·Observability ingestion delay and query failures
Cloudflare Workers Observability and Cloudflare Traces had delays in new data ingestion and increased query errors. The incident affected the Workers and Workers Observability components. Cloudflare reports that the incident is resolved, and it lasted about 5 hours and 26 minutes.
Cloudflare·Durable Objects and D1 – Increased Errors
Cloudflare reported increased errors and latency on Durable Objects and D1 for a subset of customers; Workers that do not use these components were not affected. Cloudflare identified the problem and implemented a fix. The incident is resolved and lasted about 32 minutes.
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.live/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.live/feed.xml?providers=cloudflare/feed subscribe https://outages.live/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane