1. Home
  2. Companies
  3. Cloudflare
Cloudflare

Cloudflare status: hosting issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

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.

At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

  • 40% Domains (40%)
  • 27% Cloud Services (27%)
  • 13% Web Tools (13%)
  • 13% Hosting (13%)
  • 7% E-mail (7%)

Live Outage Map

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

CityProblem TypeReport Time
Manchester Domains 16 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:

  • TickerTalksX
    TickerTalks (@TickerTalksX) reported

    HTTP 402 "Payment Required" has sat unused in the web's plumbing since 1995. Written into the spec, never switched on. $NET (Cloudflare) just switched it on. Its new Monetization Gateway lets any site behind Cloudflare charge per request, settled in stablecoins, and the obvious customer is the AI crawler. Those bots hit a page anywhere from 100 to 10,000+ times for every human visitor they send back. No ads seen, no subscription bought, gone. Free scraping at scale. Cloudflare sits in front of roughly a fifth of the web, so it's positioned to meter that traffic and charge for it. Whoever wins the AI race still has to pay to read the web.

  • aaronware
    Aaron Ware (@aaronware) reported

    @Cloudflare is there an official way to setup up an account for someone and transfer it? Have some non technical clients that we want to help get setup w/ their own accounts. Can't make accounts from existing emails, trying to have less friction to help small biz/orgs onboard

  • ruchitdalwadi
    Ruchit Dalwadi (@ruchitdalwadi) reported

    @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.

  • jaybfly
    JB (@jaybfly) reported

    4/Here's what just happened: Cloudflare, which routes about a fifth of all internet traffic, launched something called the Monetization Gateway on July 1, 2026. It lets any website charge AI agents per request. Not per month. Per single question answered. 5/Think of it like a tiny M-Pesa till sitting in front of your website or API. An AI agent knocks. The till says "that'll be $0.001." The AI pays instantly. The door opens. No account, no login, no invoice — just pay and go.

  • tando_me
    Tando (@tando_me) reported

    @fridgebuzz_art @Cloudflare I want slow fiat even less than I want fast fiat.

  • yu_hoo2
    Yu⚡️ (@yu_hoo2) reported

    @EliteSlayer_12 Getting errors related to cloudflare. It's honestly frustrating

  • prutadigital
    Mike Pruta | AI employees (@prutadigital) reported

    @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.

  • alphaticaio
    Alphatica (@alphaticaio) reported

    LARGE / MID-CAP TAPE | July 8, 2026 Large / mid-cap blocks. +$214M net buy. Flipped. Yesterday: -$726M. $AKAM +$88M zero sells. $NET +$65M. $CRWV +$62M. Yesterday's sellers became today's buyers. Q3 week two. $1.61B in buy blocks. $1.39B in sells. Net: +$214M. 2,437 prints. Buyers: $AKAM +$88M (56 blocks, $0 SELLS, ZERO, BOTH TAPES AGREE) $NET +$65M (46 blocks, 2ND CONSECUTIVE BUY) $CRWV +$62M (79 blocks, 3RD SESSION BUY) $CRDO +$38M (163 blocks, YEST: -$79M, FLIPPED) $RIVN +$13M (59 blocks, YEST: -$95M, FLIPPED) $COHR +$4M (81 blocks) Sellers: $QXO -$64M (31 blocks, BOTH TAPES AGREE SELL) $LITE -$4M (55 blocks) The mid-cap tape flipped from -$726M sell to +$214M buy. Same reversal as the mega-cap tape (+$13.37B). The institutions bought the sell day across both universes. $AKAM: +$88M. Zero sell blocks. Both tapes agree buy. Yesterday $AKAM was a dark pool seller at -$26M. Today: zero sells on the lit tape, +$33M in the dark pool. The reversal is complete. $CRDO: -$79M yesterday, +$38M today. $RIVN: -$95M yesterday, +$13M today. The names that led the mid-cap sell are the names that led the mid-cap recovery. The first cross-session reversal signal the mid-cap panel has produced. Three days old and already showing reversal patterns. $NET: +$65M. Second consecutive buy session. Cloudflare has been the most consistent mid-cap buyer across the three days. The mid-cap panel mirrors the mega-cap panel. Both flipped. Both bought the sell. The data is consistent across universes. Watching the tape.

  • HierB4TheAC
    Quis ut Deus? (@HierB4TheAC) reported

    @Dimi7ri @realsedepicante A pen name on the internet is irrelevant. Even if you use a VPN youre not anonymous. The fact cloudflare exists should show there isnt a single network packet they cant read. They know everything everyone does on the internet.

  • flowerpower732
    chr (@flowerpower732) reported

    @levelsio @Cloudflare yeah I got the same issue. got fallback set on AWS SES.

  • Bryce58831457
    Bryce (@Bryce58831457) reported

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

  • WayneShirreffs
    Wayne Shirreffs (@WayneShirreffs) reported

    @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.

  • alphaticaio
    Alphatica (@alphaticaio) reported

    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.

  • Lord_of_Candy
    Lord of Candy | Kaeos (@Lord_of_Candy) reported

    "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.

  • HaythamChhilif
    Haytham Chhilif (@HaythamChhilif) reported

    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.

  • cybnexlabs
    Cybnex Labs (@cybnexlabs) reported

    Bots now make up more of the internet than people do. On June 3, 2026, Cloudflare's CEO Matthew Prince announced that automated traffic had passed human traffic online for the first time — roughly 57.5% machine to 42.5% human. He had predicted the crossover would land in late 2027. His words on the timing: "Welp, that happened faster than I predicted." That number is why your VPN keeps getting hit with CAPTCHAs. The version circulating on forums: AI companies hide their scrapers behind VPNs to steal content, so websites block VPNs to stop them. It's wrong, and believing it points you toward the wrong fixes. The major AI crawlers don't hide. GPTBot, ClaudeBot, and Googlebot announce themselves in their user-agent strings. That's the entire reason publishers can block them by name. The collision happens at the network address instead. Commercial VPNs and scraping infrastructure rent from the same datacenters. To a security engine scoring your connection, a Mullvad exit node and a scraping proxy look alike. Neither resembles home broadband in Ohio. That's the crossfire — architectural overlap, not deception. A block is rarely one thing. It's a score assembled from six layers — address type, address reputation, request rhythm, browser fingerprint, session coherence, geographic consistency. Reputation on a shared exit node is collective. Hundreds of people leave a website through the same address you do. If enough trip security systems, that address turns hot, and everyone behind it inherits the consequences. You did nothing. The address remembers anyway. Which is why fixing the address alone doesn't always clear the block. It's one input among six. Why the defenses tightened: Prince describes the asymmetry this way — a person shopping for a camera visits five websites. An agent doing it for them visits five thousand. That's real server load and none of the ad revenue the old crawl-for-referrals bargain assumed. Cloudflare's data shows over half of AI crawler traffic is spent re-fetching pages that never changed. On July 1, 2026, Cloudflare split automated traffic into three declared categories: Search, Agent, and Training. Starting September 15, new domains will have Training and Agent crawlers blocked by default on ad-displaying pages. Search stays allowed. Read that carefully. The block targets declared crawler categories. Not VPN users. But it signals the industry's posture: default-suspicious, verify-before-serve. Every operator running bot management is tuning tighter than two years ago, and tighter tuning means more borderline connections get challenged. Yours is borderline. What actually works, without disconnecting: Switch servers once, to somewhere nearby and less crowded. Congested exit nodes accumulate bad reputation faster. Stop hopping. This is the one people get wrong when frustrated. Cycling through a dozen servers in two minutes produces a session where your apparent location changes repeatedly. No person does that. Automation does. You're feeding the system the exact evidence it uses against you. Clear cookies for the site challenging you — stale session data tied to your previous address contradicts your current one. Stay logged in where you trust the site. An authenticated session with history reads as a returning person. An anonymous datacenter connection reads as an unknown. Use an ordinary browser build. Heavy fingerprint modification is meant to make you unremarkable. Done badly, it makes you unique — the opposite. On dedicated IP addresses: Some providers sell an address that belongs only to you. It reliably cuts challenges on banking portals and work systems, because no stranger's behavior contaminates it. The trade-off gets skipped in most write-ups recommending them. A shared address gives you cover precisely because hundreds of people leave through it. Reserve one to yourself and you've bought access by spending anonymity. Several strictly no-log providers don't offer them at all — a permanent address is a persistent identifier, which contradicts their entire design. Some blocks won't yield to any of this. A streaming service enforcing regional licensing isn't scoring your traffic at all. It knows exactly what you are and is contractually obligated to refuse. The friction isn't reversing either. As agents perform more of the browsing people used to do themselves, the systems separating human from machine grow more sensitive. What you're experiencing is closer to a floor than a ceiling. Your VPN puts you in that gap by design. It strips the residential fingerprint that would otherwise vouch for you — and that removal is the whole point of running it. So the goal was never invisibility. It's coherence. Give the system a signal that reads as one person, browsing at human speed, from a stable place, and most of the friction dissolves without ever touching the disconnect button. #CyberSecurity #AI — Cybnex Labs

  • memepilled
    Meme Pilled (@memepilled) reported

    @brave Even twitter keeps getting some poisoned cookies **** and throwing fcuc king constant cloudflare loops on brave that dont get fixed by doing anything other then nuking the browsers coolies

  • WayneShirreffs
    Wayne Shirreffs (@WayneShirreffs) reported

    @pranavsf @Cloudflare Never heard someone actively wishing to pay the 3% robbery fee to accept credit cards when we have a better system with essentially zero fees using stable coins.

  • MillsNotMiles
    Mills (@MillsNotMiles) reported

    @Kolar_Dev @softwareengng @EOEboh Yeah Cloudflare free tier doesn’t support this

  • codellyson
    codellyson (@codellyson) reported

    @Cloudflare social login is not working. thank you

  • BuildAfter40
    Build Wealth After 40 (@BuildAfter40) reported

    @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.

  • Zain_Wania
    Zain Wania (@Zain_Wania) reported

    @aarondfrancis I just tried it again a few hours later and no issues. Might be a cloudflare blip. Anyways, loving solo, but I noticed I can’t click Claude codes special little links for things, they presumably did a hacks thing that makes certain text look and work like hyperlinks and it’s a pretty nasty papercut I’m feeling my not being able to click on those.

  • CorvusCrypto
    Clifford Richardson (@CorvusCrypto) reported

    Rule 1 on @ycombinator's historically useful forum: Thou shalt not let someone apply nuance or call for positivity around another's developments Sorry jonluca, you have broken the rule and will now need to be erased from the universe by Garry and gang. Seriously, it's a problem and I wish it got more attention rather than let people encourage each other to be more and more cynical. Many are doing their part like this chap to call it out, but what I have hidden is just... depressing. Skepticism and critical feedback is great. Comments like "Cool, just 20 years too late." (a real comment on the cloudflare drop post) is not great.

  • inababi
    Salina Mendoza (@inababi) reported

    @Cloudflare @OpenAI Damn what a loss. What does this mean? I hope this doesn’t mean we all signed up to share our data with OAI. I will need to reevaluate my entire stack if so.

  • BrettN89441
    Brett N (@BrettN89441) reported

    @pcgs there have been more problems with your @Cloudflare nonsense and pages freezing, not loading, and just endless waiting for your system to keep up. This is only getting worse. Just sat here fo another 45 seconds waiting for a freaking page to load. This is unacceptable.

  • vbkotecha
    Vivek Kotecha (@vbkotecha) reported

    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.

  • FireFlyGG
    FireFly (@FireFlyGG) reported

    Cloudflare can make AI agents pay per request. Monetization Gateway lets sites bill AI agents for every fetch. > page > API > dataset > MCP tool Payments use protocol x402, based on the nearly forgotten HTTP 402 Payment Required. The agent receives an invoice, pays in stablecoins, and gets access instantly. All inside a normal HTTP request, no registration or payment pages. Cloudflare says one real user generates thousands of AI requests. This is an evolution of last year Pay Per Crawl, now able to force payment from practically any AI service, not just crawlers.

  • Carlo_Buonpane
    Carlo Buonpane (@Carlo_Buonpane) reported

    @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.

  • eoslick
    Evan Oslick (@eoslick) reported

    @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.

  • KayhanB21
    Kayhan (@KayhanB21) reported

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