outages.live
Live
CloudflareIncident ·

Fedramp Customers have Delayed Purges

DegradedOfficial update
0

Cloudflare CDN Cache Purge has delayed purges for Fedramp customers. Stale content may be served until it expires. Non-Fedramp customers are not affected. Cloudflare identified the problem and continues to work on a fix.

State

Identified

Started

Ongoing for

22 h 39 min

Worst impact

Degraded

Timeline

2 updates
17:4723:2705:0610:4616:26
DegradedUpdate postedTimes in UTC

Investigating

13 min 1%

Identified

22 h 26 min 99%

Updates

Times in UTC

As posted by Cloudflare

Identified

We are continuing to work on a fix for the issue.

Investigating

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

1
CDN Cache Purge

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

77

Days with an incident

72

Median duration

1 h 33 min

This incident

15× the median

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

56 days
median 1 h 33 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Network Performance Issues in Chicago

Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.

Resolved

Cloudflare·Spectrum Availability Issue in Phoenix

Cloudflare reports an issue with Spectrum availability in Phoenix. This issue can degrade existing Spectrum applications. Cloudflare is monitoring the situation for further issues.

Degraded

Cloudflare·Partial System Outage

Cloudflare reported a partial system outage that affected 20 locations. These locations include Albuquerque, Sydney, Bangalore, Kyiv, and other points of presence. Cloudflare reports that the outage is resolved. It lasted 423 minutes.

Resolved

Cloudflare·Wrangler Deployments, Pages, and Workers Builds failures

Cloudflare Wrangler deployments, Pages, and Workers Builds had failures in uploads. Cloudflare reported the incident as resolved. The incident lasted 21 minutes.

Resolved

Cloudflare·Network Performance Issues in Singapore

Cloudflare reported network performance issues in the Singapore region (SIN). The incident is resolved. It lasted about 1 hour and 50 minutes.

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.

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane