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:

• 
  Vaibhav Sharda (@autobloggingai) reported 5 minutes ago

  Worst Cloudflare update? So stupid.

• 
  Sourabh (@iamsourabhshen) reported 7 minutes ago

  @levelsio @Cloudflare Are you going to build an email sending service now?

• 
  Tobias_Petry.sql (@tobias_petry) reported 8 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.

• 
  Godwin Iyke (@GodwinCod3s) reported 12 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Peter Mindenhall (@PeterMindenhall) reported 13 minutes ago

  @rustybrick @JohnMu Hmm - this is precisely why companies like @Cloudflare should not be doing SEO things - they cannot be trusted and make crap up. They have an opportunity to do good things well - yet they are making a mess and causing confusion for site owners.

• 
  Cleper 🌋 (@yaircleper) reported 14 minutes ago

  so @Cloudflare just did something most of crypto missed. Last week they launched the 𝗠𝗼𝗻𝗲𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗚𝗮𝘁𝗲𝘄𝗮𝘆. Any website, API, or app behind Cloudflare can now charge for resources on a per-request basis in stablecoins. No Stripe. No accounts. No checkout page. An HTTP status code from 1997, 402 𝘗𝘢𝘺𝘮𝘦𝘯𝘵 𝘙𝘦𝘲𝘶𝘪𝘳𝘦𝘥, finally doing its job. Why does this make sense for Cloudflare? Their CEO said it himself: 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 𝗮𝗿𝗲 𝗯𝗲𝗰𝗼𝗺𝗶𝗻𝗴 𝘁𝗵𝗲 𝗱𝗼𝗺𝗶𝗻𝗮𝗻𝘁 𝘂𝘀𝗲𝗿𝘀 𝗼𝗳 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁. Agents don't have credit cards. They pay per request, in milliseconds, or they leave. Cloudflare sits in front of roughly 20% of the web. 𝗧𝗵𝗲𝘆 𝗷𝘂𝘀𝘁 𝗽𝘂𝘁 𝗮 𝗺𝗲𝘁𝗲𝗿 𝗼𝗻 𝗶𝘁. But here is what almost nobody is asking. Every one of those payments settles on a blockchain. Millions of micropayments a day, verified and confirmed on-chain. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗺𝗲𝗻𝘁 𝗿𝗮𝗶𝗹 𝗶𝘀 𝗼𝗻𝗹𝘆 𝗮𝘀 𝘁𝗿𝘂𝘀𝘁𝘄𝗼𝗿𝘁𝗵𝘆 𝗮𝘀 𝘁𝗵𝗲 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘁𝗵𝗮𝘁 𝗿𝗲𝗮𝗱𝘀 𝗶𝘁. Ten weeks ago we watched $292𝗠 𝗱𝗶𝘀𝗮𝗽𝗽𝗲𝗮𝗿 𝗳𝗿𝗼𝗺 𝗞𝗲𝗹𝗽𝗗𝗔𝗢 because a verification network trusted the wrong data source. One more thought. 𝗔𝗱𝘀 𝗳𝘂𝗻𝗱𝗲𝗱 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁 𝘄𝗲 𝘀𝗰𝗿𝗼𝗹𝗹. In an 𝘪̲𝘯̲𝘵̲𝘦̲𝘳̲𝘧̲𝘢̲𝘤̲𝘦̲𝘭̲𝘦̲𝘴̲𝘴̲ ̲𝘪̲𝘯̲𝘵̲𝘦̲𝘳̲𝘯̲𝘦̲𝘵̲, nobody sees a banner. 𝘗𝘢𝘺𝘮𝘦𝘯𝘵𝘴 𝘵𝘢𝘬𝘦 𝘵𝘩𝘦𝘪𝘳 𝘱𝘭𝘢𝘤𝘦, 𝘢𝘯𝘥 𝘵𝘩𝘦 𝘷𝘢𝘭𝘶𝘦 𝘧𝘭𝘰𝘸𝘴 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘵𝘩𝘦 𝘶𝘴𝘦𝘳𝘴 𝘵𝘩𝘦𝘪𝘳 𝘢𝘨𝘦𝘯𝘵𝘴 𝘸𝘰𝘳𝘬 𝘧𝘰𝘳. What do you think, is the settlement layer ready for internet-scale payments?

• 
  breakfastmaxi (@pranavsf) reported 16 minutes ago

  @Cloudflare this is insane who ******** has stablecoins?? what about a normal debit/credit cards?

• 
  Prince Raj (@theprinceraj) reported 17 minutes ago

  @priyazsh @Cloudflare Well, you should get a visa/mastercard tbh if you plan to pay on international platforms. There are so many platforms especially web ones that do not support rupay cards and/or upi

• 
  Sean (@seanmozeik) reported 18 minutes ago

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

• 
  Ferbin (@Ferbin08) reported 19 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.

• 
  Ivy Finance🌍 (@ivyfinances) reported 21 minutes ago

  @williililii @pranavsf @Cloudflare That **** fonished last year

• 
  Hakimi Eiqbal (@hakimieiqbal) reported 22 minutes ago

  @levelsio @Cloudflare time to upgrade or start reading the docs for a custom domain fix

• 
  æthernet port (@aethernet_port) reported 23 minutes ago

  @opinioncasino Wow this moron owns Letterboxd? I didn’t feel bad about (sc)****** their website nonstop everyday bypassing cloudflare but now I actually feel good about it

• 
  dan ⚡️ (@mynamebedan) reported 23 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

• 
  ʙʀᴏɴᴢᴇ ᴀɢᴇ ʙɪᴛsʜɪғᴛᴇʀ (@bitforge_) reported 25 minutes ago

  @RealAlbanianPat If you pre-render your stuff I imagine you could put most of it in Cloudflare and be fine on their free plan or like a few bucks a month. Basically same as what @stephen_taylor is saying Look into "Jamstack" style architecture. I can help if interested.

• 
  Lilith Datura (@LilithDatura) reported 30 minutes ago

  @IntCyberDigest Cloudflare will be a problem for that going forward, anything centralized (rock and a hard place). Also CSAM comms with the whole Knots/Core Blockchain issue again yesterday. The parallels are interesting.

• 
  e_camli (@ekinoks_26) reported 31 minutes ago

  For the first time in internet history, automated traffic has passed human traffic. Cloudflare Radar shows roughly 57% of HTTP requests to HTML pages now come from bots and agents, versus 43% from humans. The caveat matters: this measures web page requests, not total bandwidth. But the crossover itself is the signal. Every access control system running today was designed for the other side of that ratio. CAPTCHAs assume most requests come from people. Rate limits assume human browsing patterns. Session-based authentication assumes a person sitting at a screen making decisions in real time. None of that infrastructure was built with the expectation that the majority of traffic hitting it would be non-human. Ade Adepoju flagged the core problem: agents outnumbering humans already, yet all our controls remain human-speed. An agent making thousands of API calls per hour operates at a pace no human-reviewed approval process can match. Waiting for a person to review each request isn't a security measure at that volume. It's a bottleneck that either gets bypassed or ignored. @RialoHQ built Latch around this exact inversion. Machine-bound identity and policy enforcement that operate at the speed agents actually work, not the speed humans review at. The Cloudflare number isn't a curiosity. It's confirmation that the control layer needs to be redesigned for a world where the majority of actors are already software, and that redesign needed to happen before the ratio flipped, not after.

• 
  Vivek Kotecha (@vbkotecha) reported 35 minutes ago

  Claude, Cursor, ChatGPT, Windsurf, VS Code, Hermes, Codex, Claude Code. 8 AI coding assistants. All support x402 payments. Every one of them will need data APIs. Market intelligence. Crypto data. Search capabilities. On-chain analytics. Right now, most agents use free APIs with rate limits and throttling. The moment an agent hits a paywall, it needs a wallet. This is why Coinbase built the CDP Bazaar. This is why Cloudflare launched the Monetization Gateway. This is why AWS added x402 to CloudFront. The infrastructure is being built RIGHT NOW. The APIs that get listed first will capture the early demand. First mover advantage in agent commerce isn't about having the best product. It's about being DISCOVERABLE when agents start searching for services.

• 
  haadi (@mhaadiabu) reported 41 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

• 
  fridgebuzz (@fridgebuzz_art) reported 41 minutes ago

  @tando_me @Cloudflare Convert them to fiat at your CX and withdraw. Problem solved.

• 
  Nathan Binford (@NathanABinford) reported 44 minutes ago

  Cloudflare HATES the open web. Why don’t more people see they are bad actors?

• 
  Bryce (@Bryce58831457) reported 46 minutes ago

  @ibocodes Cloudflare has some of the worst support imaginable I would never trust my business with them again

• 
  Jaime Medina (@itsJaimeMedina) reported 46 minutes ago

  New; Cloudflare Dynamic Worker APIs now can act more like CDN assets. Instead of only caching images/CSS/static HTML well, you can cache API responses, rendered HTML, search results, product/category pages, expensive database reads, AI responses, computed JSON, etc. You can put the Worker near the database, not necessarily near every user. This is probably the most important architecture change. If your database is in one region, running DB-heavy Worker code near that database avoids slow DB round trips. Then Workers Cache can serve the result close to users. That means: app logic near data, cached output near people.

• 
  Build Wealth After 40 (@BuildAfter40) reported 51 minutes ago

  @StockSavvyShay @FuturumEquities Cloudflare is interesting because it sits where traffic, security and AI agents increasingly meet. But the megacap argument still comes down to monetization. Handling more of the internet is powerful; turning that position into durable revenue growth, margins and cash flow is the test.

• 
  Akshat Mittal (@iakshatmittal) reported 51 minutes ago

  It took Cloudflare years to do this even though they ARE the CDN/Caching company, damn. This was my biggest blocker to using Workers for specific things. Better late than never, glad this is a thing now!

• 
  Alphatica (@alphaticaio) reported 51 minutes ago

  LARGE / MID-CAP DARK POOL | July 7, 2026 $NET +$142M zero sells. Cloudflare is the mid-cap safe haven. $CMG -$83M zero buys. $RKLB -$22M. $RIVN -$21M. Both agree sell. 62 prints. Q3 week two. $289M in buy prints. $308M in sells. Net: -$19M. Nearly flat. Buyers: $NET +$142M (15 prints, $0 DP SELLS, BOTH TAPES AGREE) $CRWV +$22M (3 prints, 2ND SESSION BUY) Sellers: $CMG -$83M (4 prints, $0 DP BUYS, ZERO) $EXC -$28M (1 print) $IREN -$24M (4 prints) $LITE -$23M (6 prints, BOTH TAPES AGREE SELL) $RKLB -$22M (2 prints, BOTH TAPES AGREE SELL) $RIVN -$21M (2 prints, BOTH TAPES AGREE SELL) $NET: +$142M. Zero dark pool sells. Both tapes agree buy. On a sell day where the mid-cap blocks were -$726M and the internals hit series lows on every metric, Cloudflare is the only mid-cap name the dark pool bought without opposition. +$142M dark pool, +$79M lit tape. Zero opposition on both venues. The mid-cap safe haven on a sell day is a cloud infrastructure name. $CMG: -$83M. Zero buys. Chipotle. Consumer discretionary sold with zero dark pool buying. Not one print on the buy side. $RKLB: -$22M. $RIVN: -$21M. Both agree sell on both tapes. Rocket Lab and Rivian, the growth/EV names that led Q3 week one, are being sold on both venues. The growth sell is cross-venue. $IREN: -$24M. Iris Energy. Bitcoin mining. Crypto-adjacent sold. $LITE: -$23M. Lumentum. Optical networking. Semi-adjacent. The sell is concentrated in semi-adjacent, EV, and crypto-adjacent names. The only buyer is cloud infrastructure. Yesterday: $MRNA +$123M zero sells was the headline. Today: $NET +$142M zero sells. The mid-cap dark pool is producing a new name-level signal each session. The patterns accumulate. The weekly scorecard builds. Watching the tape.

• 
  Haytham Chhilif (@HaythamChhilif) reported 52 minutes ago

  The Clanker Support stack, for the curious: - Cloudflare Workers + Hono on the backend (edge, cheap, fast) - Next.js for the dashboard + marketing - A tiny Vite-built widget that drops into any site - pnpm monorepo holding it together One embed script, runs at the edge, loads in ms. Happy to go deeper if anyone wants.

• 
  Ayush Chugh (@aayushchugh) reported 58 minutes ago

  Okay so my hypothesis was correct and the flyer was the main issue only. Imagine if I am buying 10 tickets together and adding those to my wallet, it would download a flyer from the bucket 10 times and optimise those using sharp individually even though the flyer was same for each ticket. So now, I have implemented a caching mechanism which will cache that flyer. Also, we are now using Cloudflare images for our flyer but passes were implemented with the S3 approach so now we are downloading the smaller flyer using Cloudflare image's transformation functionally. These are the new stats

• 
  Vivek Kotecha (@vbkotecha) reported 59 minutes ago

  Three payment protocols are racing to become the standard for machine commerce. x402: HTTP-native, governed by Linux Foundation, backed by Google, Cloudflare, Stripe, Visa. OKX Agent Payments Protocol: exchange-native, fast execution, integrated with OKX chain. Coinbase for Agents: wallet-native, largest distribution, built on Base. One will become the TCP/IP of agent commerce. The others will become legacy rails. Bet on the one with HTTP compatibility. Agent commerce does not need a new network. It needs a new status code.

• 
  Filecoin (@Filecoin) reported 59 minutes ago

  @thetobiaskrug @john_zuccaro @Cloudflare proof of possession and integrity comes first, ZK proofs over the data are a harder problem, but worth building toward.