Fedramp Customers have Delayed Purges
Cloudflare CDN Cache Purge has delayed purges for FedRAMP customers. The problem started 13 minutes ago. Cloudflare has identified the issue and continues to work on a fix. Stale content may be served until it expires. Other customers are not affected.
State
Identified
Started
Ongoing for
21 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
13 min 63%
Identified
8 min 37%
Updates
Times in UTCAs posted by Cloudflare
We are continuing to work on a fix for the issue.
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.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
71
Median duration
1 h 36 min
This incident
78% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reported a partial system outage. The outage affected 20 locations, including Albuquerque, Bangalore, Sydney, Kyiv, and Nairobi. Cloudflare reports that the outage is resolved. It lasted 7 hours and 3 minutes.
Cloudflare·Wrangler Deployments, Pages, and Workers Builds failures
Cloudflare Wrangler deployments, Pages, and Workers Builds failed. The incident affected Pages, Workers Builds, Wrangler, Developer Services - Pages, and Developer Services - Workers Builds. Cloudflare reported the incident as resolved after 21 minutes.
Cloudflare·Network Performance Issues in Singapore
Cloudflare reported network performance issues in the Singapore (SIN) region. Cloudflare reports that the incident is resolved. The incident lasted about 1 hour and 50 minutes.
Cloudflare·Workers Builds Issues
Cloudflare Workers Builds had degraded performance. The incident is resolved. It lasted 29 minutes.
Cloudflare·Network disruption across multiple colocations in India
Cloudflare reported a network disruption across multiple colocations in India. The disruption degraded Cloudflare services in the region and affected Cloudflare R2 in Asia Pacific. Cloudflare identified 9 impacted colocations in India and removed them from the network. The incident is resolved and lasted 72 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