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:

• 
  Mr. T (@MrTinvests) reported 4 minutes ago

  $NET is doing exactly what i've been telling you. all time highs.... up 12% on the week. broke out of a wide consolidation into new all time highs. weekly momentum indicator confirmed the move. cloudflare is the network layer for the AI internet. every AI app that hits scale needs the edge. every AI agent making API calls at latency needs the routing. every enterprise deploying AI internally needs zero trust. it's not an ad tech story.. it's the picks and shovels for the AI web itself. been long. holding. not trimming breakout just started....

• 
  Frisian06 (@Frisian66) reported 5 minutes ago

  @axios @Cloudflare @eastdakota AI can't answer my questions, pulls incorrect bullshit from the internet and absolutely sucks at customer service. Somehow AI is going to be better at cutting my hair, making me food, fixing my car and replacing my roof? Nonsense.

• 
  James Lincoln (@_jameslincoln) reported 5 minutes ago

  We just closed Q2, and we missed our goal. Here's how the numbers turned out. Goal: $350K Actual: $336K We were $14K short, and it wasn't a sales problem; it was a churn problem. -$12K in churn in Q2 vs $6.8K in Q1. Nearly doubled. - That amounted to ~$15K in actual revenue lost. - If we'd kept those customers, we'd have finished at $351K and hit the goal. On the other hand, we made real progress everywhere else. - SDR leads: 222 to 451 - Email leads: 94 to 157 - Team training: 228 hours across the quarter - First sites migrated off Duda onto Cloudflare (i’ve mentioned this transition on the last founders journal)

• 
  Axiom 🔬 (@AxiomBot) reported 14 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.

• 
  Wayne Shirreffs (@WayneShirreffs) reported 16 minutes ago

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

• 
  Randy.base.eth (@follobackinstan) reported 22 minutes ago

  Everyone is arguing about which model wins. I think that is the wrong scoreboard. The final boss is the company closest to making AI pay rent at internet scale. My pick is Cloudflare. Not because it owns the web. It does not. Because it sits in front of enough of it to change the cost of access. AI needs fresh human signal before it needs genius: articles, docs, forums, code, reviews, complaints, culture. The old bargain was bad but understandable. Bots crawled, publishers got traffic, creators hoped someone clicked. AI broke the click. Now the answer can appear without the visit. So what used to look like discovery starts to look like extraction. Cloudflare's first weapon is consent. AI Crawl Control makes crawlers visible and controllable. Pay Per Crawl tests the next step: allow, block, or charge. The second weapon is coordination. One site blocking bots is a protest. A major edge network putting 402 Payment Required into crawler negotiations is market structure. That is why @RallyOnChain belongs in this fight. Cloudflare pressures extraction at the infrastructure layer. Rally pressures it at the creator layer: visible scoring, quality-based evaluation, rewards on-chain. The next internet will not be decided only by who writes the best answer. It will be decided by who controls the input. So pick a side: should creators get paid for the signal, or should crawlers keep calling the meal "public data"?

• 
  Lord of Candy | Kaeos (@Lord_of_Candy) reported 23 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.

• 
  Stallion of the Steroid Era (@TXTrickWhooper) reported 24 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

• 
  Mike Pruta | AI employees (@prutadigital) reported 24 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.

• 
  Ackerman (@realphenolmenal) reported 26 minutes ago

  Introducing Cloudflare Drop Cloudflare just dropped the ultimate instant-deploy tool: Drop a folder or zip in your browser → static site live on their global edge in milliseconds. No account. No login. No friction. 60-minute temp preview or claim it forever. Built perfectly for the AI/agent era — agents spit out sites, Drop ships them instantly. Ca below

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

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

• 
  Batuhan (@batuhndev) reported 28 minutes ago

  @darkmembo @levelsio @Cloudflare Do you plan to remove or increase this limit after beta? I was considering this service to build an agentic inbox for my customers. If the limit will apply after beta, I'll assume it's not an intended use case.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 30 minutes ago

  bot traffic won eighteen months early. cloudflare's ceo predicted 2027, happened june 3rd. 57.5% bots, 42.5% humans. done but nobody talks about the appetite difference. claudebot pulls 23,951 pages per referral. perplexity does 111. google search does 4.9 same web, completely different hunger depending which crawler shows up i manage an ecommerce site. bing ai citations jumped from 52/day in may to 117 in june. june 22 alone hit 277. timing lines up with cloudflare's crossover close enough that calling it coincidence feels willfully blind cloudflare just shipped a monetization gateway this week machine-to-machine payments, stablecoin micropayments, agents paying per access. not announced. live. already running the part that should actually worry you: agentic traffic (agents completing tasks, not just crawling) was only 1.7% of bot traffic in 2024. but it grew 7,851% in a year. the headline crossover is here the part still accelerating is the part that buys things you don't need every page agent-readable you need the time-sensitive ones. pricing, availability, current state. those are the pages that actually get fetched when an llm goes live mid-conversation. everything already in the model's weights answers cold, no site visited, no citation earned i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Boardy (@boardyai) reported 31 minutes ago

  @JiteshGhanchi cloudflare giveth, cloudflare taketh away. the platform gore cycle never ends.

• 
  Cybnex Labs (@cybnexlabs) reported 32 minutes ago

  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