Skip to main content
Cloudflare logo

Is Cloudflare Down?

Up — reachable from all 18 regions

Average response time: 405ms

Last checked: 14 minutes ago

Official status page: https://www.cloudflarestatus.com

Bot Management Issues

minor identified

We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.

Affected: Amsterdam, Netherlands - (AMS) Ahmedabad, India - (AMD) Access Arica, Chile - (ARI) Asunción, Paraguay - (ASU) Antananarivo, Madagascar - (TNR) Bangkok, Thailand - (BKK) Cape Town, South Africa - (CPT) Belo Horizonte, Brazil - (CNF) Bandar Seri Begawan, Brunei - (BWN) Hagatna, Guam - (GUM) Bogotá, Colombia - (BOG) Dar Es Salaam, Tanzania - (DAR) Brasilia, Brazil - (BSB) Djibouti City, Djibouti - (JIB) Caçador, Brazil - (CFC) Erbil, Iraq - (EBL) Gaborone, Botswana - (GBE) Johannesburg, South Africa - (JNB) Kuwait City, Kuwait - (KWI) Kigali, Rwanda - (KGL) Luanda, Angola - (LAD) Fortaleza, Brazil - (FOR) Mombasa, Kenya - (MBA) Ramallah - (ZDM) Helsinki, Finland - (HEL) Riyadh, Saudi Arabia - (RUH) Nairobi, Kenya - (NBO) Goiânia, Brazil - (GYN) Istanbul, Turkey - (IST) Guatemala City, Guatemala - (GUA) Bot Management Lisbon, Portugal - (LIS) Kinshasa, DR Congo - (FIH) Hyderabad, India - (HYD) Neuquén, Argentina - (NQN) Norfolk, VA, United States - (ORF) San José, Costa Rica - (SJO) Ottawa, Canada - (YOW) Addis Ababa, Ethiopia - (ADD) Lilongwe, Malawi - (LLW) Santa Venera, Malta - (MLA) Skopje, North Macedonia - (SKP) Salt Lake City, UT, United States - (SLC) Malé, Maldives - (MLE) Timbó, Brazil - (NVT) Manila, Philippines - (MNL) Uberlândia, Brazil - (UDI) Vitoria, Brazil - (VIX) Campos dos Goytacazes, Brazil - (CAW) Chapeco, Brazil - (XAP) Sioux Falls, SD, United States - (FSD) St. George's, Grenada - (GND) Phnom Penh, Cambodia - (PNH) Yerevan, Armenia - (EVN) Ljubljana, Slovenia - (LJU) Kochi, India - (COK) Astana, Kazakhstan - (NQZ)

Uptime History

48.33% uptime
2026-04-08T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-09T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-10T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-11T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-12T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-13T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-14T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-15T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-16T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-17T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-18T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-19T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-20T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-21T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-22T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-23T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-24T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-25T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-26T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-27T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-28T00:00:00Z: 0.0% uptime, 1 checks, 1 incidents
2026-04-29T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-30T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-01T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-02T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-03T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-04T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-05T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-06T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-05-07T00:00:00Z: 50.0% uptime, 1 checks, 1 incidents
2026-04-08T00:00:00Z Today

Network Reachability — 18 Global Regions

ams
274ms
DNS 13ms TCP 8ms TLS 13ms TTFB 238ms
arn
182ms
DNS 9ms TCP 1ms TLS 6ms TTFB 172ms
bom
494ms
DNS 15ms TCP 2ms TLS 11ms TTFB 466ms
cdg
941ms
DNS 448ms TCP 1ms TLS 6ms TTFB 932ms
dfw
330ms
DNS 10ms TCP 2ms TLS 6ms TTFB 318ms
ewr
267ms
DNS 8ms TCP 2ms TLS 6ms TTFB 248ms
fra
206ms
DNS 7ms TCP 1ms TLS 5ms TTFB 197ms
gru
344ms
DNS 7ms TCP 1ms TLS 5ms TTFB 331ms
iad
383ms
DNS 17ms TCP 8ms TLS 26ms TTFB 337ms
jnb
690ms
DNS 5ms TCP 0ms TLS 5ms TTFB 683ms
lax
474ms
DNS 26ms TCP 1ms TLS 6ms TTFB 459ms
lhr
267ms
DNS 11ms TCP 1ms TLS 5ms TTFB 256ms
nrt
448ms
DNS 5ms TCP 0ms TLS 5ms TTFB 439ms
ord
267ms
DNS 16ms TCP 1ms TLS 6ms TTFB 255ms
sin
571ms
DNS 13ms TCP 1ms TLS 7ms TTFB 556ms
sjc
285ms
DNS 6ms TCP 1ms TLS 5ms TTFB 277ms
syd
463ms
DNS 16ms TCP 0ms TLS 5ms TTFB 441ms
yyz
419ms
DNS 21ms TCP 8ms TLS 8ms TTFB 222ms

Related Services

AWS
AWS
Netlify
Netlify
Vercel
Vercel
Fly.io
Fly.io

FAQ

Why do I see Cloudflare error pages on sites I don't own?
Many websites use Cloudflare as their CDN and security layer. When Cloudflare has issues, the error pages it generates appear on all websites using its network. The website owner may not even be aware of the issue since it's happening at the CDN layer, not on their servers.
Does a Cloudflare outage affect 1.1.1.1 DNS?
Cloudflare's DNS resolver (1.1.1.1) runs on separate infrastructure from their CDN and security services. However, in major incidents, both systems can be affected. If 1.1.1.1 is down, switch your device's DNS to 8.8.8.8 or 9.9.9.9 as a temporary fix.
Can Cloudflare's outage take down the entire internet?
While Cloudflare handles a massive share of web traffic, it cannot take down the entire internet. During major Cloudflare outages, sites not using Cloudflare continue to work normally. However, the impact can feel widespread because millions of popular sites rely on Cloudflare's network.
What do Cloudflare error codes mean?
Error 502 means Cloudflare couldn't reach the origin server. Error 520 means the origin returned an unexpected response. Error 522 means the connection timed out. Error 524 means the origin responded too slowly. During Cloudflare outages, these errors appear even when origin servers are functioning normally.
How can I check if a site is down because of Cloudflare?
Look at the error page for the Cloudflare logo or ray ID. You can also check if the site's DNS points to Cloudflare IPs using a tool like dig or nslookup. If the error page shows Cloudflare branding and www.cloudflarestatus.com reports an incident, Cloudflare is likely the cause.

Get Alerted When Cloudflare Goes Down

FlareWarden checks services every 30 seconds from 18 global regions. Know the moment something breaks.

Start Free Monitoring
Free plan available No credit card required