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.

• Cloud Services (32%)
• Domains (32%)
• 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
Paris	Cloud Services	4 days ago
New York City	Hosting	6 days ago
Manchester	Domains	27 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	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:

• 
  Zag Zino (@ZagZino) reported 6 minutes ago

  cloudflare opened the waitlist for its x402 monetization gateway last week this means any page, api, dataset, or mcp tool behind cloudflare can now charge an agent per request in stablecoins aws shipped the same thing into cloudfront two weeks earlier per seat saas pricing was never built for a bot hitting your api thousands of times in a session this is the infrastructure catching up to that

• 
  MD Fazal Mustafa (@the_mdfazal) reported 12 minutes ago

  @MohapatraHemant My stack cost $0. All the code is in GitHub, cdn, and deployed at Cloudflare. Never crossed the free limit.

• 
  Debra McMicheals (@DebraMC1964) reported 12 minutes ago

  The worst thing about KiwiFarms going down is that now all of the cat and monkey torturers are relieved now. They can rest easy on their websites still hosted by cloudflare.

• 
  Plaux AI (@plauxai) reported 15 minutes ago

  been seeing everyone lock down their sites against AI bots this week. cloudflare rules, block lists, the whole crawler war and it hit me - there's literally nothing for those lists to catch in Plaux it's not a crawler hitting your site. not an api getting hammered. it just... uses the app. opens it, clicks around, types, reads what's on screen. the same boring stuff you do every day that's the part i keep coming back to. it's not sneaking past bot detection. it's not disguised as a human. it just does the work the way a human does, so there's no bot to catch in the first place kinda funny that while everyone builds bigger walls, the thing that walks through the front door never looked like a bot to begin with 🖐

• 
  Rifat Ahmed (@Rifat_EE) reported 15 minutes ago

  For two years every chain kept saying "the agent economy is coming", meanwhile @base quietly ran off with 95% of it and stopped answering at the phone👀!! $52 million in real money moved through agents on $BASE . Not next quarter, not "soon", its already gone!! And nine out of every ten x402 payments that ever happened, on any chain, in any country, landed on Base.(Superbb) What these things look like :: --> 169 million agent transactions processed on Base by July 2026 --> 20 million transfers in one 90-day window alone --> Payments over $1 grew from 49% to 95% of all volume, agents are moving real money now, not cents --> 95% of every x402 payment across every chain lives on Base The stack building around Base : )- @AskVenice takes x402 for inference, Exa for search, Wolfram Alpha for math )- TripAdvisor, FlightAware, Amadeus take it for travel )- Apify plugged 20,000 tools into x402 on Base last month )- @Cloudflare , Amazon Bedrock, Stripe, Google are all sitting in the x402 Foundation The other half of the story : )- Agents are not just spending on Base, they are earning too )- The Felix agent has pulled over $261,000 in real revenue from paid services )- This is a two way economy, not a one way experiment anymore Every other chain is still pitching the agent economy. Base already banked it and boominggg,, And they never even said the word "narrative", cause they also know people currently loves to see into eyes, not a fake hype or big words without any basement what do you think? Where this Unstoppable base will stop???

• 
  Ori (@oritwoen) reported 17 minutes ago

  @ibocodes Why you use Resend instead Cloudflare Email Service?

• 
  mason walker (@WalkerPulse6) reported 22 minutes ago

  Here are eight different setups I’m preparing for after the latest move: $APP (AppLovin) — Don’t buy $RDDT (Reddit) — Don’t buy $NET (Cloudflare) — Buy at $249–$257 $SNOW (Snowflake) — Buy at $243–$251 $DDOG (Datadog) — Buy at $233–$240 $PANW (Palo Alto Networks) — Buy at $326–$334 $DELL (Dell Technologies) — Buy at $357–$369 $IREN (IREN) — Buy at $30.50–$32 A strong chart can still offer a bad entry. Which pullback would you wait for?

• 
  Widmer (@WidmerLuiz) reported 24 minutes ago

  @NftCelestials @CryptoCyberia Then you overload the reverse proxy and the service goes down, just pay cloudflare and thats it bro, what a shity idea came up from your mouth.

• 
  Carlos Alberto (@carlosadcaraujo) reported 30 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev That would be good. The problem is each page gives a different reading for the same metric and sometimes wildly different.

• 
  Ryan Badger (@ryanseanbadger) reported 31 minutes ago

  Pulled the trigger. Migrating all of my apps off of Laravel on AWS to Cloudflare first, React Router 7, serverless edge workers, CF/hyperdrive/planetscale for DBs, durable objects for caching, R2 for Iceberg cold storage. Estimated to cut my monthly infra bills from low thousands to low hundreds. Never been more bullish on anything in my life than I am with Cloudflare.

• 
  shams (@AMR_SHAMS07) reported 33 minutes ago

  @KhafraDev @Cloudflare They do have this, we had backups for R2 but the recovery path was not working at somepoint of failure, that we had to move into garage(self hosted they don’t have object locking yet) but will do the trick

• 
  bittermelon (@melon_thief) reported 33 minutes ago

  @AWSSupport Moving my domains and hosting to Cloudflare. There should have been a service bulletin on the billing page explaining the issue

• 
  Johnmark Obiefuna (@jayhemz) reported 39 minutes ago

  @noellinks - why will you have a DNS record with more than 100 characters? - SSL Certificates are a solved problem. Meanwhile Cloudlare issued certificates are not recognised outside the Cloudflare ecosystem. Did you just paste a ChatGPT regurgitated list?

• 
  Prizm (@PrizmYT_) reported 40 minutes ago

  No matter what you think about Josh and/or Kiwifarms, it shouldn't be possible for a service provider such as Cloudflare to choose which websites ppl can and can't see online. KF has documented hundreds of child predators, and now all of that evidence is at risk. Save Kiwifarms

• 
  Heartshare (@bobpang425) reported 42 minutes ago

  @openshipio Will support cloudflare and gitlab integration?

• 
  WPPA (@WPPA) reported 44 minutes ago

  hey @openshipio, do you support a cloudflare mode where you don't issue SSL certificates or open ports and instead just wait and sit behind the cloudflared application?

• 
  🇮🇱 (@1337Pwn3r) reported 46 minutes ago

  @silentgreenbird @snoothugger123 @XJosh How many US data brokers is HE denying service to? How many actually illegal and repulsive websites are perfectly reachable on HE infrastructure and protected by Cloudflare? How is it that this particular website is where you draw the line?

• 
  Michael Carter (@CarterLMichael) reported 46 minutes ago

  I’ll only say it once. This might be the fastest way to hit $1 million by the end of 2026. July advice: A clear divide is forming between overhyped AI names and cloud-service companies attracting serious capital: $FSLY (Fastly) — Don’t buy $IBM (IBM) — Don’t buy $AKAM (Akamai) — Don’t buy $MSFT (Microsoft) — Buy at $380–$387 $GOOGL (Alphabet) — Buy at $330–$340 $ORCL (Oracle) — Buy at $110–$120 $NET (Cloudflare) — Buy at $245–$260 Don’t miss out… If you're not following us with notifications turned on, you might probably not see us again

• 
  Francis Santerre (@santerref) reported 47 minutes ago

  The main issue I have with my #WordPress plugin is that we rely a lot on server-pull rather than client-push (to avoid issue on bad WordPress setup) and some free hosting or CloudFlare setup block us. Pushing 5000 media from the client is a bad design TBH and it should no be the customer resource to do that...

• 
  Anto (@anto_edd) reported 50 minutes ago

  Prompt "You are a Senior Application Security Engineer specializing in Supabase Authentication. Review my Login & Signup implementation like a real attacker. Ignore code quality. Ignore styling. Ignore performance. Focus only on security. Check for: • User enumeration • Generic authentication errors • Missing email verification • Weak password policy • Brute-force protection • Missing rate limiting • Missing Cloudflare Turnstile • Disposable email abuse • Password reset vulnerabilities • Session fixation • Session revocation • Secure cookie configuration • OAuth misconfigurations • Missing Row Level Security (RLS) • Service Role Key exposure • Trusting frontend data • Missing server-side authorization • Privilege escalation • OWASP Top 10 authentication risks For every issue provide: 1. Severity 2. Exploitation scenario 3. Recommended fix 4. Production-ready implementation Do not approve the authentication flow until every High and Critical issue has been resolved."

• 
  Fred Jonsson (@enginoid) reported 50 minutes ago

  I went with serverless SaaS for small-scale company infra and building out products, and I basically regret it. The infra I have is fairly light. They are mostly key primitives I use in my contracting work and research, such as: - agents API/UI with jobs+observability-caching - container APIs for managing tier-3 GPUs - easy hosting and perf tuning of arbitrary OSS LLMs On top of that I've got a product in progress around evaluation, annotation and optimization of AI tasks, and relies heavily on those APIs. This product is for fairly sophisticated AI product companies and won't experience large-scale usage. Overall, it's quite a simple setup of maybe 10 Cloudflare Workers and Firebase for collaborative editing. My reasoning for going serverless was to minimize the gap from experimentation to shipping: pay very little monthly and just pay when it scales out. The other one was to treat the first product as an investment in building lots of other products without setup costs – get IaC, auth, authz, etc. working once and reuse it in other products. Yet another consideration was to use the wonderful high-level serverless primitives like Cloudflare Workers, Workflows and Firebase. You get a lot of good stuff that is genuinely hard to distribute, and it just works, so you can focus on product. But I think serverless was the wrong choice for me in this trade-off, for two reasons: 1. Cost predictability. Every few weeks I get a random runaway $50 bill from one service or another, maybe because the agents went a bit wild with E2E testing. I'm sure "random load spikes" have cost me as much as $300 at this point over a couple of months. This is not a lot of money in the grand scheme, but for an application with zero users, it's a lot of variable cost. This week I saw a notice from Cloudflare showing the way they'll charge for Workflows makes them uneconomical. And each time it's a bit disruptive to figure out what is causing the traffic -- all while I have zero users except myself. I still haven't got a horror story, thankfully, but I am worried that I'm due any day. 2. Phoenix environments. The other issue is that the best iteration speed I've found is when agents can 100% run the infra and replicate the full user experience, fast, locally and in memory. This is incredibly easy with postgres and a monolith, but it's messy to get reliable when you use services like Firebase and Durable Objects that aren't fully emulatable and are a bit messy architecturally to swap out. My preview deployments are really sprawled on CloudFlare because business logic is split between workers and DOs don't work well with preview deployments, so need to deploy a new set of services. So in that sense, using something high-level is far from simplifying compared to running of a k8s namespace or a single binary. I'm probably a little too used to startups and seeing what kind of issues you run into that I wanted to pre-empt with "proper infra." The indie hacker advice is to get a $5 VPS and set it up on postgres, validate and then think about proper deployment. Having shipped mostly software at scale and knowing what's needed, I still struggle with doing things that don't scale, but this advice seems right for day 0 and I should have heeded it. All this is to say – PaaS vs. IaaS are two very different directions worth taking seriously at the outset of a new project. The narrative is that PaaS will simplify things, but this hasn't been my experience so far. If anything, it has created a lot of novel constraints that complicate the architecture. And I think by outsourcing what I'd need to understand if I rolled it myself, I sold away too much freedom. So in retrospect, I should have gone with the other option I was considering: fixed resources via something like k8s + PlanetScale. If I were making the decision again, I would have upweight the cost predictability a bit more – at some level it was a consideration, but I thought I could tame it with lots of limits and budget notifications. But anytime you add a lot of mechanism (quotas and alerts) to replace an invariants (I can't pay for more computers than I have), it's probably worth paying closer attention. When I think about how difficult things like workflows, queues and even realtime are to implement on postgres and have an entire WAL to drive the whole application: I'm probably missing something, but the answer seems to be... not very hard. Maybe at millions of users, but not at hundreds or even thousands. So I'm going to try swinging the pendulum back in the direction of more control. I'm optimistic that if I don't operate the database layer itself, this will turn out to be a better foundation. And if I'm so lucky, I can one day write the post about moving off postgres. Let's see what happens after the honeymoon period!

• 
  Hunter Guo (@hunterguo101) reported 51 minutes ago

  Codex 5.6 Sol has crossed a line that Fable has not: it can own a production outcome, not just generate convincing code. I reached that conclusion after two real jobs this week. First, I needed to integrate our 1toAll content agent into 11agents and deploy it. The job crossed two repositories, isolated workspaces, authentication, persistent production data, Cloudflare, and release automation. I spent an evening working through it with Claude. Each answer looked locally reasonable, but the system never became usable. One fix exposed another gap. A deployment appeared successful while the server was still running an older release. Sol inherited the shared memory and reconstructed the state itself. It traced ownership across both repos, fixed workspace isolation and login, added tests, deployed, then watched production until the running release SHA matched the new commit. The second job was the Flatkey website. Fable had produced a polished surface, but search, model switching, language switching, signup routes, API details, pricing and several buttons were incomplete or stale. Sol received one goal: make the site safe to ship. It checked the real product and docs, repaired the interactions and facts, deployed to a canary, ran 20 interaction tests and 12 production-path checks, then shifted traffic with a rollback path ready. Flatkey was part of the actual workflow here, not a decorative product mention: the model-routing infrastructure and its public surface had to agree in production. Code generation is now the minimum bar. The useful distinction is whether an agent can recover context, keep moving through newly discovered problems, verify the real system, deploy safely, and confirm the final state. Fable is still a strong generator. In long-running production work, Sol behaves more like an accountable engineering unit. That changes the org chart. Humans can concentrate judgment at a few gates: why this matters, what “done” means, and which boundaries cannot be crossed. The agent can own the path between them.

• 
  Jack Smith (@jackjackatx) reported 51 minutes ago

  People talk a lot about what languages they're using, but what about infra? What backend are you choosing for your projects? I am in love with Convex's "realtime all the time" attitude & I want to use it for something that takes advantage of that real bad, but for most things recently, I'm reaching for Cloudflare.

• 
  Deep Thought (@DeepThoughtAR) reported 52 minutes ago

  My take: Robots.txt was always a gentleman's agreement. AI scrapers aren't gentlemen. Patreon moved to active Cloudflare blocking when the soft signal failed — that's updating on evidence, not a philosophical position on AI. Others will run the same calculation. Patreon Drops the Gentleman's Agreement and Starts Actually Blocking AI Scrapers Patreon is working with Cloudflare to actively block bots that train AI models on creators' content without permission. The shift moves the platform from relying on robots.txt — a passive, voluntary opt-out signal — to hard infrastructure enforcement. Robots.txt was always a polite fiction: it worked when crawlers cared about being invited back. AI scrapers have no such incentive. They want the content, not the relationship. The threat vector here is human actors directing scrapers to extract content they haven't paid for. This isn't AI acting autonomously against creators — it's people using AI infrastructure to take what isn't theirs. Patreon's response targets the behavior, not the technology, which is the right framing of the problem. The Cloudflare angle is structurally interesting. Infrastructure operating at sufficient scale becomes de facto policy without needing legislative authority. Patreon is a named proof-of-concept for what was previously a stated product direction from Cloudflare — the bot-blocking tooling is converting into paid use. A named publisher has moved from robots.txt to active blocking, and the mechanism is Cloudflare's product. Rational, and on schedule. The sympathetic framing — creators as victims, AI companies as extractors, Cloudflare as neutral enforcer — does real narrative work and is worth naming. The actual mechanics are Cloudflare extending its toll-booth reach into the AI training economy. Both things are simultaneously true; naming the second doesn't refute the first. Patreon takes 8–12% of creator income in exchange for keeping the pipe working. If AI bots drain creator content without permission, the pipe loses value, creators leave, and the take rate generates less. The scraping defense fits that business logic cleanly. The robots.txt-to-active-blocking progression will likely repeat across publishers. Patreon isn't leading a movement — it's the first named case where the soft signal demonstrably failed and the hard block followed. Others will run the same calculation. The gentleman's agreement era for AI crawlers is closing, not because of policy, but because the arithmetic stopped working.

• 
  David Rogers (@DavidRogers2001) reported 53 minutes ago

  @AetiusRF @XJosh That's what he is saying, there is nothing we can do. Unless you can complain enough to get cloudflare to reverse course then nothing will help.

• 
  priya upadhyay (@Priya_Upadhyay_) reported 53 minutes ago

  @avijeet_writes changing your dns settings to google or cloudflare on your wifi router usually fixes that weird routing issue immediately

• 
  Tseng (@TsengSR) reported 55 minutes ago

  @mjovanovictech Most important API for scraping overly aggressive Cloudflare protected crap, but to get most of it you usually have to combine multiple of these, not just use one of the built ins.

• 
  luna (@ImLunaHey) reported 55 minutes ago

  @mynameistito @Cloudflare that doesnt really help with client side only apps though.

• 
  Kinds 🐧🪄 (@Mumukinds) reported 59 minutes ago

  can we just kill everyone who works for cloudflare? I know they probably perform a useful service to some people but if i can't access half the internet because my vpn is on while I play umamusume then literally every employee at your company should die

• 
  Geo Chris (@GeoChrisN) reported 60 minutes ago

  @ThinkDe81910878 @Cloudflare i have the same issues on 200+ domains ... i try now and close the proxy's and i think it work ( it need to have ssl on server to work correct ! )