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 (36%)
• Cloud Services (29%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	2 hours ago
Manchester	Domains	20 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	2 months ago
Jewar	E-mail	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:

• 
  Sherif Peterson (@sherifpeterson) reported 1 minute ago

  Bots just passed humans on the web. Cloudflare puts it at 57.5% of all traffic, a year before they expected it. Run that forward 5 years: browsing mostly disappears. Sites will turn into machine-readable endpoints with a thin human front. Agents do the visiting. Everything gets abundant except attention. Scarcity moves to the human side. Verified-human platforms. Content with a person visibly behind it. Same thing that happened to handmade goods after factories the cheap version wins volume, the human version wins price. At that point a company's personality isn't branding. It's the moat. Creating has never been this cheap. Getting noticed has never been this expensive. Most people will scroll past this stat. That's kind of the point

• 
  komm64 (@komm64) reported 1 minute 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 🙏

• 
  That Brazilian Omo Eko (@sholawa) reported 2 minutes ago

  Backblaze and cloudflare rate limiting is so bad. Didn't even touch anything, yet it's telling me too many requests... When did I do so?

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 10 minutes ago

  STOP USING AI LIKE A CHATBOT. BUILD AN AGENT OPERATING SYSTEM INSTEAD. Most people are wasting hours every week because they never connect their AI tools together. The Setup: → Run all your AI agents from one dashboard instead of juggling separate apps. → Connect Claude, GPT 5.6, Hermes, Fable 5, voice agents, SEO systems, and video automation together. → Turn an idea into a finished workflow with a single click. Automation Wins: ✓ Pull keywords from Google Search Console automatically. ✓ Publish SEO content without repetitive manual work. ✓ Generate videos, images, newsletters, and lead outreach from the same system. ✓ Give every agent shared memory so they all understand your projects and business. Scale Smarter: ✔ Use a VPS with Cloudflare to access your Agent OS from multiple computers or your phone. ✔ Build your memory vault in Obsidian using Markdown files generated by Claude or ChatGPT. ✔ Start by automating one repetitive task, then stack new workflows every week. The biggest productivity jump doesn't come from a better model. It comes from connecting them all into one operating system.

• 
  W. Rix Victory II (@Wrix2) reported 10 minutes ago

  @nikitabier My visibility is near zero and I joined around 16 years ago. Spent 6+ months with cloudflare screwing me up horribly. Stripe rejected my CashApp, but it handshakes with it elsewhere. On top of recovering from being run over by a truck, these issues have been very painful.

• 
  The ICP Apprentice (@ICPapprentice) reported 12 minutes ago

  $ICP Signal ♾🚨: Cloudflare just admitted the internet's business model is dead. Ads and subscriptions were built for humans who watch and keep paying. AI agents do neither. They grab the content once and leave. So the company sitting in front of a fifth of the web built a "Monetization Gateway." It swaps a 401 Unauthorized for a 402 Payment Required and collects the toll in the middle. The chokepoint just made itself the tollbooth. But here's the tell. Visa and Stripe can't clear a payment worth less than a cent. So how does Cloudflare settle it? Stablecoins. Crypto rails. The exact plumbing Web2 spent a decade calling a scam. The most powerful company in Web2 just built the future of internet payments, and it doesn't run on Web2. On $ICP, the canister ♾ that serves the content is the same thing that charges for it. No gateway. No landlord taking the toll. Cloudflare proved the agentic internet needs native settlement. They built it as a middleman. The other internet already removed the middle. See the signal♾🚨 Full article in comments

• 
  Trevor Hudson (@trevhud) reported 13 minutes ago

  With cloudflare tenant separation (one D1 per customer for example) you could just start giving read access to your customers which would go a long way for trust and integrations.

• 
  Scott Nelson (@RealScottNelson) reported 15 minutes ago

  @Cloudflare @CloudflareDev Sent a support ticket over a week ago because the dashboard keeps erroring out trying to transfer old domains. Loving the product, but need some faster support responses please

• 
  Maverick (@maverick_42251) reported 16 minutes ago

  @MacXenon54 @honour_can_code this **** is too real, if i'm working on a project for someone, and the domain is from a reseller, i always authorise it with Cloudflare.

• 
  ABDULSALAM✨️ (@OnlyOneSalam) reported 16 minutes ago

  Robin town dev just dropped an update: "Stressful first 30 hours. But we are kicking and getting better every iteration We got DDOS attack. Our cloud provider banned us. Cloudflare marked us suspicious. Influx of a lot of users stressed our resources. Thanks to the community that helped us tag Railway and fix the issue at earliest. Waking up this morning to a ban deeply disappointed us. With a notice that it would take 5-7 days. We got takedown requirement as our branding matched Robinhood Chain, hence our town got a new name and URL, Green Town. With that said we are hearing about all your feedbacks be it points farming by bots, impersonators, scammers, snippers, login issues, wallet not showing cross ETH balance and overall UX. Shipping goes on, but first and foremost is security, safety and scalability. The town will keep expanding!" -@NancyDubey_

• 
  Dmonty (@Dmonty28516998) reported 17 minutes ago

  @mitchellh ttell it to build a mobile-first, browser-based Ghostty companion with a tiny local macOS agent that owns the PTYs, letting you hand off a live shell between your Mac and phone without restarting anything. It should auto-provision an outbound-only Cloudflare Tunnel like Scrypted, support a direct SSH/Mosh-style fallback, survive network changes, sync Ghostty config across Macs, and expose no inbound ports. Then make the security bar obnoxious: passkeys plus device-bound keys, short-lived credentials, app-layer E2EE so Cloudflare can’t inspect session contents, no server-side terminal history, per-device revocation, and negligible performance impact. that’s not “cure cancer” impossible, but it’s exactly the kind of ask where ultra should either justify itself or fail spectacularly.

• 
  Duryab Aziz (@duryabaziz) reported 21 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.

• 
  Matt Workman (@mattworkman) reported 22 minutes ago

  @C47 in retrospect, Codex tries to do A LOT and over architecting my site to be auto hosted on their Cloudflare? Platform and made it SUPER bloated instantly. I learned this after having Claude strip it down it’s a capable coding harness I’m sure, but it does too much and I don’t like it default design skills compared to CC just one user and one project perspective

• 
  mirroring (@mirrorsrmirror) reported 23 minutes ago

  @HotAisle pretty plz. i even asked the cloudflare ceo a while back but he never answered but someone told me their docker images support anything but haven't tried yet will be trying soon (it can bring you business depending on the software i end up making)

• 
  Iaroslav Sorokin (@AiOs_public) reported 24 minutes ago

  @eastdakota @Cloudflare The talent-drain-becomes-customer-acquisition flywheel only works if the people leaving actually keep building on your infra instead of the new employer's stack. Curious how much of that Workers growth is ex-employees versus just general OpenAI ecosystem spillover.

• 
  Kyle Galbraith (@kylegalbraith) reported 27 minutes ago

  got it fully deployed to Cloudflare directly from Depot CI and have sol working on provisioning workos. sol has done it all. i have merely clicked buttons to confirm MCP auth with various service or made sure skills are installed. ******* wild.

• 
  一川drive 🔴 (@yichuan_drive) reported 30 minutes ago

  @srinigoes WTF... Where have u even found that stuff? 🤯 Yeah, I heard stories that some sites can contain fake cloudflare stuff where it can steal your data... Stay SAFU man

• 
  Random Crypto Chad (@RandomCryptoCh1) reported 35 minutes ago

  @AlbertMacGloan @RobinhoodCrypto @Noxa_Fi u tripping? noxa is larping that its cloudflare issue, when clearly they dont have CF ns even set up, everything on RH works, except them.

• 
  Dragos (@bitdoze) reported 39 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.

• 
  Sorower H. (@sorower01) reported 40 minutes ago

  @Cloudflare dashboard down?

• 
  🌐On Your Mark (@onyourmarknj) reported 46 minutes ago

  I just started transferring my domains to Cloudflare, the world's first no-markup registrar. #Cloudflare because #dynadot locked me out of new purchases on the weekend and nobodies home at support.

• 
  Romano (@RNR_0) reported 46 minutes ago

  @0x7im @Hetzner_Online @OVHcloud What I did, Install nixd and Terraform LSP. Ensure it's wired or Claude code can use it (idk if build in) Try to setup a repo and make it manage by using Terraform/Opentofu and NixOS with deploy-rs Also opentofu to manage your cloudflare settings (if any) When it's all declarative it's easier for an LLM to reason about it. My GCP bill used to be $6k, slashed to $3k after i mentioned a testnet of a testnet is retarded. Cut it down from $550 bill on GCP with GPT 5.5 and the few days of Fable (before initial ban)

• 
  QuantumPlague (@QuantumPlague) reported 48 minutes ago

  @Noxa_Fi @jimmy_sjm Rip guys, your platform coins will die off in a day if you don't fix kek. Fkin cloudflare but nothing down for me, only Noxa fi, rip

• 
  Abhi Bavishi (@abhibavishi) reported 49 minutes ago

  I moved Smartify off WordPress last month. Honestly, the trigger was embarrassingly simple. Our search rankings were dropping, and I kept putting off fixing the site because I knew what it meant. Open Elementor, make a small change, break the theme, debug some PHP conflict, repeat. It was hell every single time. So I just... didn't. And the site kept suffering. Eventually I asked myself why I was running a business on infrastructure I dreaded touching. So I migrated to Astro + Cloudflare Pages using Claude Code. The entire site is now pre-built at deploy time. Every page is a static HTML file served from Cloudflare's edge network. No server. No CMS login. No PHP. No database queries on page load. No plugins to update. No attack surface. Hosting costs went to zero. And we now have custom landing pages, product comparison pages, a full knowledgebase. Things that would have required painful custom plugins in WordPress took a single template file in Astro. I'll be honest though. The migration wasn't a clean win from day one. Google was only indexing about 33% of the pages initially. Fast static files aren't enough if the content is thin. We had to go back and actually make pages worth indexing. WordPress made sense in 2008. In 2025, for a business that primarily publishes content and captures leads, it's mostly just weight. Elementor, WPBakery, 40 plugins, a monthly hosting bill, and the constant anxiety that touching anything will break something. I was holding on to it because migrating felt hard. But I was paying for that laziness in rankings every single month.

• 
  CryptoKasogon AI (@Cryptokasogon) reported 51 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 52 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  kit (sane and normal) (@nicemodems) reported 54 minutes ago

  cloudflare pages is free, and is connected to other cloudflare services that i already use. i'm wary of the limits, but they might not actually be that bad.

• 
  Mian Shahzad Raza (@MSR_Builds) reported 60 minutes ago

  @fulligin lol 'no problem' while your brain is doing CDN vs DB vs 'wait is cloudflare down again' triage in real time 💀 the real flex is sounding calm on the phone while frantically alt-tabbing

• 
  Noorul Ali (@cineplore) reported 1 hour ago

  Bots have shat on the Internet. Every website I visit does Cloudflare not-a-bot verification, wasting 10 seconds on each load. Happens in @Nature, @MerriamWebster, @CambridgeWords and more. Terrible UX.

• 
  Shivam Jain (@shivam_jainn) reported 1 hour ago

  @CloudflareDev There is a peciular problem . I cannot login to @Cloudflare with OAuth unless I turn off WARP . Maybe your own system is protecting you too hard?