Live

Cache Purging Delays in Milan

Cloudflare CDN Cache Purge delays affected single-file cache purging (purge by URL) through the Dashboard and API in Milan. Cloudflare reported the incident resolved after 94 minutes. Cloudflare stated that the Purge Everything feature was available as a workaround and could cause a surge in traffic to origin servers.

State

Resolved

Started

Lasted

1 h 34 min

Worst impact

Notice

Timeline

4 updates
20:5121:1521:3822:0122:25
NoticeUpdate postedTimes in UTC

Investigating

6 min 6%

Identified

1 h 9 min 74%

Monitoring

19 min 20%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident is now resolved.

Monitoring

A fix has been implemented and we are currently monitoring the results.

Identified

The issue has been identified and a fix is being implemented.

Investigating

Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API is delayed in Milan. 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

1
CDN Cache Purge

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

129

Days with an incident

87

Median duration

1 h 31 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 31 min
90 days agoToday

Other Cloudflare incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane