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	26 days ago
London	Domains	28 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:

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

  @betablacklotus @GoDaddy @GoDaddyHelp I recently switched to Cloudflare and I am never looking back.

• 
  𝐋𝐚𝐤𝐬𝐡 𝐑𝐚𝐠𝐡𝐚𝐯𝐚𝐧 (@laraghavan) reported 12 minutes ago

  @Cloudflare Will @beehiiv support this natively? @denk_tweets?

• 
  UP-LVL.com (@uplvls) reported 12 minutes ago

  @jessepollak Can we get cloudflare on web3 half the internet and half of crypto goes down still when their down

• 
  Carlo Buonpane (@Carlo_Buonpane) reported 14 minutes ago

  @brian_armstrong The stablecoin settlement is the useful part, a rail that clears without a card network skimming the middle. Everything else routes through Cloudflare, so "native to the web" really means native to one company, and the off-switch that turns your page dark stays in their hands.

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 17 minutes ago

  @Eli5defi @Cloudflare good thing is cloudflare already sits in front of 20% of the web. protocol adoption problem solved by default. distribution wins again

• 
  Vivek Kotecha (@vbkotecha) reported 19 minutes ago

  In 1995, the HTTP 402 status code was written into the specification. "Payment Required." Nobody implemented it. In 2025, Coinbase revived it. In 2026, Cloudflare, AWS, and the Linux Foundation all built production infrastructure around it. x402 has now processed 169 million payments across 590,000 buyers and 100,000 sellers. Not projections. Settled transactions. A 31-year-old placeholder in a protocol document became the payment layer for machine commerce. The infrastructure was always there. It waited 31 years for a customer that wasn't human.

• 
  Sooraj (@whotooksooraj) reported 19 minutes ago

  TIL Cloudflare uses Google chat instead of slack, wtf?

• 
  Fireside Alpha (@firesidealpha) reported 22 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.

• 
  Rafael Martins (@rgmcorp) reported 24 minutes ago

  Anyone getting 500 errors from Cloudflare security challenges?

• 
  KevinC (@Fbkevy) reported 24 minutes ago

  @mygovid I can't verify my account. The screen with the email log in says the page is not available after the cloudflare check. I tried on another phone. Cleared cache etc. Please fix your app

• 
  Soqucoin (@soqucoin) reported 24 minutes ago

  Watch what the biggest vendors do. They see the threat models first. Google committed its infrastructure to 2029. Cloudflare matched it. Now Microsoft. Our network never needed a deadline. Post-quantum has been the foundation since block zero.

• 
  haadi (@mhaadiabu) reported 26 minutes ago

  @DhravyaShah honestly cloudflare has really cool infra but it’s always such a pain to work with deploying an app to workers is so frustrating. everyone talks about vercel’s “lock-in” but you don’t need to fight configs to get your deployment up worst case scenario you add a nitro plug-in

• 
  Lord of Candy | Kaeos (@Lord_of_Candy) reported 26 minutes ago

  "But I can’t help build or maintain a path whose purpose is to defeat Cloudflare/Turnstile verification, even if older work crossed that line or framed it as scraping." Did OpenAI get in league with CF to stop bypasses? This is new to me. And stupid. Thanks nan.

• 
  Eli5DeFi (@Eli5defi) reported 28 minutes ago

  This is insanely big. @Cloudflare just opened a waitlist for its Monetization Gateway. Simply put, it lets any site, API, dataset, or tool behind Cloudflare charge AI agents directly in stablecoins using the x402 protocol. Old monetization models were built for humans: → Ads need attention and clicks → Subscriptions need logins and retention → API keys and per-seat pricing need accounts and ongoing relationships AI agents don’t behave like that. They make hundreds to tens of thousands of requests per human visitor, consume the resource once, and leave. They have no reason to watch ads or maintain logins. Credit cards and bank rails cannot handle real micropayments: → Fixed fees eat the entire transaction → Chargebacks and slow settlement add risk and delay → Onboarding friction (accounts, KYC, API keys) breaks autonomous agents Stablecoins solve the economics via x402. Near-zero fees and near-instant settlement make tiny payments viable. Cloudflare runs payment verification and enforcement at the edge across 330+ cities. This protects origin servers from high-volume payment traffic. They are not launching its own chain or token. It is embedding existing stablecoin rails into the HTTP request path at global scale. Tbh this will accelerates the shift from “block the bots” to “charge the agents.” When machines become primary consumers of content and APIs, usage-based micropayments become one of the few scalable business models left.

• 
  Sean (@seanmozeik) reported 29 minutes ago

  .@Cloudflare @PlanetScale I'm trying to setup unified billing for PlanetScale, but getting cryptic payment errors, can anyone help?

• 
  ori (@the_real_ori) reported 30 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.

• 
  Sponko (@sponkostonko) reported 33 minutes ago

  … is cloudflare down?

• 
  Jeremy Shepherd 🔻🇵🇸 (@jeremy_wokka) reported 34 minutes ago

  @Cloudflare You have to scroll down a LOT to get past the blue check zombies and into the replies from non-mouth breathers who pay for twitter and then you can see how unpopular this is

• 
  Kayhan (@KayhanB21) reported 37 minutes ago

  It seems the @Cloudflare Workers AI model GLM 4.7 has not been working for the past few days; I keep getting 504 errors.

• 
  Tate Johnston (@cheurouge) reported 42 minutes ago

  Does it support Cloudflare?

• 
  dan ⚡️ (@mynamebedan) reported 51 minutes ago

  only cloudflare really could've done this. i can see a path where this leads to an even bigger monopoly of their service. the stripe effect but much larger. i happen to really like this model of paid services on the internet, it's so simple and effective

• 
  jason silberman (@_jasonsilberman) reported 51 minutes ago

  thanks to everyone at cloudflare for responding and helping resolve this! it's great to see this level of customer support on X, and i hope the in product customer support continues to improve. i think even a fully ai support agent would be able to handle claims like this quicker in the future

• 
  FixlyAI (@Fixlyai) reported 52 minutes ago

  AI companies have been stealing the web. Not hacking it. Not paying for it. Just taking it. OpenAI crawls 1,700 pages to send back 1 visitor. Anthropic? 73,000 pages. One referral. Publishers pay the bandwidth. AI companies keep the value. No credit. No payment. No permission. Cloudflare just decided that ends on September 15. Any bot scraping ad-supported pages without permission gets blocked by default. Search crawlers stay. AI training bots don't. "The majority of traffic on the internet is now non-human." The web was never built for this. And now someone is finally doing something about it. Every AI product built on scraped content has 70 days to figure out what comes next. Are you one of them?

• 
  Alex Prompts (@alexpromptz) reported 53 minutes ago

  @Cloudflare Which crypto network we using?

• 
  Mike Pruta | AI employees (@prutadigital) reported 55 minutes ago

  @levelsio @Cloudflare The scary part isn't the newsletter going down — it's password resets and receipts riding that same quota. They fail silent: no error, the user just can't log in. Worth keeping transactional on its own domain and sender so one cap can't lock people out.

• 
  Hueglist (@Hueglist) reported 57 minutes ago

  @Cloudflare @grok dumb this down so I can understand what it means.

• 
  Ewan (@ewan_tindale) reported 59 minutes ago

  The majority of this was a 1 shot. Fable handled all the "models", animations, zombie sounds, shooting sounds etc by itself (downloaded them from online I guess? I didn't pay much attention) Even for the game design, I just told it to copy the fun parts of COD zombies but for the browser using @threejs then I followed up to fix a few small issues with the menus, multiplayer, box collisions, melee range, added some music tracks. Running on @Cloudflare Workers/Durable Objects

• 
  defido 👊⛽️ (@defido) reported 60 minutes ago

  @KayhanB21 @Cloudflare Their entire workers AI suite is down or not working properly

• 
  Maxim Fedotov 🇯🇵 (@DouTatsu) reported 1 hour ago

  Been really frustrated with @Cloudflare @CloudflareHelp recently. Their abuse system is so broken - I get a notice, I follow the instructions to send a response. I then get an auto-reply saying it's not for responses, so their instructions literally contradict each other...

• 
  Rahul Kumar Singh (@rahulitblog) reported 1 hour ago

  @Cloudflare @Cloudflare, what about Cloudflare Pages support?