Cloudflare Zero Trust connectivity
This incident has been resolved.
The latest update from Cloudflare.
State
Resolved
Started
12 d ago
2026-10-20 03:20 UTC
Lasted
3 h 12 min
until 2026-10-20 06:32 UTC
Worst impact
Major outage
Timeline
9 updatesInvestigating
1 h 20 min 41%
Identified
4 min 2%
Monitoring
1 h 48 min 56%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
The Cloudflare Access API has been fully restored, with error rates and latency returning to normal levels. We continue to monitor these services.
The Cloudflare Access API continues to experience higher-than-normal error rates and increased latency. We are working to resolve the remaining API issues. Edge functionality, including Access logins and Cloudflare Secure Web Gateway connectivity, has been fully restored. We continue to monitor these services.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to investigate the issue.
We are continuing to investigate the issue.
We are continuing to investigate the issue.
Cloudflare is investigating an issue with traffic that goes through Cloudflare One Gateway when an identity policy is present in the policy decision. This impacts all onramps to Cloudflare One Gateway. Cloudflare One Gateway policies with no identity policy are unaffected. We are also seeing impact to the Cloudflare Dashboard and are investigating further.
Affected components
4Cloudflare in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
66
Median duration
1 h 15 min
This incident
2.6× 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