Is Cloudflare down right now?

Partly. Cloudflare's status page lists CDN Cache Purge (degraded performance). Open incident: “Fedramp Customers have Delayed Purges”, identified, posted November 6, 2026, 17:47 UTC. 130 other components are operational (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes). Its data center locations are listed separately: 57 of 342 are flagged right now (23 major outage, 32 degraded performance and 2 under maintenance). The page-level indicator in the feed reads “Partial System Outage”; Datvero answers from the service components and the open incidents, and shows the locations separately.

From August 27 to November 6, 2026, www.cloudflarestatus.com lists 68 incidents: 1 critical, 6 major, 56 minor and 5 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.4 h. Longest: “Incorrect geo location for some Cloudflare WARP users” (August 27, 2026), 55.9 days. In the last 30 days: 67 incidents, 7 of them major or critical.

Cloudflare publishes it at https://www.cloudflarestatus.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Cloudflare.

When the status page is green but your site shows a Cloudflare error page, read the error code. Cloudflare’s documentation describes 520 as “web server returns an unknown error”, 521 as “web server is down” and 522 as “connection timed out”, and says that when troubleshooting most 5xx errors the correct course of action is to first contact your hosting provider or site administrator. Start with your own origin server.

The status page lists what Cloudflare has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Cloudflare succeeds.

Cloudflare lists its data center locations as components next to its services. When some locations are flagged, the page-level indicator of its status feed can read “Partial System Outage” even though every service component is operational. Datvero answers from the service components and the open incidents, and shows the locations in a separate table with their own counts.

Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.