Skip to main content
Cloudflare logo

Is Cloudflare Down?

No — Cloudflare is up

Reachable from all 17 checked regions

Average response time: 166ms

Last checked · checks run every 30 minutes

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

Network Performance Issues in LAX

minor identified

Cloudflare is investigating issues with network performance in LAX. We are working to analyse and mitigate this problem. More updates to follow shortly.

Components the vendor reports as affected: Arica, Chile - (ARI) Major Outage Annaba, Algeria - (AAE) Major Outage Baku, Azerbaijan - (GYD) Degraded Performance Bangalore, India - (BLR) Degraded Performance Canberra, ACT, Australia - (CBR) Major Outage Belo Horizonte, Brazil - (CNF) Degraded Performance Hagatna, Guam - (GUM) Major Outage Erbil, Iraq - (EBL) Degraded Performance Sydney, NSW, Australia - (SYD) Degraded Performance Gaborone, Botswana - (GBE) Degraded Performance Curitiba, Brazil - (CWB) Degraded Performance Audit Logs Degraded Performance Luanda, Angola - (LAD) Degraded Performance Nairobi, Kenya - (NBO) Degraded Performance Fuzhou, China - (FOC) Degraded Performance Istanbul, Turkey - (IST) Degraded Performance Haikou, China - (HAK) Degraded Performance Kyiv, Ukraine - (KBP) Degraded Performance Hengshui, China - (SJW) Degraded Performance Lima, Peru - (LIM) Degraded Performance Kinshasa, DR Congo - (FIH) Major Outage Los Angeles, CA, United States - (LAX) Degraded Performance Windhoek, Namibia - (WDH) Major Outage Jakarta, Indonesia - (CGK) Degraded Performance Panama City, Panama - (PTY) Degraded Performance Mexico City, Mexico - (MEX) Major Outage Jinan, China - (TNA) Degraded Performance Cloudflare One Client Degraded Performance Johor Bahru, Malaysia - (JHB) Major Outage Quito, Ecuador - (UIO) Degraded Performance Kaohsiung City - (KHH) Degraded Performance Recife, Brazil - (REC) Degraded Performance Norfolk, VA, United States - (ORF) Major Outage Palermo, Italy - (PMO) Major Outage Kolkata, India - (CCU) Degraded Performance Santiago, Chile - (SCL) Degraded Performance Kuala Lumpur, Malaysia - (KUL) Degraded Performance São Paulo, Brazil - (GRU) Degraded Performance Lilongwe, Malawi - (LLW) Major Outage Manila, Philippines - (MNL) Degraded Performance Tirana, Albania - (TIA) Degraded Performance Campos dos Goytacazes, Brazil - (CAW) Major Outage Sioux Falls, SD, United States - (FSD) Degraded Performance St. George's, Grenada - (GND) Major Outage Phnom Penh, Cambodia - (PNH) Degraded Performance Singapore, Singapore - (SIN) Degraded Performance Palmas, Brazil - (PMW) Major Outage Salvador, Brazil - (SSA) Degraded Performance Kochi, India - (COK) Degraded Performance WARP Degraded Performance Workers Degraded Performance China Network Degraded Performance Shenzhen, China - (SZX) Major Outage Xiangyang, China - (XFN) Major Outage Baoji, China - (XIY) Degraded Performance Chengdu, China - (CTU) Degraded Performance Anshun, China - (AVA) Major Outage Dushanbe, Tajikistan - (DYU) Major Outage

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Cloudflare fail from enough regions to rule out probe noise.

Cloudflare uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
203ms
Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

43-day clean streak
Sep 14: 100.00% uptime, 857 checks
Sep 15: 100.00% uptime, 911 checks
Sep 16: 100.00% uptime, 854 checks
Sep 17: 100.00% uptime, 922 checks
Sep 18: 100.00% uptime, 897 checks
Sep 19: 100.00% uptime, 864 checks
Sep 20: 100.00% uptime, 864 checks
Sep 21: 100.00% uptime, 864 checks
Sep 22: 100.00% uptime, 910 checks
Sep 23: 100.00% uptime, 889 checks
Sep 24: 100.00% uptime, 862 checks
Sep 25: 100.00% uptime, 880 checks
Sep 26: 100.00% uptime, 911 checks
Sep 27: 100.00% uptime, 862 checks
Sep 28: 100.00% uptime, 864 checks
Sep 29: 100.00% uptime, 855 checks
Sep 30: 100.00% uptime, 850 checks
Oct 1: 100.00% uptime, 815 checks
Oct 2: 100.00% uptime, 815 checks
Oct 3: 100.00% uptime, 814 checks
Oct 4: 100.00% uptime, 816 checks
Oct 5: 100.00% uptime, 816 checks, 1 incident
Oct 6: 100.00% uptime, 816 checks, 1 incident
Oct 7: 100.00% uptime, 816 checks, 1 incident
Oct 8: 100.00% uptime, 815 checks, 1 incident
Oct 9: 100.00% uptime, 816 checks, 1 incident
Oct 10: 100.00% uptime, 816 checks, 1 incident
Oct 11: 100.00% uptime, 815 checks, 1 incident
Oct 12: 100.00% uptime, 815 checks, 1 incident
Oct 13: 100.00% uptime, 765 checks, 1 incident
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
81ms
DNS 16ms TCP 2ms TLS 6ms TTFB 66ms
arn
57ms
DNS 11ms TCP 1ms TLS 5ms TTFB 45ms
cdg
76ms
DNS 12ms TCP 2ms TLS 7ms TTFB 57ms
dfw
179ms
DNS 6ms TCP 1ms TLS 4ms TTFB 162ms
ewr
145ms
DNS 9ms TCP 2ms TLS 9ms TTFB 119ms
fra
84ms
DNS 16ms TCP 1ms TLS 8ms TTFB 70ms
gru
242ms
DNS 10ms TCP 2ms TLS 8ms TTFB 226ms
iad
100ms
DNS 13ms TCP 2ms TLS 7ms TTFB 74ms
jnb
318ms
DNS 16ms TCP 0ms TLS 5ms TTFB 301ms
lax
203ms
DNS 13ms TCP 2ms TLS 8ms TTFB 177ms
lhr
102ms
DNS 19ms TCP 2ms TLS 8ms TTFB 74ms
nrt
231ms
DNS 7ms TCP 1ms TLS 7ms TTFB 209ms
ord
138ms
DNS 10ms TCP 1ms TLS 5ms TTFB 116ms
sin
291ms
DNS 7ms TCP 1ms TLS 5ms TTFB 278ms
sjc
173ms
DNS 22ms TCP 1ms TLS 6ms TTFB 153ms
syd
280ms
DNS 8ms TCP 1ms TLS 6ms TTFB 271ms
yyz
122ms
DNS 7ms TCP 1ms TLS 7ms TTFB 100ms

What Cloudflare does

Cloudflare is a global network that provides CDN, DDoS protection, DNS, and security services to millions of websites. It acts as a reverse proxy between visitors and websites, caching content and filtering malicious traffic. Cloudflare handles a significant percentage of global internet traffic and provides the 1.1.1.1 public DNS resolver.

What an outage looks like

Cloudflare outages typically cause websites to display "Error 502", "Error 520", or "Error 522" pages with the Cloudflare logo. DNS resolution may fail for domains using Cloudflare's nameservers, and websites behind Cloudflare may become completely unreachable even if the origin server is healthy.

What to do about it

Check www.cloudflarestatus.com for current incidents. If you manage a site behind Cloudflare, you can temporarily switch DNS to point directly to your origin server as a workaround. For 1.1.1.1 DNS issues, switch to an alternative resolver like 8.8.8.8 (Google) or 9.9.9.9 (Quad9) temporarily.

Is it down for everyone, or just you?

If this page says Cloudflare is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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

How we measure this

  • We request Cloudflare's public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 17 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Cloudflare publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Cloudflare goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required