Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (39%)
• Cloud Services (29%)
• Web Tools (14%)
• Hosting (11%)
• E-mail (7%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Manchester	Domains	19 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	2 months ago
Jewar	E-mail	2 months ago
Braga	Web Tools	2 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Cloudflare Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Diego Artiles (@dartilesm) reported 8 minutes ago

  Cloudflare Workers used to run in front of the cache. Now they can run behind it. Workers Cache: one wrangler.jsonc line. Worker never runs on a cache hit — no CPU charge. Does this change how you'd design a Workers app?

• 
  Dragos (@bitdoze) reported 8 minutes ago

  Hey @BunnyCDN why are you not providing a service similar to cloudflare pages? You have all the infrastructure, CDN. Only thing missing is the app.

• 
  God’s baby (@Godsbaby2025) reported 11 minutes ago

  Anthropic’s Claude bot crawls ~2,800 web pages for every 1 visit it sends back to the site, according to Cloudflare data (July 1-7). That’s the worst ratio among major AI companies. It’s actually improved a lot — was ~8,800:1 in early April, and spiked to a wild 24,700:1 in the first week of May. Anthropic pushed back, saying it can’t verify Cloudflare’s math and that its new search feature is driving more referral traffic to sites.

• 
  Quis ut Deus? (@HierB4TheAC) reported 11 minutes ago

  @Dimi7ri @realsedepicante A pen name on the internet is irrelevant. Even if you use a VPN youre not anonymous. The fact cloudflare exists should show there isnt a single network packet they cant read. They know everything everyone does on the internet.

• 
  Tom Rush (@tr4777) reported 12 minutes ago

  I’m activating KER-453 as the sole security child and using the OFF issue workflow to carry it through current-truth preflight, minimal remediation, adversarial review, one PR into staging, automatic staging deployment, bounded test-identity proof with cleanup, and Linear closeout. Before editing I’ll identify the exact profile-contract, persistence, authorization-consumer, OpenAPI, and regression-test files; production, provider, credential, Cloudflare/Render configuration, and unrelated auth semantics remain outside scope. /codex

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 19 minutes ago

  The fix: → Blocked the IP range in .htaccess and CSF firewall → Added rate limiting via mod_ratelimit: 100 requests/minute per IP → Enabled Cloudflare Bot Fight Mode (free on all Cloudflare plans) → Added robots.txt rules to block known commercial scrapers → Enabled Cloudflare's "I'm Under Attack" mode for 24 hours Bot traffic: dropped to near zero within 4 hours. Bandwidth: back to normal the next week.

• 
  Manfred Neustifter (@supermanfredX) reported 20 minutes ago

  @Cloudflare The worktree name (which is the issue name)

• 
  Johnny Doomslayer (@VolkNewsDotC0m) reported 20 minutes ago

  @ric_rac Rumble has the potential, but it is not going to succeed if you don't fix the basic issues that persist. For one, I've not been able to verify my phone for months. Tried getting help, and there is no response after the initial contact! Your cloudflare presents a loop that prevents people from signing in. Moderation tools for trolls is non existent making your platform allow horrendous people ruin the experience. Lastly, I am a creator on Rumble. I pay you a fee to be able to. However, I do not watch anything on Rumble because it barely works when watching. Maybe it is just me because I get viewers who don't complain, but the live streams are difficult to watch. Video play is fine.

• 
  komm64 (@komm64) reported 23 minutes ago

  @Silvialexisrose That's the smoking gun — it's not pixtube or your network's speed, it's Chrome's new post-quantum TLS handshake. Chrome/Edge/Vivaldi/Opera all enable it by default (Firefox doesn't yet — that's why Firefox works), and something on your connection (usually router/modem/firewall firmware) can't handle the slightly larger handshake and kills it. Your phone works because it takes a different path. Quick fix in your Chromium browsers: 1. Go to chrome://flags (or edge://flags, vivaldi://flags, etc.) 2. Search "post-quantum" (also try "kyber" or "ML-KEM") 3. Set the matching flag to Disabled, restart the browser. That should make them all work. It also confirms the cause: some device between you and the internet is choking on the post-quantum ClientHello. Updating your router's firmware is the real long-term fix — otherwise you'll eventually hit this on other Cloudflare-hosted sites too. Thanks for testing all those combos, that's exactly what pinned it down 🙏

• 
  Binary Sniper ⚡ (@MrBinarySniper) reported 26 minutes ago

  @zeddotdev @huggingface Neee cloudflare gateway support

• 
  AI will replace lawyers by 2031 🦊 (@ohfarfoxache) reported 29 minutes ago

  @FSUofAustralia @celinevmachine_ I never received any notification of them reaching out to Cloudflare trying to get my site pulled. I only found out in court when I subpoenaed them for documents.

• 
  Hyper (@HyperbooleanHB) reported 30 minutes ago

  @cremieuxrecueil I hate having to click a cloudflare box to visit a site. Something has to be done to maintain usability. Overuse of JavaScript was bad enough

• 
  Hajime Hoshi (@hajimehoshi) reported 35 minutes ago

  @Piechutowski * GitHub Pages requires GitHub Actions YAML, which is difficult to test on local machines * GitHub Actions is sometimes down * Cloudflare Pages' loading speed is way much faster * Cloudflare Pages supports redirections

• 
  Shinjae Kang (@zemnanet) reported 36 minutes ago

  Workers Cache changes the deploy check: a cache hit means your Worker never runs and CPU time stays at zero. So the proof is not just “URL works” — verify headers, tags, purge path, and the first miss. Which one do you test first? #cloudflare

• 
  Frank “Dot Matrix” Lee💎 (@fullfrankchan) reported 37 minutes ago

  @biilmann And you're juuuuuust stingy enough with the free credits that if you have to iterate more than you thought you end up buying a plan. Upside is, it's so dang good that you don't really care. Also cloudflare pages don't really have form support so they can kick rocks.

• 
  Wayne Shirreffs (@WayneShirreffs) reported 38 minutes ago

  @pau11960 @pranavsf @Cloudflare Stablecoins don’t move 3% a day wtf are you even talking about? Stablecoins are stable dollar equivalents. Same as excepting dollars except don’t have to grease the middle man 3% of every transaction.

• 
  amelia!! (@aamelting) reported 41 minutes ago

  @luffymindset2 content delivery network.. although its not a real one its piggybacking on cloudflare free tier cache.. basically google drive with fewer features that i made for liek personal use nd sharing files with friends that were too big to send

• 
  Randy.base.eth (@follobackinstan) reported 41 minutes ago

  Everyone is arguing about which model wins. I think that is the wrong scoreboard. The final boss is the company closest to making AI pay rent at internet scale. My pick is Cloudflare. Not because it owns the web. It does not. Because it sits in front of enough of it to change the cost of access. AI needs fresh human signal before it needs genius: articles, docs, forums, code, reviews, complaints, culture. The old bargain was bad but understandable. Bots crawled, publishers got traffic, creators hoped someone clicked. AI broke the click. Now the answer can appear without the visit. So what used to look like discovery starts to look like extraction. Cloudflare's first weapon is consent. AI Crawl Control makes crawlers visible and controllable. Pay Per Crawl tests the next step: allow, block, or charge. The second weapon is coordination. One site blocking bots is a protest. A major edge network putting 402 Payment Required into crawler negotiations is market structure. That is why @RallyOnChain belongs in this fight. Cloudflare pressures extraction at the infrastructure layer. Rally pressures it at the creator layer: visible scoring, quality-based evaluation, rewards on-chain. The next internet will not be decided only by who writes the best answer. It will be decided by who controls the input. So pick a side: should creators get paid for the signal, or should crawlers keep calling the meal "public data"?

• 
  Samian (@ApplyWiseAi) reported 45 minutes ago

  @QuinnyPig @Cloudflare the "ask the customer what they want" trap is such a cop out. cloudflare just ships a sensible default and moves on. that's the whole difference.

• 
  James Lincoln (@_jameslincoln) reported 49 minutes ago

  We just closed Q2, and we missed our goal. Here's how the numbers turned out. Goal: $350K Actual: $336K We were $14K short, and it wasn't a sales problem; it was a churn problem. -$12K in churn in Q2 vs $6.8K in Q1. Nearly doubled. - That amounted to ~$15K in actual revenue lost. - If we'd kept those customers, we'd have finished at $351K and hit the goal. On the other hand, we made real progress everywhere else. - SDR leads: 222 to 451 - Email leads: 94 to 157 - Team training: 228 hours across the quarter - First sites migrated off Duda onto Cloudflare (i’ve mentioned this transition on the last founders journal)

• 
  Aarón (@AaronCornellius) reported 49 minutes ago

  @mddanishyusuf @Cloudflare @Namecheap I use namecheap and have had some issues. Probably going to do this too and move to Cloudflare

• 
  Konstantin Mikheev (@sirstripy) reported 49 minutes ago

  @anakin @Cloudflare It's taken by a DNS service

• 
  Vijay Tupakula (@vijaytupakula) reported 52 minutes ago

  @HotAisle @Cloudflare Oh no! I haven’t used their email service yet. @Cloudflare can you help?

• 
  Sean Knox (@Opp_Knox) reported 53 minutes ago

  @wholemars @levelsio @Cloudflare What is bad about it sendgrid?

• 
  Nas (@Nas_tech_AI) reported 56 minutes ago

  You can’t believe this: you spent more on coffee this month than on a startup’s infrastructure. If you’re still waiting for the “right moment” to build, this is it. The cost of entry has never been lower. - Claude = coding ($20/mo) - Supabase = backend (free) - Vercel = deploying (free) - Namecheap = domain ($12/yr) - Stripe = payments (2.9%/transaction) - GitHub = version control (free) - Resend = emails (free) - Clerk = auth (free) - Cloudflare = DNS (free) - PostHog = analytics (free) - Sentry = error tracking (free) - Upstash = Redis (free) - Pinecone = vector DB (free) Total monthly cost to run a startup: ~$21 There has never been a cheaper time to build.

• 
  Clip Arabia (@ClipArabia) reported 56 minutes ago

  BREAKING: Cloudflare is down

• 
  Vikas (@vikaskbh) reported 56 minutes ago

  @riku720720 @whoiskatrin cloudflare support workers for websocket?

• 
  Duryab Aziz (@duryabaziz) reported 59 minutes ago

  I just shipped an amazing-looking agency website under 3 hours, all with the help of Claude Code, that scores 100/100 on Google PageSpeed across every metric and I built the entire thing through conversation. No page builder, no dev team, no 3-week back-and-forth with an agency. A few months ago my website was the thing I kept avoiding. Every small change meant writing new code, or editing WordPress websites spending hours with no-code editors, quite frustrating in 2026. Publishing a new page felt like a project, not a task. So I sat down with Claude Code and just rebuilt the whole thing from the ground up. Not a drag and drop builder, an actual architecture. Here's roughly how it works, in plain terms. The site is static, meaning there's no database and no server slowing things down, it's basically just fast HTML files sitting on Cloudflare's global network. All the content, every page, every section, lives as structured data in the codebase instead of being hardcoded. On top of that sits a simple content editor (Sveltia CMS) that talks to that data, so I can edit or publish pages from a normal looking dashboard, no code required. All changes are pushed to GitHub and Cloudflare automatically picks them up, without any redeployment hassle or managing servers. The part that changed everything for me is how pages are built. Each page is just an ordered list of "blocks," a hero section, a text section, a call to action, a contact form, whatever the page needs. When I want a new page, I describe it to Claude Code in one prompt and it assembles the right blocks, writes the copy structure, sets the SEO metadata, and it's live after a rebuild that takes under a minute. That's also why the SEO is properly built in rather than bolted on. Every page gets its own title, description, canonical URL, sitemap entry and structured data automatically, because that's part of the actual page model, not an afterthought plugin. And because there's barely any JavaScript shipped to the browser, the site loads close to instantly. I ran it through Google PageSpeed and it came back 100 out of 100. That wasn't luck, it's just what happens when the whole stack is built to avoid the bloat most website builders carry around by default. The other thing I didn't expect, I don't need my laptop anymore. Claude Code has cloud agents now, so does ChatGPT, so does Cursor. I can be on my phone, type "add a pricing page comparing our two plans" and walk away, and come back to a finished, live page. Same with small fixes or new features. That still feels a bit unreal to type out. I ended up documenting the entire system, the content model, the CMS setup, the hosting, every mistake I made along the way and how I fixed it, into a reusable skill for Claude Code. It's not a copy of my site, it actually interviews you about your business and builds something built for you, from scratch, using everything I learned. I want to give it away, but only to people who are genuinely going to use it. So here's the deal. Like this post, follow me, and comment "SITE" below. Once I see it, I'll send it straight to your inbox. Let's build something.

• 
  Arpit Bhayani (@arpit_bhayani) reported 60 minutes ago

  Cloudflare has been building Meerkat, their new global consensus service, built on a protocol called QuePaxa instead of the usual Raft or Paxos. To be honest, I did not know about QuePaxa before this. I learned about it from the post itself, and it is genuinely interesting. Most consensus systems, like Raft, rely on timeouts to detect a dead leader and trigger a new election. That works fine until your network latency fluctuates a lot, which is exactly what Cloudflare deals with every day. Too short a timeout, and replicas panic and block writes. Too long, and the system just sits there while something is actually broken. So instead of Raft, Meerkat runs on QuePaxa. Here is how QuePaxa avoids the leader problem. A client does not need to go through a leader at all; it can contact any replica, and that replica can drive consensus for the current slot on its own. A leader still exists in the system, and it has one advantage: if it is the one proposing, it takes just one round trip to reach a decision. A non-leader replica needs three or more round-trip to do the same thing. So the leader speeds things up, but it is not a requirement for progress. If the leader goes down or slows down, any other replica simply picks up the work, and writing keeps flowing. Also, concurrent proposals do not conflict destructively. The replicas coordinate and converge on a single agreed value regardless. Interestingly, Cloudflare is planning to build a full key-value store and a leasing system on top of it. I have started reading up on QuePaxa after this post, and wanted to share what I found first. Hope this helps.

• 
  sol87 (@Sol87_live) reported 1 hour ago

  @JonathanLigmas @Luffydude1 @prestonjbyrne Right now it's as easy as signing up for any web service provider(they can't block AWS, Azure, Cloudflare) copy/paste 1 thing into the terminal, put the file it creates to any device, now you have VPN on any major service provider.