Is Cloudflare down?

What works right now

• ●UpEdge networkYes: Cloudflare-proxied sites are being served.200 in 187 ms
• ●UpAPIYes: the dashboard, wrangler and Terraform can make changes.200 in 307 ms

Failing for you? Check whether it is you

1. Is it you? Read the error number

   521 (origin down), 522 (origin timed out), 523 (origin unreachable), 524 (origin too slow), 525 and 526 (origin TLS) mean Cloudflare is up and your server is not answering it. 520 is an unexpected reply from your origin.

What to do while Cloudflare is down

When Cloudflare is down, sites proxied through Cloudflare, Workers, Pages, R2 or 1.1.1.1 may fail, often only in some regions. The API and dashboard can be down while sites still serve.

1. Bypass the proxy

   If the dashboard or API works, set the site's DNS records to "DNS only" (grey cloud). Traffic goes straight to your server, so it needs its own TLS certificate, and your origin IP becomes public.

2. 1.1.1.1 not resolving

   Point your device or router at another resolver until it is back.

   8.8.8.8 / 8.8.4.4 (Google)
   9.9.9.9 (Quad9)

   Copy

3. Check your region

   Cloudflare reports by data center. The official page lists them; a reroute in one city often shows as slow, not down.

Last 24 hours

Last 30 days

Incident timeline

Outages our checks saw, and incidents from the official status page, newest first.

1. OfficialOct 24, 1:01 UTC · 2.1 hNetwork Performance Issues in Ashburn

   This incident has been resolved.

2. OfficialOct 23, 15:47 UTC · 2.9 hNetwork connectivity issues affecting services in North America

   This incident has been resolved.

3. OfficialOct 23, 15:27 UTC · 5.2 hDelayed, missed, and duplicated Workers Cron Triggers

   This incident has been resolved.

4. OfficialOct 23, 9:01 UTC · 21 minCloudflare Access Availability Issues

   This incident has been resolved.

5. OfficialOct 22, 17:01 UTC · 30 minElevated errors for some requests in Ashburn, Virginia

   This incident has been resolved.

6. OfficialOct 22, 15:33 UTC · 43 minCloudflare Workers API Latency

   This incident has been resolved.

7. OfficialOct 21, 19:15 UTC · 2.1 hElevated Errors for R2 and Durable Objects in ENAM

   This incident has been resolved.

8. OfficialOct 21, 16:42 UTC · 3.2 hIncreased Latency in India

   This incident has been resolved.

9. OfficialOct 20, 3:20 UTC · 3.2 hCloudflare Zero Trust connectivity

   This incident has been resolved.

10. OfficialOct 19, 11:28 UTC · 23 minDNS Update Delays

    This incident has been resolved.

11. OfficialOct 18, 8:00 UTC · 50 minNetwork Performance Issues in Virginia and Ohio United States

    Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the r

12. OfficialOct 16, 17:56 UTC · 1.2 hCloudflare Fedramp Dashboard and Access

    This incident has been resolved.

13. OfficialOct 16, 12:58 UTC · 5 minIncreased HTTP 5xx Errors Ashburn

    Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD). The incident is now resolved, and systems are fully operational.

14. OfficialOct 16, 10:15 UTC · 1.2 hCloudflare Dashboard sign up issues

    This incident has been resolved.

15. OfficialOct 16, 9:20 UTC · 38 min Cloudflare Access Availability Issues

    This incident has been resolved.

16. OfficialOct 16, 6:48 UTC · 42 minNetwork Performance Issues in Thailand

    Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.

17. OfficialOct 16, 1:13 UTC · 58 minNetwork issues in Incheon (ICN)

    Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since r

18. OfficialOct 16, 0:01 UTC · 1.1 hWorkers Cron Triggers issues

    Workers Cron Triggers have stabilized

19. OfficialOct 15, 20:48 UTC · 50 minNetwork Performance Issues in Eastern North America

    This incident has been resolved.

20. OfficialOct 15, 17:33 UTC · 13 minNetwork Performance Issues in London

    This incident has been resolved.

21. OfficialOct 15, 16:42 UTC · 4.7 hPages.dev sites experiencing availability issues in Norway

    This incident has been resolved.

22. OfficialOct 15, 16:05 UTC · 5 minNetwork Performance Issues in Kuala Lumpur

    Cloudflare resolved an incident where we observed network performance issues in our Kuala Lumpur (KUL) facility. Customers may have observed elevated error rates and/or increased latency today, 2026-10-15, between approximately 16:10 and 16:15 UTC.

23. OfficialOct 15, 15:33 UTC · 2.8 hDNS Update Delays

    This incident has been resolved.

24. OfficialOct 15, 10:47 UTC · 9.9 hIncreased HTTP 502 Errors

    This incident has been resolved.

25. OfficialOct 14, 7:43 UTC · 8 minIncreased HTTP Errors in London (LHR)

    Cloudflare is aware of, and has resolved, an increased level of HTTP errors in London (LHR), between 07:43 UTC and 07:51 UTC. Services have resumed normal operation after this time.

Official status

The official page: https://www.cloudflarestatus.com/.

Get alerts, or show it in your README

Follow the RSS feed of Cloudflare incidents in any reader, or paste this badge into a README; it updates itself.

[![Cloudflare status](https://tensorust-status.vercel.app/api/badge?id=cloudflare)](https://tensorust.com/status/cloudflare/)

How we check Cloudflare

Every 5 minutes, from Washington, D.C., with no API key. A failed check is retried once after 2 seconds before it counts; Cloudflare is down when every critical check fails, and degraded when some do or the official page reports a problem.

• https://www.cloudflare.com/cdn-cgi/trace: A Cloudflare-proxied site answering from the nearest edge.
• https://api.cloudflare.com/client/v4/ips: api.cloudflare.com (dashboard, wrangler and Terraform use it).

Other services