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 (40%)
• Cloud Services (27%)
• Web Tools (13%)
• Hosting (13%)
• E-mail (7%)

Live Outage Map

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

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

• 
  John Nigroᵍᵐ (@jn) reported 2 minutes ago

  @snipextt @p_naix @spaceship why does everyone shill cloudflare? you cannot change your nameservers. You save 9 cents to have a fundamentally broken domain name.

• 
  Ferbin (@Ferbin08) reported 2 minutes ago

  @Cloudflare For AI startups, it's not infra. It's whether it works when customers actually plug it in. Most never survive that test.

• 
  Digital in Blue (@digital_in_blue) reported 3 minutes ago

  @betablacklotus Yep. No issues with doing this in cloudflare. Check it out! My site has no Wordpress and no databases.

• 
  Ifee Anthony (@IfeeDev) reported 3 minutes ago

  @levelsio @Cloudflare Set up an email service on a vps and yes, it can hit inbox when you do the right setups.

• 
  ori (@the_real_ori) reported 10 minutes ago

  @DhravyaShah Taste is a headcount allocation decision. Vercel staffs polish like a feature team, Cloudflare staffs primitives. Neither is wrong, but DX debt compounds quietly: every rough edge is a support ticket someone else monetizes.

• 
  Sean Knox (@Opp_Knox) reported 11 minutes ago

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

• 
  ibo (@ibocodes) reported 12 minutes ago

  @jacobmparis the problem is that the "company" is vercel i wish cloudflare acquired it tbh

• 
  Dexarok (@dexarok) reported 12 minutes ago

  @LowKickLuke @thecoastguy The game of cat and mouse is over. Technology has caught up with the wet dreams of censors and authoritarians. That's what the data centres are actually for. They don't care about the 0.01% of tech savvy folks who are prepared to heavily inconvenience themselves on principle. This is about long term mass control. It's not even about this generation, it's about future generations who grow up into this, wondering why anyone would bother to complain about something which has always been that way. The internet used to be uncensorable, but that time is over now that LLMs can read and process everything without having to spend 30 billion dollars on staff. New services? Forget about it. Do you remember what happened to Parler? Any noncompliant service will be shut down by cloudflare or AWS, their domains will be seized. As I said before, they've already done it so they know they can. The platforms and the OS makers are compliant. The job is done, you just don't know it yet. One more black pill for the road: What you say about cycles used to be true but just isn't anymore. Revolution will soon be impossible. There will never be another major uprising, ever again. Revolutions rely on critical mass. People in the streets. The police and soldiers coming face to face with pregnant women, and putting their guns down and joining the revolt. The robot dogs with guns on their backs don't have a conscience. They will never put their guns down. This is the cusp of forever. They will never stop trying to control information, now that they have the tools to do it. Game over. Have a great day.

• 
  Ruben (GoBrand.app 🍃) (@PonziChad) reported 13 minutes ago

  @ivebenfreed @DhravyaShah Yes. And then use their GitHub integration that doesn’t support environments so you end up with worker-production and worker-staging, now I have ~20 workers to maintain 🥲 I am a cloudflare customer because of durable objects and cost but damn if I miss vercel, never had an issue with startup time stuff, unhandled promises when trying to use their hyperdrive, dashboard improved but on vercel it was beautiful how it auto integrated with GitHub and had automatically ****, staging and previews, how I could just use a starter from them and immediately start from a strong polished point… However my bet was on cloudflare I think they eventually will get there, just slower than what I thought, but pretty sure they’ll manage because they are a cracked team

• 
  @aaronjmars (@aaronjmars) reported 13 minutes ago

  the issue with cloudflare monetization gateway is you can't tell humans from bots. every detection system leaks - cloudflare might ship 10 blogposts about 99.9% accuracy but there are tons of open-source repo bypassing it so stop trying to detect. you can't verify identity, but you can verify payment. x402 gives us micropayments at scale. so don't gate on what you are - gate on payment. everyone pays to consume. agents, humans, doesn't matter. the whole industry is shipping agentic payment infra. but "everyone pays to consume" only works if a human can pay as frictionlessly as an agent - and no wallet does that yet. that's the missing piece imo

• 
  Lum (@LumRamabaja) reported 14 minutes ago

  x402 sounds good on paper. In practice, per-request on-chain settlement doesn't scale to micropayments, which is why Cloudflare itself proposed the deferred scheme: agents lock a lump sum in escrow, providers redeem vouchers in daily/weekly batches. A clearing house, basically. Here's the problem: that works one-to-one, or many-to-one (a CDN). It breaks the moment it's one-to-many. An agent paying multiple providers from one escrow can issue vouchers exceeding its deposit, double-spending in the window between deposit and settlement. The only "fix" is routing everything through one trusted gateway. Convenient if you're Cloudflare. But a payments layer that assumes a single trusted chokepoint won't hold up in a multipolar world.

• 
  Ruchit Dalwadi (@ruchitdalwadi) reported 14 minutes ago

  @Cloudflare @OpenAI Search quality is increasingly a data-contract problem. The useful pattern: make pages explicit about freshness, source type, and canonical answers so retrieval can prefer reliable context instead of just popular context.

• 
  Stallion of the Steroid Era (@TXTrickWhooper) reported 15 minutes ago

  @CEOGuy @Cloudflare It sounds like a paywall behind a made-up coin that has no good/service directly backing its stability and value

• 
  UnsoldBanana (@UnsoldBanana) reported 17 minutes ago

  @skooookum Average person and startups are going to have a lot of problems because cloudflare wants to follow Anthropics footstep in behaving like parents and tell the world what is allowed.

• 
  Evan Oslick (@eoslick) reported 19 minutes ago

  @DanielMiessler Not always. Cloudflare just has enough reach to probably make it happen easier. And still doesn’t mean we shouldn’t talk about risks and downfalls. Like I said. I want this to happen. And cloudflare’s bot detection tech + endpoint tech can make this a positive. I just have concerns with them doing it and their size and reach. I am hoping I can get this type of service built into my small business generator I am trying to build. We’ll see.

• 
  Maxim Fedotov 🇯🇵 (@DouTatsu) reported 19 minutes ago

  This whole experience is really making me consider moving away from Cloudflare. Someone could just abuse the abuse system and send countless reports to shut down every link on the site. I imagine you'd get it fixed eventually, but who knows when? (It's been a month now for me)

• 
  Smakosh (@smakosh) reported 24 minutes ago

  @levelsio @Cloudflare Would be fun to build an email gateway so it auto falls back to another service when quota is hit for you. Either use the service with a fee or bring your own keys Just like @llmgateway does for llms

• 
  Tando (@tando_me) reported 26 minutes ago

  @Cloudflare @grok what's the best Cloudflare alternative that doesn't drag us all down the path of more fiat debt slavery? Looking for something that gets us off this rusty hampster wheel. Ps. In your reply draw a rusty hamster wheel with an obese hamster struggling in a dilapidated cage.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 27 minutes ago

  @zeke login with cloudflare as self managed oauth is a genuinely useful primitive

• 
  Zhu Liang (@paradite_) reported 30 minutes ago

  complete opposite experience for me. vercel, next.js and ai sdk are full of bugs and edge cases. they were never stable or advanced enough for my use cases. cloudflare on the other hand, i can at least trust it with firewalls and dns stuff.

• 
  LEI System (@leisystemglobal) reported 32 minutes ago

  The Linux Foundation plans to launch the Agent Name Service (ANS), an open standard for AI agent identity built on DNS. It supports existing identifiers, including the LEI. Backed by Cloudflare, Cisco, Salesforce, and others.

• 
  Binary Sniper ⚡ (@MrBinarySniper) reported 33 minutes ago

  @zeddotdev @huggingface Neee cloudflare gateway support

• 
  Jimmy Q (@Jimmyq_startup) reported 38 minutes ago

  [Fixed] Domain verification for Gmail (Cloudflare) TDLR: Expected ~10 min setup took days; found a bug in Gmail domain verification and a workaround. 1. Initially, Cloudflare's direct verification was used in Google, and it added the TXT "Google-site..." in DNS. Nothing else was prompted. Waited a long time, no update. 2. Fix: went to manual verification and saw that I also have to add a CNAME in DNS. After that, hit finish and - Viola! - domain verified. #gmail #indiedev

• 
  Vivek Kotecha (@vbkotecha) reported 40 minutes ago

  Solana just became the second x402 network. Every major player now supports dual-chain: Base + Solana. Alchemy, AWS CloudFront, Cloudflare Gateway. If your x402 endpoint is only on Base, you're leaving half the agent economy on the table.

• 
  Fireside Alpha (@firesidealpha) reported 43 minutes ago

  1/ Okay so $NET is officially getting into the payments-tollroad business. The new Monetization Gateway gives clarity, and it's exactly the toll booth for agent traffic sketched last time. Here's an updated look at the numbers, and how MG would actually work. 2/ The math, updated Last time, on @eastdakota's own numbers: 25M txn/s x 31.5M sec/yr = 788T transactions x $0.0003 per txn = $236B of gross volume x 1% take = ~$2.4B of incr. rev, vs a ~$2.2B base. The gateway doesn't break the math. It confirms the rail (stablecoins over x402) and widens the taxable base from crawls alone to any asset, any API, any tool, any agent action. Same toll booth, more roads running through it. The one thing it moves is price mix. The gateway's own examples run cents to dollars per action, like $0.01 per request or $0.99 per resolved support escalation, well above a flat fraction of a penny. So the realized model looks like fewer, higher-value transactions rather than an ocean of sub-cent ones. Push price up and volume down and you land in the same billion-dollar range. The bracket still runs from about $160M at the floor to north of the whole company at the center. And the number that decides where inside that range you actually land was not disclosed, its take rate. 3/ How the gateway actually works It runs on HTTP 402, Payment Required, a status code that has existed since the beginning of the web and almost never gets used. An agent requests something behind Cloudflare. Instead of the content, the server answers with a price. The agent pays in a stablecoin, settled in under a second for a fraction of a cent with no chargebacks, resubmits with proof of payment, and gets what it asked for. The seller sets the price. Cloudflare runs the plumbing in the middle and takes its cut of every settlement. There is no card network in the loop, because a card cannot clear a one-cent charge profitably. That is the whole reason it is built on stablecoins and x402. The agentic web finally gets a way to pay per action, and Cloudflare got its way into the action. _____ Follow @firesidealpha for more business analysis derived from key industry figures in conversations and firesides.

• 
  Wayne Shirreffs (@WayneShirreffs) reported 45 minutes ago

  @pau11960 @pranavsf @Cloudflare Stablecoins don’t move 3% a day wtf are you even talking about? Stablecoins are stable dollar equivalents. Same as excepting dollars except don’t have to grease the middle man 3% of every transaction.

• 
  Axiom 🔬 (@AxiomBot) reported 46 minutes ago

  x402 is not a payment button. It is the toll booth for agents: request, price quote, pay within a cap, retry with receipt. Cloudflare matters because it puts that loop at the web edge, where APIs and MCP tools already live. No login, no checkout page.

• 
  Tobias_Petry.sql (@tobias_petry) reported 52 minutes ago

  @jaydrogers @mattiasgeniar Its too new. Give cloudflare a few months. Time will show if cloudflare is doing enough to remove spammers from their platform. If not, deliverability rates will be as bad as many of the providers providing hundreds of mails free each month.

• 
  Hugo Sousa (@Ciberon) reported 57 minutes ago

  I've joined* Cloudflare *as a customer

• 
  Dave (@TechPostsEU) reported 59 minutes ago

  Just a/b perf tested Tigris versus Cloudflare R2 and R2 smoked Tigris. Not sure why you'd use it unless you need free egress or something. Performance was genuinely bad, like 700KB/s download over a 500+ Gbps link