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 (38%)
• Cloud Services (29%)
• Hosting (15%)
• Web Tools (12%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	7 days ago
Angers	Cloud Services	18 days ago
London	Domains	20 days 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:

• 
  sw1tch.sh (@thinkistillcare) reported 4 minutes ago

  suddenly i start getting captchas on google and cloudflare it has to be my IPTV service on my fire stick right?

• 
  Viktor Lazarov (@viktor_techness) reported 5 minutes ago

  @EddCoates Doesn't Cloudflare anti-bot help? They have a setting specifically for scrapers + robots.txt attachment for a legal notice.

• 
  KarenR (@heykarenrc) reported 5 minutes ago

  When I built d1-studio, I was still early in my transition from UX to development. At first, I just wanted the simplest stack possible. Something lean. Something affordable. Something I could build with fast. Like many new devs, I started with the familiar stack: Next.js. Supabase. Vercel. AI helping me along the way. Supabase was great to get started. I still like it. But as I built more products, I started noticing the small costs and tradeoffs that you only understand after shipping. Storage. Egress. Deployment limits. The usual “newbie learns the hard way” stuff. That pushed me to look for a stack that fit how I wanted to build. Then I found Cloudflare. Workers. Pages. D1. R2. Queues. Generous free tier. Simple deployment. Close to the edge. I slowly moved more of my projects there and never really looked back. But there was one thing that kept slowing me down: Cloudflare D1 local development. D1 is great, but working with the database locally felt too slow. I didn’t want to keep jumping between CLI commands just to inspect tables, edit rows, run SQL, or check data while building. I also didn’t want a tool that required a long setup. My thinking was simple: The database is already in my Cloudflare project. The wrangler.toml is already there. Why can’t a studio just detect it and work? That became the trigger for D1 Studio. A native database studio for Cloudflare D1. No complicated setup. No extra database connection string. No heavy workflow. Just run it inside your project and start working with your D1 database faster. You can inspect tables, edit data, run SQL, and work with local or remote D1 without fighting the CLI every few minutes. It started as a tool I needed for myself. Now it’s getting used by other Cloudflare developers too. This week it hit 311 weekly downloads. Not a huge number in the grand scheme of things, but for me it means a lot. Because this is the first product I built that truly came from my own pain. Not a random idea. Not a trend. Not something I forced. Just a problem I kept hitting until I finally built the tool I wished existed. That’s been the biggest lesson for me as I move from design into development: The best products are often not born from brainstorming. They come from friction. Something feels slower than it should. Something takes too many steps. Something breaks your flow. And eventually you think: “There has to be a better way.” That’s how D1 Studio started. And seeing people use it for their own Cloudflare projects is still one of the best feelings.

• 
  Coyote (@8bit5_0) reported 7 minutes ago

  @benlandautaylor the only tech layoff that can’t be explained by bad financials (either due to post ZIRP overhang or increased AI capex) seems to be Cloudflare. So I guess not for tech really

• 
  63green (@63green) reported 10 minutes ago

  So @Cloudflare works overtime to destroy thei reputation by sending emails despite every notification turned off, and I’m willing to grant their request to never, ever trust this criminal company, and never use them. Any company willing to **** you by email will **** your data.

• 
  Fardeem (@FardeemM) reported 12 minutes ago

  If you're on your way to building a billion dollar company that involves a web app, here are some of my notes on architecting the frontend. if you don't do this, it's probably fine but one day you'll hire someone to fix it but truly that person could be doing some other higher value thing if you make some key optimizations on day 1 you don't even have to learn anything you're gonna tell your agents to do it anyways! okay here it goes: - Make your server code generate a openapi spec which then generates all the relevant client side code. Never do this by hand. Typing backend types instead of generating them should be banned - You need to make a decision on how the client talks to the backend. rest/graphql works in which case please just use tanstack query. other libraries will look similar but tanstack query truly is goated. - if you want linear style sync setups or offline mode, think about this HARD and architect it from day 1. Bolting this on later is so tedious. - People like using plain react router but things have gotten a lot better since then. Try their new framework mode or just even use tanstack router. Use route data loaders. - If you store a lot of state in query params, make that a first class citizen and make sure its type safe. use nuqs or tanstack query. - Most apps just need a single state management situation for server state and thats it. If you have other bespoke needs, i have quite like zustand and xstate/store. - If you have a super interactive app where things come in and out of view, theres a lot of frontend state to maintain, music is playing and what not, lock in and learn xstate. Trust me if you wanna keep ur sanity, you need to model ur frontend as a state machine otherwise you're gonna be deep in useEffect hell - React compiler is here my friends, the days of useMemo and useCallback are gone. Update your priors accordingly - Tailwind is easy and fun but makes it really hard to maintain a large app with consistent styling. You need a "agent-first design system/component library" but maybe this is a rant for another day - Don't be afraid to hack your routing library to fit your needs more closely. A lot of apps have "drawers" to show additional info. You should 100% be able to say "here's a route, make it a drawer" and everything should be handled from there. - Managing loading and error states using isPending and isError is madness. Lean into Suspense and ErrorBoundary. - Figuring out a blessed path for websockets and SSE on day 1 i think will pay dividends in the long term if you're building anything AI related. - If you're building a SPA, don't use next.js. it literally makes no sense. Why would you do this. - Definitely deploy on Cloudflare or vercel. There are other services but trust, there have weird missing features. - Assuming you build something people want, the next job is to build the factory so it can efficiently build the thing. Act accordingly.

• 
  nemmy (@Pandaptable_) reported 13 minutes ago

  @UseCider cloudflare for a page that just connects to a local instance.... truly genius engineering.... holy **** you guys are incompetent fix the cpu usage already it's using more than the official am client with lossless

• 
  Lachlan (@lynx769) reported 15 minutes ago

  @EddCoates Are you using Cloudflare in front of it? It should help.

• 
  kiosa (@thegreatest_sv) reported 18 minutes ago

  THE BIGGEST SCAM IN TECH MIGHT BE HOW MUCH PEOPLE STILL PAY TO HOST SIMPLE WEBSITES. >I just launched one for $0. > have 9 project ideas > each needs a domain (~$15) + hosting (~$10/mo) + SSL > do the math > talk yourself out of 7 of them > later find out domains can be free > register one in 2 minutes, no card > Cloudflare for DNS + SSL, free > Cloudflare Pages for hosting, free > live custom-domain site in 20 minutes > cost: $0 > mfw the only thing stopping me was a bill I never had to pay >full build below

• 
  Michael Ramos (@backnotprop) reported 20 minutes ago

  Every "ADE" is going to be pushed into one of either of (some might try to do all): - Linear competitor - Notion competitor - diffxyz/Ai-review competitor and away from "a harness for harnesses" - and/or misstep into remote execution (this requires all in customer bets. Like you either all go all in into the linear model or you do not - I can't imagine this scaling). But there's a much stronger durable layer nobody's really hitting at other than the infrastructure providers - context/artifacts has a lot of exciting potential. You can see it with cursor origin, cloudflare artifacts, code[dot]storage are pointing at. A lot of innovation to be had here & on top of - beyond "hey, share your HTML with me" There's still room for middle layer execution innovation, and it might smell like memory, but nobody's doing memory right.

• 
  Nicholas Preston (@Mike_Preston17) reported 22 minutes ago

  @PLOwingPots @DevLeaderCa You really should learn C and C++ to understand the fundamentals, etc. I say this as a C# dev who went C -> C++ -> Java -> C#. You won't appreciate the 'better' language nearly as much if you don't at least suffer from the shortcomings of its successor language. I suffered pointer and stack overflows from C++ and that taught me to not be an idiot with my memory. Rust babies devs too much, imo - that's what (again, imo) led to the Cloudflare outage: too much trust in the compiler and willfully ignoring the dynamic nature of data in production (which NO language can account for).

• 
  Maaz Perwez (@MaazMz) reported 24 minutes ago

  @Aurarri How is it easier to install another app and then turn it on rather than doing it inside the app for which I want to use proxy? Plus cloudflare will control all of my network while telegram proxy only changes telegram...

• 
  ./can (@shcansh) reported 25 minutes ago

  Adding validity checks for Azure and Salesforce tokens is the real win in the latest secret scanning updates. Instead of chasing ghosts, devs can now see if a leaked credential is still active. But with 11 GitLab token types added and new blocks for Cloudflare, we are putting a lot of trust in automated regex. Are active validity checks actually enough to stop the leak crisis, or are we just treating the symptoms of a broken secret-management culture?

• 
  CAPED CRUSADER🦇 (@stilleclectic) reported 27 minutes ago

  @matthansbello Sigh, everything was originally done on namecheap but I’ve now just moved the dns to cloudflare. Waiting to see if that fixes the issue

• 
  simulx4 (@simulx4) reported 28 minutes ago

  cloudflare is using Kimi K2.6 to automatically resolve billing issues. and... it worked fine. it fixed my problem faster than any human. by chat/email... so much better than talking to a person, honestly

• 
  Bernardo Gonzalez (@bgonzalesp) reported 31 minutes ago

  @CloudflareHelp @Cloudflare how do you expect we can contact support to gain access to my account, if you require to login to send a help request??? It's simple logic... I assume that your really don't care about helping your customers

• 
  Shimju David (@ShimjuDavid) reported 35 minutes ago

  @payloadcms Deploy on Cloudflare Fully self-contained — one click to deploy Payload with Workers, R2 for uploads, and D1 for a globally replicated database is not working. It returns build error. Kindly fix. 📷

• 
  Jasper Disney (@jasper_disney) reported 37 minutes ago

  As an unsuccessful app builder, I only need to pay 5 dollars to Cloudflare each month. Life is not that bad.

• 
  Caleb Sylvest (@calebsylvest) reported 37 minutes ago

  @jasondoesstuff Skip the CMS. Recently did the same. Used Claude to build everything Used Astro. Deployed to Cloudflare. Writing with MDX. Pre-rendered everything and served from Cloudflare edge network. Basically a fast as possible.

• 
  ShadeNoah (@ShadeNoah) reported 38 minutes ago

  @EddCoates Yeah that sucks... Has been an issue forever, though. Nobody gives a **** about robots.txt... No wonder CDNs like Cloudflare pretty much have over half the internet on their servers by now. See if you can rate-limit every request, or bite the bullet and use a CDN. Godspeed, mate.

• 
  Hunter Bertoson (@BertosonHunter) reported 43 minutes ago

  @jamesqquick Watched the network tab, reverse-engineered an undocumented API, and turned it into a Cloudflare Worker that catches failed attendance syncs and emails an alert every night. Workers + cron is unreasonably good for this kind of thing.

• 
  JD (@TooTrill4Thiss) reported 45 minutes ago

  @BoringBiz_ Every business doesn't need a custom agent. It needs an enterprise plan and a few capable devs who can map it, and deploy agents. building automation that don't rely on agent compute. like hello??? app scripts, compute engine, cloudflare workers. ******** are people doing?

• 
  Elshad (@elshad_ff) reported 45 minutes ago

  @Teknium Anyone using dashboard via Cloudflare tunnel? Have you websocket problem?

• 
  SpikeViper (@spikeviper) reported 46 minutes ago

  I am once again asking @Cloudflare for a response on why their support is radio silent on what is now a shady billing situation

• 
  Richard Sever (@cshperspectives) reported 47 minutes ago

  @manuelrivascruz working on solutions to this. the problem as I'm sure you can imagine is like so many sites we are being hammered by LLM bots in addition to all the DDOS attacks, so (again like many others) use services like Cloudflare to ensure human readers maintain access

• 
  Adrian Fritz (@adrianwjfritz) reported 47 minutes ago

  5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

• 
  rita kozlov 🐀 (@ritakozlov) reported 49 minutes ago

  at a lot of companies, product's role is to come up with ideas, carefully groom the roadmap and narrowly define requirements for engineering to (blindly) follow this maybe makes for an "easier" product role but limits creativity (and accounrability) one thing that's unique about cloudflare is that ideas can really come from so many more places product's role is to help map those ideas to customer problems and make sure we actually solve them and help get those ideas in customers' hands (aka actually ship it and make it good!) it makes for a much more interesting role and breeds so much innovation and leads to better experiences because engineering is not exempt from taking ownership in the deliverable. "i shippped what's in the PRD" is not good enough. you own the customer problems & solutions together

• 
  JustAnotherUser_4 (@JAU_4) reported 50 minutes ago

  @EddCoates Cloudflare firewall, thank me later. I blocked entire countries. Solved so many problems.

• 
  Autism Capital 🧩 (@AutismCapital) reported 57 minutes ago

  @jdoliner Sorry, can't do your scan today, Cloudflare is down.

• 
  Mundo Trading (@DonPepeVaquito) reported 60 minutes ago

  Is cloudflare down or it's just me?