1. Home
  2. Services
  3. Cloudflare
Cloudflare cloudflare.com

Is Cloudflare down right now? Live status and outage tracker

No, Cloudflare is up.

No widespread outage detected. 7 user reports in the last hour is within the normal range.

Cloudflare's own status page: www.cloudflarestatus.com

Live Last spike Data refreshes every 5 minutes
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

217 reports in total, counted in 15-minute windows

In the last hour, 7 problem reports came in for Cloudflare, against about 28 at this time on a usual day. Over the last 24 hours there were 217 reports. Worldwide, most recent reports were about DNS (37%) and server connection (35%). The last spike in reports was 48 h ago and lasted 30 min. These are user reports from the US, where most people report Cloudflare problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Indonesia 3 · India 3 · Malaysia 2. By country

In the past 24 hours, 217 user reports came in for Cloudflare. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 9 reports, about 21 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
7
22% on the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
9
9 reports, 21 h ago
Last 24 hours

Cloudflare outages and problems

In the past 24 hours, 217 user reports came in for Cloudflare. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 9 reports, about 21 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Cloudflare stayed at their usual level the whole time.
Official status

What Cloudflare's status page says

This month

Cloudflare in October 2026

Problem reports in October (since 5 October)
1,635

Monthly report for October 2026

What went wrong

What people said was wrong in recent problem reports for Cloudflare worldwide.

  1. DNS37%
  2. Server Connection35%
  3. API11%
  4. Dashboard / Console6%
  5. Security and Identity Mgmt6%
  6. Virtual Machines3%

Share of 65 recent reports that said what was wrong, from every country listed below.

World map

Cloudflare reports around the world

In the last 24 hours, 1,179 problem reports about Cloudflare came in from 60 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 11346
Indonesia Normal 328
India Normal 326
Malaysia Normal 26
Brazil Normal 1198
France Normal 146
Morocco Normal 17
New Zealand Normal 11
The UK Normal 096
Poland Normal 035
Germany Normal 031
The Netherlands Normal 028

Each country's status compares its reports with the usual level there. 60 more countries had 331 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Cloudflare problem spikes, last 30 days

Since 5 October, Cloudflare had 4 outage spikes and 8 periods of elevated reports. The longest lasted 4 h 22 min, on 28 October.

  • Fri 2 Oct: no data
  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: 3 reports
  • Tue 6 Oct: 5 reports
  • Wed 7 Oct: 6 reports
  • Thu 8 Oct: 10 reports
  • Fri 9 Oct: 13 reports
  • Sat 10 Oct: 3 reports
  • Sun 11 Oct: 3 reports
  • Mon 12 Oct: 4 reports
  • Tue 13 Oct: 7 reports
  • Wed 14 Oct: 10 reports
  • Thu 15 Oct: 6 reports
  • Fri 16 Oct: 7 reports
  • Sat 17 Oct: 4 reports
  • Sun 18 Oct: 4 reports
  • Mon 19 Oct: 8 reports
  • Tue 20 Oct: 32 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 1 report
  • Fri 23 Oct: 19 reports
  • Sat 24 Oct: 2 reports
  • Sun 25 Oct: 17 reports
  • Mon 26 Oct: 8 reports
  • Tue 27 Oct: 46 reports (elevated reports that day)
  • Wed 28 Oct: 164 reports (outage spike that day)
  • Thu 29 Oct: 739 reports (outage spike that day)
  • Fri 30 Oct: 345 reports
  • Sat 31 Oct: 169 reports
  • Outage
    Thu 29 Oct, 20:31–21:01
    Lasted 30 min
    38peak reports
  • Elevated reports
    Thu 29 Oct, 19:01–19:45
    Lasted 43 min
    22peak reports
  • Outage
    Thu 29 Oct, 15:55–17:49
    Lasted 1 h 55 min
    63peak reports
  • Elevated reports
    Thu 29 Oct, 03:09–03:29
    Lasted 20 min
    13peak reports
  • Elevated reports
    Wed 28 Oct, 22:43–23:02
    Lasted 18 min
    13peak reports
  • Elevated reports
    Wed 28 Oct, 18:54–19:19
    Lasted 26 min
    21peak reports
  • Elevated reports
    Wed 28 Oct, 16:47–17:08
    Lasted 21 min
    24peak reports
  • Outage
    Wed 28 Oct, 12:03–16:25
    Lasted 4 h 22 min
    76peak reports

4 earlier spikes in this period.

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US1,047
  • Brazil678
  • The UK285
  • Poland111
  • France104
  • Mexico103
  • India97
  • The Netherlands92

Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services

Troubleshooting

How to fix Cloudflare not working

Cloudflare is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach cloudflare.com over your own connection, right now. Nothing is sent to us or stored.

  1. Check Cloudflare status

    Open https://www.cloudflarestatus.com and read the incident list for the product you use. If an active incident is listed, wait for the update instead of changing local settings; if none is listed, move to a local test. This site only counts user problem reports and never probes the service.

  2. Switch off WARP and VPNs

    If the WARP app is connected, open it and toggle the connection off, then load the site again. Do the same for any VPN or proxy on that device; a blocked IP range can make a challenge loop on one device while other devices work.

  3. Clear Cloudflare clearance cookies

    In Chrome on desktop, open Settings > Privacy and security > Delete browsing data. Pick Cookies and other site data and Cached images and files, set Time range to All time, then delete and reload the page. A stale cf_clearance cookie can keep a challenge loop tied to one browser profile.

  4. Flush DNS and try 1.1.1.1

    On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache and sudo killall -HUP mDNSResponder in Terminal, then change the DNS server to 1.1.1.1 in your network settings and retry. If another device on the same network works, treat the fault as local to this device's DNS cache or resolver.

Error messages

Common Cloudflare error messages

What each message means and what to try. The wording can differ a little between app versions.

  • Error 1020 Access denied

    Means
    A firewall rule on the site you asked for blocked your request, usually because your IP address or region is on the owner's list.
    Fix
    Switch networks or wait if you are just visiting, since only the site owner can lift the block. If the site is yours, open the firewall rules and find which one matched the request.
  • Error 1015 You are being rate limited

    Means
    You sent requests faster than the site's rate limit allows, so a short block is in place.
    Fix
    Wait a few minutes and load the page once instead of hitting reload over and over. If you run the site, check your rate limiting rules and any script that fires requests in a loop.
  • Error 522 Connection timed out

    Means
    The origin server behind the site did not answer a connection from the network in time.
    Fix
    Reload once, because short origin hiccups clear on their own. If it keeps happening, look at the origin's load and firewall, and check the official status page for a known incident.

While Cloudflare is down: what to use instead

  • Google Public DNS or Quad9 If your phone or router uses Cloudflare's resolver and sites stop loading by name, switch the DNS setting to one of these until the service recovers.
  • Turn off WARP With the WARP app on, all your traffic runs through Cloudflare, so disconnecting it often brings your normal connection back.
  • DNS-only mode for site owners If your origin server is healthy, setting proxied records to DNS-only sends visitors straight to it, though the dashboard has to load first and your server's IP becomes public.
  • Wayback Machine Visitors can often read an older copy of a static page there.
Your device

Fix Cloudflare on Windows, Mac, Android and iPhone

Cloudflare on Windows

Fix
Fix Cloudflare issues on Windows by restarting the WARP client or flushing your DNS cache. You can also temporarily switch your network adapter's DNS servers back to automatic.
Check
Check if Cloudflare is down on Windows by looking at the WARP client connection status or verifying if you can access websites using a different DNS provider. You can also check the official Cloudflare Status page.
Command Prompt
ping cloudflare.comTest whether Cloudflare's servers reply
nslookup cloudflare.comCheck that Cloudflare's DNS resolves
tracert cloudflare.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Cloudflare on Mac

Fix
Fix Cloudflare on macOS by toggling the WARP client off and on from the menu bar. If you configured Cloudflare manually, reset your DNS settings to default in your macOS Network System Settings.
Check
To check if Cloudflare is down on a Mac, check if the WARP menu bar app fails to connect or if web pages load when you change your DNS. You can also visit the Cloudflare Status website.
Terminal
ping -c 4 cloudflare.comTest whether Cloudflare's servers reply
nslookup cloudflare.comCheck that Cloudflare's DNS resolves
traceroute cloudflare.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Cloudflare on Android

Fix
Fix Cloudflare on Android by clearing the 1.1.1.1 app cache or reinstalling it from the Google Play Store. Alternatively, disable the Cloudflare Private DNS option in your device's connection settings.
Check
Check if Cloudflare is down on Android by opening the 1.1.1.1 app to see if it fails to connect. You can also check if your internet connection restores when turning off Cloudflare Private DNS.

Cloudflare on iPhone and iPad

Fix
Fix Cloudflare on iOS by reinstalling the 1.1.1.1 app from the App Store or toggling the VPN profile in your settings. You can also reset your network settings if the Cloudflare profile is stuck.
Check
Check if Cloudflare is down on iOS by opening the 1.1.1.1 app to see if the connection toggle remains disconnected. You can also check if Safari loads pages normally after disabling the Cloudflare VPN profile.
Same time

Problems at the same time as Cloudflare

Since 5 October, all 12 of Cloudflare's spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Cloudflare problems

The busiest hour for reports about Cloudflare is 20:00 to 21:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 2.7 reports on an average day
  • 01:00 to 02:00: 2.4 reports on an average day
  • 02:00 to 03:00: 1.5 reports on an average day
  • 03:00 to 04:00: 2 reports on an average day
  • 04:00 to 05:00: 1.5 reports on an average day
  • 05:00 to 06:00: 1.3 reports on an average day
  • 06:00 to 07:00: 1.4 reports on an average day
  • 07:00 to 08:00: 1.4 reports on an average day
  • 08:00 to 09:00: 1.1 reports on an average day
  • 09:00 to 10:00: 1.1 reports on an average day
  • 10:00 to 11:00: 1.4 reports on an average day
  • 11:00 to 12:00: 1.6 reports on an average day
  • 12:00 to 13:00: 1.3 reports on an average day
  • 13:00 to 14:00: 2 reports on an average day
  • 14:00 to 15:00: 2.6 reports on an average day
  • 15:00 to 16:00: 3.2 reports on an average day
  • 16:00 to 17:00: 2.1 reports on an average day
  • 17:00 to 18:00: 1.8 reports on an average day
  • 18:00 to 19:00: 3 reports on an average day
  • 19:00 to 20:00: 3.2 reports on an average day
  • 20:00 to 21:00: 4.2 reports on an average day
  • 21:00 to 22:00: 3.6 reports on an average day
  • 22:00 to 23:00: 3.3 reports on an average day
  • 23:00 to 00:00: 2.2 reports on an average day

By day of the week

  • Monday: 6.8 reports on an average Monday
  • Tuesday: 23 reports on an average Tuesday
  • Wednesday: 49 reports on an average Wednesday
  • Thursday: 140 reports on an average Thursday
  • Friday: 96 reports on an average Friday
  • Saturday: 46 reports on an average Saturday
  • Sunday: 7.9 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Cloudflare goes down

Cloudflare runs a content delivery and security network for websites and developers. An outage interrupts page loads, DNS resolution, dashboard access, and edge services.

During an outage, DNS lookups can time out and your site may fail to load for visitors, often with a Cloudflare error page in place of the page you expected. API calls to proxied endpoints may return server errors, and the dashboard can reject sign-ins or fail to show analytics. DNS and proxied web traffic tend to show trouble first because a failed lookup or edge error stops the page before anything else loads. Problems are often partial, with one zone or one region affected while other traffic keeps moving; check the official status page for incident notes.

Servers and network

Cloudflare IP address, servers and network

IPv4 addresses
104.16.123.96
Show all 2
  • 104.16.124.96
IPv6 addresses
2606:4700::6810:7b60
Show all 2
  • 2606:4700::6810:7c60
Network
AS13335 · Cloudflare, Inc., registered in the United States
Served through
Cloudflare · our check was answered by its Frankfurt (FRA) data centre
DNS hosted by
Cloudflare
HTTPS certificate
Issued by Google Trust Services, valid until 5 Dec 2026 (34 days)
HTTP/3
Supported
Our check
Answered in 100 ms

Checked from our server in Frankfurt, Germany, 2 days ago, for www.cloudflare.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from www.cloudflare.com. Fastest from Milan (51 ms), slowest from Singapore (6,085 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp70 ms104.16.123.96
ViennaAustriaUp102 ms104.16.124.96
MilanItalyUp51 ms104.16.124.96
ParisFranceUp77 ms104.16.123.96
AmsterdamNetherlandsUp62 ms104.16.123.96
MadridSpainUp93 ms104.16.123.96
WarsawPolandUp129 ms104.16.123.96
Los AngelesUSAUp185 ms104.16.124.96
São PauloBrazilUp194 ms104.16.123.96
SingaporeSingaporeUp6,085 ms104.16.124.96
TokyoJapanUp220 ms104.16.123.96

Checked with check-host.net from its servers in these cities 4 days ago, for www.cloudflare.com. Time is how long each server took to load the page.

Questions

Cloudflare FAQ

Is Cloudflare down right now?

The status at the top of this page shows whether reports are above their usual level, counted in 15-minute windows over the last 24 hours. Cloudflare's official status page lists its own incident notes. To tell whether the problem is only on your side, try the same site on mobile data and in another browser; if both fail the same way, the fault is probably not your device.

Why do I see a Cloudflare error 522 on my site?

Error 522 means Cloudflare could not open a connection to your origin server before it timed out. Check that the origin is running and that its firewall allows Cloudflare IP ranges. If the site is down for you, pause Cloudflare in the dashboard and test the origin directly.

Why do I keep seeing a Cloudflare challenge page on my own site?

That challenge page comes from a WAF rule or a security level setting on your zone. Try another browser and disable extensions that block scripts. Check firewall events for a challenge or block on your IP, then adjust the rule that caught you.

Why does 1.1.1.1 stop resolving domains on my phone?

1.1.1.1 is Cloudflare's public DNS resolver, and its mobile app can route queries over HTTPS or TLS. If lookups fail, switch to another DNS resolver and check your VPN or router settings. A captive portal or a broken Wi-Fi connection can also make the app look down.

Why can't I log in to my Cloudflare account after losing my authenticator?

If you lost your authenticator, use a saved backup code for the account. Check that your phone's clock is set automatically, because a drifting clock breaks many authenticator codes. If you have no backup code, contact Cloudflare support with proof that you own the account.
On X

Service updates from @Cloudflare

Cloudflare@Cloudflare

An examination of global Internet disruptions observed by Cloudflare Radar during the third quarter of 2026. This review analyzes how power failures, natural disasters, and government shutdowns impacted network connectivity and traffic. https://cfl.re/4zWKUjb

For your site

Put the Cloudflare status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Cloudflare status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/cloudflare/"><img src="https://isitdownrightnow.app/badge/cloudflare.svg" alt="Cloudflare status" height="20"></a>
Markdown, for README files
[![Cloudflare status](https://isitdownrightnow.app/badge/cloudflare.svg)](https://isitdownrightnow.app/services/cloudflare/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Cloudflare

The status on this page comes from user-submitted problem reports for Cloudflare, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Cloudflare, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Cloudflare's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services