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
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.
What Cloudflare's status page says
Checking www.cloudflarestatus.com…
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.
Share of 65 recent reports that said what was wrong, from every country listed below.
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
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 11 | 346 |
| Indonesia | Normal | 3 | 28 |
| India | Normal | 3 | 26 |
| Malaysia | Normal | 2 | 6 |
| Brazil | Normal | 1 | 198 |
| France | Normal | 1 | 46 |
| Morocco | Normal | 1 | 7 |
| New Zealand | Normal | 1 | 1 |
| The UK | Normal | 0 | 96 |
| Poland | Normal | 0 | 35 |
| Germany | Normal | 0 | 31 |
| The Netherlands | Normal | 0 | 28 |
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.
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:01Lasted 30 min38peak reports
-
Elevated reports
Thu 29 Oct, 19:01–19:45Lasted 43 min22peak reports
-
Outage
Thu 29 Oct, 15:55–17:49Lasted 1 h 55 min63peak reports
-
Elevated reports
Thu 29 Oct, 03:09–03:29Lasted 20 min13peak reports
-
Elevated reports
Wed 28 Oct, 22:43–23:02Lasted 18 min13peak reports
-
Elevated reports
Wed 28 Oct, 18:54–19:19Lasted 26 min21peak reports
-
Elevated reports
Wed 28 Oct, 16:47–17:08Lasted 21 min24peak reports
-
Outage
Wed 28 Oct, 12:03–16:25Lasted 4 h 22 min76peak 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
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.
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.
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.
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.
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.
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.
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.
ping cloudflare.comTest whether Cloudflare's servers replynslookup cloudflare.comCheck that Cloudflare's DNS resolvestracert cloudflare.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadCloudflare 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.
ping -c 4 cloudflare.comTest whether Cloudflare's servers replynslookup cloudflare.comCheck that Cloudflare's DNS resolvestraceroute cloudflare.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadCloudflare 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.
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.
Most often at the same time
- ESPN Fantasy Football12 times
- ADP10 times
- USPS10 times
- OpenAI9 times
- Archive of Our Own8 times
- TalkTalk8 times
How many of Cloudflare's spikes overlapped one of theirs.
During the latest spike
Cloudflare: Thu 29 Oct, 20:31 to 21:01
- ESPN Fantasy Football, outage,27 Oct 19:50 to 30 Oct 05:40
- Archive of Our Own, outage,07:55 to 31 Oct 21:18
- ADP, outage,14:43 to 22:13
- StormFiber, outage,15:33 to 21:18
- Microsoft Outlook, outage,16:39 to 22:05
- Microsoft 365, outage,17:23 to 22:07
- Proofpoint, outage,17:23 to 21:52
- GOV.UK, outage,18:30 to 21:24
37 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
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.
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.
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.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 70 ms | 104.16.123.96 |
| ViennaAustria | Up | 102 ms | 104.16.124.96 |
| MilanItaly | Up | 51 ms | 104.16.124.96 |
| ParisFrance | Up | 77 ms | 104.16.123.96 |
| AmsterdamNetherlands | Up | 62 ms | 104.16.123.96 |
| MadridSpain | Up | 93 ms | 104.16.123.96 |
| WarsawPoland | Up | 129 ms | 104.16.123.96 |
| Los AngelesUSA | Up | 185 ms | 104.16.124.96 |
| São PauloBrazil | Up | 194 ms | 104.16.123.96 |
| SingaporeSingapore | Up | 6,085 ms | 104.16.124.96 |
| TokyoJapan | Up | 220 ms | 104.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.
Cloudflare FAQ
Is Cloudflare down right now?
Why do I see a Cloudflare error 522 on my site?
Why do I keep seeing a Cloudflare challenge page on my own site?
Why does 1.1.1.1 stop resolving domains on my phone?
Why can't I log in to my Cloudflare account after losing my authenticator?
Service updates from @Cloudflare
No posts about problems from @Cloudflare in the last 14 days. The latest is from .
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.