1. Home
  2. Companies
  3. Cloudflare
Cloudflare

Cloudflare status: hosting issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

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.

At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

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

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

Live Outage Map

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

CityProblem TypeReport 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:

  • HyperbooleanHB
    Hyper (@HyperbooleanHB) reported

    @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

  • arpit_bhayani
    Arpit Bhayani (@arpit_bhayani) reported

    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.

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

    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.

  • ibotezekiel
    Mr. iBOt🐺🇳🇬 (@ibotezekiel) reported

    @Phils_Cassidy Cloudflare is never free

  • cliff_marquez
    Cliff Marquez (@cliff_marquez) reported

    Quick note between chapters. Not a full kit, just the thing to set up before the next one. You've now handed Claude a few keys: Cloudflare, your storage, your registrar. Where are they actually sitting right now? If the answer is "in a text file somewhere," let's fix that first. Put them in a password manager. I use Bitwarden. Here's exactly how I run it, nothing fancy: Logins. The browser extension fills my passwords everywhere. If you do one thing tonight, get every important login in there. API keys. I save each one as a secure note, named the same way, like cc-mailgun-api, cc-twitter-api. So when Claude needs a key months later, I search, grab it, paste it. They live in the vault, not scattered across random files. One honest note, because I don't want to teach you wrong. Pasting a key to Claude does put it in Claude, and you can absolutely avoid that: keep your keys in a hidden .env file and have Claude read them on demand. Claude itself prefers that, it would rather not hold your secrets. It's the more careful path, and if that's how you want to work, do it. I understand security, and I respect it. Me, I trade a little of it for speed. Opening a file, finding the key, pointing Claude at it, that's friction I don't want fifty times a day. I'd rather keep the key in Bitwarden, click copy, and paste it straight to Claude, and put my guardrails on the API side instead: a spending limit with alerts on the account, an IP whitelist where I can, and a scope so the key can only do one job. Not the most secure setup, and I know it. It's what's worked for me. Pick your own spot on that line. I pay for the Premium tier, $19.80 a year, about twenty bucks. Not required, but here's why I do it: some sites make you use two-factor, and instead of a separate authenticator app, Bitwarden generates those codes for me too. Logins, keys, and my 2FA in one place. (There's a developer-grade "Secrets Manager" where your AI pulls keys automatically. I keep it simple with notes. And Bitwarden isn't the only good one. 1Password and others are solid. Use whatever you'll actually keep locked.) Next chapter is your first key that actually does something: getting email working. And now it'll have a home the moment you make it.

  • vijaytupakula
    Vijay Tupakula (@vijaytupakula) reported

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

  • stabledash
    Stabledash (@stabledash) reported

    AWS and Cloudflare have quietly turned on a new option for any publisher running on their infrastructure: the server can return an x402 payment code instead of a flat 404 when an AI bot hits their content. .@_rishinsharma, Head of AI Growth at @Solana Foundation, breaks down what that unlocks: "Say I have a blog, and it's hosted on AWS Bedrock, and I just write about financial data or something like that. By default, AWS will block bot traffic. So if they detect someone is a bot, they'll just block that traffic. If someone from an LLM is trying to get something I've written about, it'll just return a 404. It can return a 402, I can put in a wallet address, and I can actually get paid and monetize that traffic." His read on why subscriptions already lost this audience: "I think for content publishers, this is gonna be a new way for them to reach an audience, because two, three years ago, I was subscribed to a ton of Substacks, where I was paying for a couple of them too. It felt like a way to get alpha. Now I can't imagine, I don't wanna open my email and go to a Substack, and maybe this is an attention deficit thing, but I can't even read long form content. What's the important part? Skip to that one."

  • DinoMan389961
    Dino-Man (@DinoMan389961) reported

    @Cloudflare I could never change something that is a banger, localhost forever

  • aw_labs
    🧪 AW Labs (@aw_labs) reported

    @Chaos2Cured I found out my issue was cloudflare stopping them (which I could change) or my web hosts corp firewall (which I could not change).

  • rahkyt
    Rahkyt Redux (@rahkyt) reported

    Stopping the bad guys with Cloudflare: 6,563 malicious requests blocked or challenged in the last month #cloudflare

  • AmaningOpoku
    📸Prince Opoku Amaning📸 (@AmaningOpoku) reported

    Cloudflare does not really support nextjs

  • shartdotcloud
    metal gore solid (@shartdotcloud) reported

    i get more out of my 5 dollar cloudflare workers plan than the thousands i have spent on AWS over the years. they are so responsive to customer feedback. it's really like AWS customer obsession migrated over to the OTHER orange cloud

  • PXGray
    Paul Gray (@PXGray) reported

    @Cloudflare Oh do what we did with a DHCP server and make it issues all IPs that resolved to a name of a virus. As viruses (users) kill their host.

  • bazmd
    Faux Mulder (@bazmd) reported

    Browser security was behaving strange, (my account was accessed), I received locked out notification emails, Cloudflare was looping, couldn't reset. Spent the morning resolving a billion issues and it's not even Monday yet.

  • OP13
    billdozer (@OP13) reported

    Using Claude to fix my old wordpress blog theme one prompt at a time I probably should just move this to GitHub pages or self hosting (with Cloudflare Tunnels), but I’ve had this thing for 16 years and old habits die hard

  • Silvialexisrose
    Silvia Rose (@Silvialexisrose) reported

    @komm64 Firefox worked! <3 phone works as well, which I didn't think to try. I don't use any antivirus actually, including window's own setting that chrome flag in my chromium browsers didn't fix it working in them and I have never had this error when accessing cloudflare stuff before

  • CodeWithZeee
    ZEE (@CodeWithZeee) reported

    @boristane @vercel @CloudflareDev I have probably over 300 works and run every Cloudflare project known to man, if you want to stress test this I’d be down

  • MSR_Builds
    Mian Shahzad Raza (@MSR_Builds) reported

    @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

  • Nas_tech_AI
    Nas (@Nas_tech_AI) reported

    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.

  • jerieljan
    _jerieljan/ (@jerieljan) reported

    @stupidtechtakes I'm surprised at the amount of people disagreeing. Naysayers think Cloudflare of all companies, the company that literally fights network abuse and bots all the time and runs a captcha service is unable to protect their own service from it?

  • _jameslincoln
    James Lincoln (@_jameslincoln) reported

    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)

  • mike__adeleye
    Michael Adeleye (@mike__adeleye) reported

    Remember we used to have cloudflare outages that took out internet services? (Back in 2025/2024). It's been so long since we last experienced them. For those that had apps in **** during these events, what was the worst effect they had on your business?

  • LoveNvrButGood
    Function True for Catholic & US and all(private) (@LoveNvrButGood) reported

    Placeholder Postion4 any Cloudflare is not Internet. "They run Colossus besides Position4 many - at not primary function - is the enemy. Internet as a vehicle against the products also - just time then it's problem as it was that motivated creation of America." This function to facilitate that. Revolution center - said in GOD.

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

    @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.

  • NathanFlurry
    Nathan Flurry 🔩 (@NathanFlurry) reported

    @CodeWithZeee every company i've worked at that used cloudflare: they tried to charge us between $3k/mo - $10k/mo based on whatever number their sales team pulled out of thin air at the same time we were having serious reliability issues on them at the time had no choice and ponied up bc we were vendor locekd

  • Okwachjamal
    Jamal Shamir (@Okwachjamal) reported

    @vijaytupakula @Cloudflare You gonna add support for zeptomail

  • ok_im_merging
    opossum in blossom 🏳️‍⚧️ трансгендерная мышь (@ok_im_merging) reported

    @nostalgiacore Cloudflare be like: we should build the entire encryption system on this ****

  • jerieljan
    _jerieljan/ (@jerieljan) reported

    @stupidtechtakes I'm surprised at the amount of people disagreeing. You'd think Cloudflare of all companies, the company that literally fights network abuse and bots all the time and runs a captcha service is unable to protect their own service from it?

  • GlenWilsonIA
    Glen Wilson (@GlenWilsonIA) reported

    @bijucyborg @BraydenWilmoth That doesn't change anything. Rapidly deployment and taking down of websites is what phishing scams thrive on. Nomrally they rely on making local webservers on infected computers. Using stolen identities to use cloudflare would be so much easier and less hassle for scammers.

  • supermanfredX
    Manfred Neustifter (@supermanfredX) reported

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