Cloudflare 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:

• 
  Zero Trust Web 🔴💊 (@zerotrustweb) reported 1 minute ago

  Then Windscribe pulled the page source. Every visitor is being sorted into a variant, and the test is labeled in plain text inside an HTML meta tag: ab-test:VpnHpAndPricingVpnPlusSensibility300726. One session returns content=A, the other returns content=B. Two separate pricing URLs, one normal and one flagged test-300726-b. A screen recording shows the price flipping between clean incognito sessions, \.49 at 65% off, then \.99 at 70% off. Expired sales don't do that. Cached pages don't do that. Cloudflare has never once injected a named A/B test into anyone's markup.

• 
  AI Guides (@free_ai_guides) reported 2 minutes ago

  Cloudflare Workers creator, Kenton Varda: "For the past 25 years of cloud architecture, we've been running in the wrong direction." One of the sharpest talks I've watched on where software is headed. 18 minutes of pure insight from the engineer who built Cloudflare Workers. Personal AI codegen means every user customizes their own apps, and the cloud we run today was never built for it. This is already happening, and you can't build for it on infrastructure designed for the opposite. Watch it, then read the guide on harness engineering below.

• 
  Chirag Kulkarni (@chiraggkulkarni) reported 2 minutes ago

  Cloudflare's new crawler settings could accidentally kill your Google indexing. Cloudflare is splitting crawlers into three buckets: Search. Agent. Training. The idea sounds simple: Block Training → keep your content out of AI training. Except there's a problem. Googlebot isn't just a “Search” crawler. Google uses the same Googlebot for search crawling and other purposes. It never needed separate bots for these jobs. So if Cloudflare's rules treat that bot as both Search and Training, blocking Training can end up blocking Googlebot too. That means you could be trying to keep your content away from AI training... …and accidentally keep Google away from your site. The instinct to block AI training isn't the problem. The problem is assuming Cloudflare's three-way split maps neatly onto how Google actually crawls the web. Cloudflare is rolling this out as the new default starting September 15. So before you flip that switch, check exactly what you're blocking.

• 
  Carl B (@CarlB_jr) reported 5 minutes ago

  Being in IT I'm constantly harassed to find use cases and implement AI for almost everything. We've found some use cases and several that just don't make sense. But I always tend to play with things at home to really see what things can do and learn without the guardrails put in place at work. Last night I decided to give they API keys to my network to an AI model and told it "I've got ubiquiti hardware, investigate hardware and software settings. Provide any suggested tweaks or fixes to harden my network and improve performance." It went through and found security holes I thought I'd fixed a long time ago, it found several ways to get better performance, etc.. I did a manual backup and told it to go for it before going to bed. This morning I woke up and found it'd made a total of 92 changes to my network, my NVR, my cameras, apparently finding my CloudFlare API key in a config file and then using that to create a CloudFlare Tunnel, closed off my open ports and killed off my Port Forwarding rules. Redid my firewall changing it from IP based to Zone based. Setting up a new VLAN (for a total of 4 now), moved things around to the new VLAN setup, creating documentation for me, an architectural design, security review, security design, network diagram. Then at the end rotated all of my API keys, uploaded them to Bitwarden (found it's way into that as well through a config file), and then purged the new keys from it's memory. OK, I'm sold for certain tasks. Also a little scared/surprised on how it went through and did so much with other services. That's what I get for telling it to just do everything without any approval from me (because I was going to bed).

• 
  Fagner Sales (@fagnersales25) reported 8 minutes ago

  @a_shimanski @Cloudflare I don't have much experience with Cloudflare but I honestly want to give it a shot. I've been locked into Vercel for quite a long (It's so easy to use and setup that I never bothered trying something else)

• 
  Thomas Chua (@SteadyCompound) reported 10 minutes ago

  Machine traffic > human traffic "...if the current trends continue, we think in 5 years, nonhuman traffic will be as much as 1,000x as much as human traffic. In other words, humans will be a rounding error on the Internet, not because human traffic goes down, but that’s just how fast we’re seeing nonhuman traffic grow.” — Cloudflare CEO Matt Prince

• 
  The Circuitry (@thecircuitry_) reported 13 minutes ago

  Cloudflare mitigated more than 800 network-layer DDoS attacks exceeding 1 Tbps in Q2, a fivefold increase from the prior quarter.

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 17 minutes ago

  What does an AI agent actually pay for? Clean data that is structured and easy to access. Cloudflare is building the access and payment layer right now. So it's still early, you have 6, 12, maybe 18 months. Start with building the manual version and sell it to humans today. Curate the data before the space gets hyper-competitive. Five questions that point you at an idea: - What decision is expensive? - What information is messy? - What changes often? - Who already pays for help? - What would an agent need to do the job better? The internet is shifting from pages humans visit to resources agents use.

• 
  @vibecodit (@vibecodit) reported 18 minutes ago

  There is a status code in HTTP that has been sitting unused since 1996. 402. Payment Required. Thirty years later, RFC 9110 still describes it in exactly one line: "reserved for future use." Nobody ever agreed on what it should mean. Cloudflare is now trying to make it mean something, and the reason is worth understanding even if you never touch it. THE BARGAIN THAT JUST BROKE The web ran on one trade for twenty-five years. You let crawlers read your site for free, and in exchange they sent you humans. You monetized the humans: ads, subscriptions, affiliate links, signups. AI agents keep the first half of that trade and drop the second. The agent reads your page, answers the user directly, and the human never arrives. You paid the server bill. You got nothing. So publishers started blocking AI wholesale, which is a rational move that ends with a much smaller web. Metered access is the only middle ground anyone has proposed: the agent can read the page, but it costs a fraction of a cent. WHAT ACTUALLY EXISTS TODAY This is where most coverage of this gets sloppy, so here is the honest state of it. Pay per crawl launched on 1 July 2025. It lets a site set one flat per-request price for AI crawlers. A crawler either sends payment intent and gets a 200, or gets a 402 back with the price in a header. Thirteen months later it is still in closed beta. The Monetization Gateway was announced on 1 July 2026, and it is the bigger idea: charge any caller for any resource behind Cloudflare. A page, a dataset, an API, an MCP tool call. It is waitlist only. Not general availability, not even beta. x402, the protocol underneath, is real and open. Important correction to what you will read elsewhere: Coinbase created it in May 2025, not Cloudflare. The x402 Foundation is now hosted by the Linux Foundation, went operational on 14 July 2026, and has 46 members including Cloudflare, Coinbase, Google, AWS, Visa, Mastercard, Stripe and Shopify. Bot identity is the part nobody talks about and it is the part that makes the rest possible. Web Bot Auth is built on RFC 9421, HTTP Message Signatures, a real standard since February 2024. Cryptographic signatures instead of user-agent strings, which anyone can fake. You cannot charge a bot you cannot identify. WHY CLOUDFLARE GETS TO TRY THIS Because they are not pitching a standard, they are plumbing adding a valve. More than 20% of the web sits behind their network, by their own July 2026 figure, and 36% of the most-visited sites. Revenue was $2.17B for FY2025, up 30%. When they decide a protocol is now the default, it applies to tens of millions of sites at once. They did exactly this before. Free universal HTTPS was not a standards-body victory, it was Cloudflare making the alternative embarrassing. THE HOLE IN THE STORY Here is the part that keeps this from being a sure thing, and you will not find it in the enthusiastic threads. Not one AI company has been publicly confirmed as paying. Cloudflare cites "more than 50 publisher-AI agreements since 2023" and names no counterparties. OpenAI is not an x402 Foundation member and its payments work is with Visa on its own protocol. Anthropic is not a member either, though it does publish Web Bot Auth signatures, which is identity, not payment. Google is a member, but its x402 work is agent-to-agent commerce, not compensation for crawled content. The supply side is built. The demand side has not shown up yet. That gap is the whole risk. WHAT THIS MEANS IF YOU BUILD THINGS Two moves, and they are not equally valuable right now. Metering your own stuff is the small one. You can expose data or functionality through a lightweight API or an MCP server and put a price on it. Do it, but do it to learn the stack and be positioned, not for the money. Nobody is paying yet, so passive per-request income is not a line item in 2026. Selling the transition is the real one. Almost no small business has heard of x402, MCP, or llms.txt. Making a business legible to agents, so an agent recommends it when a user asks, is a service you can sell today with skills you already have: fast building, data cleanup, marketing. That is the actual opportunity, and notice it does not depend on Cloudflare paying anybody. One correction while we are here, because these get conflated constantly: llms.txt has nothing to do with payment. It is a community convention Jeremy Howard proposed in September 2024, never standardized, no RFC. Useful for discovery. Not a toll gate. THE PART THAT IS ACTUALLY A VIBECODING LESSON This whole post started as an AI research answer, and that answer was wrong four times. It credited x402 to Cloudflare instead of Coinbase. It reported $2.5B revenue against $2.17B audited, quietly using a forward run rate as an achieved number. It implied OpenAI and Anthropic were integrating, when neither is a member. And it described a waitlist-only product as rolling out. Every single error pushed the same direction: this is further along than it is. The mechanism was explained correctly, the structure was clean, the tone was confident, and none of that told you anything about whether the numbers were real. That is the failure mode to internalize. A wrong answer does not look wrong. It looks like this post before someone checks it. Verify anything with a number in it before you repeat it. That habit is worth more than any prompt you will learn this year.

• 
  The Agentic Operator (@AgenticOperator) reported 18 minutes ago

  @nicklaunches nothing anywhere records the loss..... that's the whole problem. AI recommends your competitor, the buyer never visits your site, and your dashboard shows nothing. no click, no bounce, no trace. just revenue that vanished and you never knew. cloudflare giving you the scoreboard is huge but most brands haven't even checked their robots.txt yet lol.

• 
  Sebastian Buzdugan (@sebuzdugan) reported 21 minutes ago

  @Cloudflare watched fedramp high deployments drift out of compliance through customer configuration, certification is the baseline

• 
  heather (@latentforms) reported 22 minutes ago

  @synopsi @Cloudflare ui is still awful, but used to be 1000x worse

• 
  🦋 hyeseong.kim (@cometkim) reported 23 minutes ago

  @yusukebe Does Cloudflare support it?

• 
  James Hurst (@Zafaron11) reported 24 minutes ago

  @p_e_t_e_r_s_e_n I mean, couldn't the web just switch from Cloudflare to a different service? Or is it everywhere?

• 
  JohnnyB (@JonBroadbentt) reported 25 minutes ago

  @synopsi @Cloudflare That edge network though