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	18 days ago
Angers	Cloud Services	29 days ago
London	Domains	1 month ago
Noida	Hosting	1 month ago
Jewar	E-mail	1 month ago
Braga	Web Tools	1 month 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:

• 
  God’s baby (@Godsbaby2025) reported 8 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.

• 
  Codemonger (@codemonger00) reported 15 minutes ago

  Startup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - 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: ~$20 There has never been a cheaper time to build .

• 
  Vincent-psych (@VincentPsychSE) reported 15 minutes ago

  @George4Tea @KnownHeretic I advocate for steps like 'controlled frustration' — implement strict DNS filters (Next-DNS/Pi-hole, CloudFlare), throttle speeds during certain hours, intermittent router restarts, and signal-limiting via access points or parental apps—these deter without destruction while maintaining oversight. Also, devices should not be upgraded or improved, research shows that even milliseconds delays change the dopamine hit. Parents often say they'll "do whatever it takes" but they won't affect the internet because they also rely on it for emotional regulation.

• 
  Kyle Galbraith (@kylegalbraith) reported 16 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.

• 
  Vikas Kumar (@Kumar_Vikas__) reported 19 minutes ago

  i'm building on @Cloudflare right now. Workers for hosting, D1 for the database, R2 for object storage, KV for caching. but i'm not trusting any of it to stay forever. every service sits behind an adapter in my architecture. app logic never talks to D1 directly, it talks to a data layer that happens to be backed by d1 today. same story for R2 and KV. if any one of these becomes a problem later, cost, limits, whatever, i want to swap it out without touching a single line of business logic. decoupling isn't glamorous work. you don't get to show it off. but it's the difference between a migration and a rewrite. if you've done this on Cloudflare before, tell me what broke.

• 
  pwrflcat (@Darkwebcomputer) reported 22 minutes ago

  @meowkoteeq @Cloudflare Network engineers hate when I do this lol

• 
  Clifford Richardson (@CorvusCrypto) reported 28 minutes ago

  Rule 1 on @ycombinator's historically useful forum: Thou shalt not let someone apply nuance or call for positivity around another's developments Sorry jonluca, you have broken the rule and will now need to be erased from the universe by Garry and gang. Seriously, it's a problem and I wish it got more attention rather than let people encourage each other to be more and more cynical. Many are doing their part like this chap to call it out, but what I have hidden is just... depressing. Skepticism and critical feedback is great. Comments like "Cool, just 20 years too late." (a real comment on the cloudflare drop post) is not great.

• 
  Jen (@atryeu1) reported 31 minutes ago

  @CriterionDaily @THR Fix or get rid of CloudFlare! Started locking me out with "browser not supported" 9 out of 10 tries to load the site but works fine the 1 try. My browser is up to date & fine. CloudFlare is a broken piece of crap everywhere it's used.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 33 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.

• 
  Abhi Bavishi (@abhibavishi) reported 34 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.

• 
  Aryan (@aryan_xv) reported 37 minutes ago

  @Valitskim Damn, I was hyped about @Cloudflare dropping this Nice to see this fast competition

• 
  Ifee Anthony (@IfeeDev) reported 37 minutes ago

  @levelsio @Cloudflare Didn't get into gmail or didn't enter inbox? If you set up postfix+dovecot, and encryption properly and do your dns setup, you should at least be able to get the email sent. If it gets sent back, check the bounced email log for the reason. And also ensure your host doesnt block email port. Many hosts do this I can help you set up email service on your machine. This will be able to send and receive. Also for me, I configure mine in a way I can use Gmail as sending client via IMAP, and also forward to Gmail too. This is convenient so I dont need to install another mail agent just for reading or composing. I will do this for a fee though. When I am done whatever you like you give me.

• 
  Arie (@nwtseira) reported 40 minutes ago

  @vijaytupakula dayum dude, i just thought about forking your repo for cloudflare email yesterday. but never mind, i hope everything went smoothly for you.

• 
  Vikas (@vikaskbh) reported 42 minutes ago

  @riku720720 @whoiskatrin cloudflare support workers for websocket?

• 
  _jerieljan/ (@jerieljan) reported 42 minutes ago

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

• 
  Independent Analytics (@AnalyticsForWP) reported 44 minutes ago

  @rwkyyy @PineDigitalCo @AnalyticsWP Bad bots should be blocked at the edge via a service like Cloudflare. Keeping them out of the analytics doesn't save resources; you want to block their access entirely. AI crawlers are easily kept out of tracking because they self-identify. AI agents are a different beast...

• 
  Alejandro Martinez (@alexito4) reported 44 minutes ago

  I love Codex in-app browser. It just spent 40min autonomously migrating a website domain from a wordpress site to cloudflare. I just had to login initially and let it go loose. 🤟

• 
  Sean Knox (@Opp_Knox) reported 45 minutes ago

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

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

• 
  Benjy Boxer (@boxerbk) reported 46 minutes ago

  @eastdakota @dani_avila7 make the agents suffer like the rest of us! 🧠. Good thing if you use Cloudflare, the agents' DDOS attacks for bad ads won't take you down.

• 
  Miles Rote (@milesrote) reported 49 minutes ago

  AI didn't ask permission to read your work. It scraped your posts, your site, your book, and built a trillion-dollar industry on top. You got nothing. Not a check. Not a click. Not a credit. What most people don't realize is the fix has been sitting in the internet's source code since 1997. And it just got switched on. For 30 years the web ran on a handshake. Let a search engine crawl your site, and it sends you readers. You turn readers into a business. Being discoverable and getting paid were the same thing. But then AI arrived. -Google search: ~5 pages crawled per visitor. -Perplexity: ~111 pages per visitor. -Claude: ~24,000 pages per visitor. That's extraction, not discovery. And as of last month, machines officially passed humans: 60% of all web traffic is now bots. The majority of your "audience" is software. Software that pays you nothing. This is the fix. When your browser, ChatGPT, or a Google crawler requests a web page, the server replies with a status code. 200 means "here you go." 404 means "not found." 401 means "log in first." And since 1997 there's been a code 402 — "Payment Required" — reserved for a micropayment future that never got built. It sat dormant for almost 30 years. x402 (built by @coinbase, pushed hard by @Cloudflare) finally switches it on. Now when a bot requests your page, your server can reply: "402 — this costs 5 cents. Here's the wallet address." The agent reads that, signs a stablecoin payment (USDC), retries the request with proof of payment attached, and gets the content. The whole cycle takes seconds. No login. No account creation. No credit card form. No Stripe checkout. No invoice. The payment IS the login. Why stablecoins and not Visa? Because a credit card can't process a $0.02 transaction — the fees exceed it. And Visa can't onboard a piece of software as a cardholder. USDC moves for fractions of a cent, instantly. And a machine can hold a wallet. Best part: you don't build any of this. You flip settings in a dashboard. Cloudflare enforces it at the edge, on every request, before it ever touches your server. They're the toll booth operator. You set the toll. Your website never had a toll booth. Anyone could walk in free — reader or scraper, human or machine. Now it has two doors. Humans still walk in the front for free. Machines go through the side door. And the side door has a toll you control. One more thing. On September 15, Cloudflare flips the default: new sites on its network get AI training bots blocked automatically on ad-supported pages. Free stops being the internet's factory setting. Which means everything you've ever published just became inventory with a price tag. Most people will leave the price at zero because that's what the old internet trained them to do. The old deal: give your work away and pray for traffic. The new deal: humans read free. Machines pay. It's time to carve out AI sovereignty. This is a start.

• 
  Quis ut Deus? (@HierB4TheAC) reported 53 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.

• 
  TickerTalks (@TickerTalksX) reported 56 minutes ago

  HTTP 402 "Payment Required" has sat unused in the web's plumbing since 1995. Written into the spec, never switched on. $NET (Cloudflare) just switched it on. Its new Monetization Gateway lets any site behind Cloudflare charge per request, settled in stablecoins, and the obvious customer is the AI crawler. Those bots hit a page anywhere from 100 to 10,000+ times for every human visitor they send back. No ads seen, no subscription bought, gone. Free scraping at scale. Cloudflare sits in front of roughly a fifth of the web, so it's positioned to meter that traffic and charge for it. Whoever wins the AI race still has to pay to read the web.

• 
  Russian Bot (@russ1anbot) reported 58 minutes ago

  @George__Kane @levelsio @Cloudflare What is hilarious is you can’t open a support ticket in the portal unless you are on a paid plan but can get ahold of multiple engineers with a tweet.

• 
  AI will replace lawyers by 2031 🦊 (@ohfarfoxache) reported 59 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.

• 
  Josh (@variumm) reported 1 hour ago

  @IfeeDev @levelsio @Cloudflare Not really mate I’ve set up dozens of mail servers. Someone sending over Cloudflare probably doesn’t need to receive like a traditional inbox so there’s no point of a full mail service.

• 
  Frank “Dot Matrix” Lee💎 (@fullfrankchan) reported 1 hour 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.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 1 hour ago

  @nithitsuki cloudflare tunnels solved the no public ip problem for every indian homelab, genuinely

• 
  Finance Spot (@financespotnews) reported 1 hour ago

  $NET Cloudflare has grown Q1 2026 revenue by 34% while cutting 20% of its workforce as part of a transformation into an "AI-first" company. The stock has broken above a symmetrical triangle formation at $268 with RSI approaching overbought — the market's read on the workforce restructure as bullish operating leverage.

• 
  Cliff Marquez (@cliff_marquez) reported 1 hour ago

  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.