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:

• 
  Indranil Tiwary (@indraniltiwary) reported 4 minutes ago

  @AdityaShips VPS from Hetzner - with Coolify/Dokploy - Dokploy if you want a better UI/UX and alternatively you can think cloudflare but you just mentioned compatibility issues, so I am guessing that isn't working for you. - Hetzner VPS + Dokploy

• 
  Naoris Protocol (@NaorisProtocol) reported 5 minutes ago

  @mariozz_13_ @Cloudflare Cloudflare protects traffic in transit at the edge. It doesn't touch what's already signed and sitting permanently on a blockchain, that's a different problem entirely

• 
  DegenCalls (@Degen_calls_sol) reported 6 minutes ago

  GITHUB REPOS YOU SHOULD KNOW ABOUT Most scrapers break for boring reasons. A button moves, a class name changes, Cloudflare gets in the way, or the crawler dies halfway through a long run. Scrapling turns scraping into a more resilient system. Scrapy-style spiders, concurrent crawlers, pause and resume, anti-bot handling, and adaptive element finding in one framework. The detail most people miss: the adaptive selectors are the real unlock. Instead of hard-coding brittle CSS paths and praying the site never changes, the scraper can relocate elements after redesigns. That matters when you are scraping production targets, not toy pages. This is the shift from scripts to infrastructure. A script extracts data once. A scraping framework keeps extracting when the website changes, slows down, blocks, or moves the target. Most people still build scrapers like one-off hacks. The better setup is a crawler that expects failure and keeps going anyway.

• 
  Brais Calvo (@braiscv) reported 9 minutes ago

  @antonosika On Cloudflare, mainly for Zero Trust. And honestly, the switch to token based billing for the Cloud features has been pretty terrible. Another reason for hosting it externally is to have more control and transparency over the stack.

• 
  WOLF Crypto (@WOLF_Crypto_X) reported 16 minutes ago

  CLOUDFLARE JUST BUILT A WAY FOR AI AGENTS TO PAY FOR CONTENT ON THEIR OWN, STARTING WITH STABLECOINS It targets a problem that's quietly breaking the web's business model. Here's the idea: For 30 years the web ran on one trade: content in exchange for human attention. You read, you see ads, you maybe subscribe. An AI agent does none of that. It reads a page, takes what it needs, and moves on. No ads, no subscription. And they're voracious. Cloudflare says AI crawlers already pull content anywhere from a hundred to tens of thousands of times for every visitor they send back. Cloudflare's answer is a "Monetization Gateway." Site owners set which content costs money and how much. When an agent requests it, payment clears, then access opens. The payment layer, at least to start: Stablecoins, settling in under a second at negligible fees, running on Coinbase's open x402 payment protocol. The bigger picture: This is one of the first real attempts to price the machine-to-machine web, where software pays software per request, and stablecoins are the rails it runs on.

• 
  Cyber_Racheal (@CyberRacheal) reported 16 minutes ago

  This is infact entirely true. A Department of Justice court filing confirmed that employees from the Department of Government Efficiency (DOGE) moved a massive dataset to an unauthorized location. Under the direction of agency tech leadership, a live copy of the Numerical Identification System (NUMIDENT) database was uploaded to a custom cloud server. This database contains the sensitive personal information, birth details, and Social Security numbers of more than 300 million Americans. The agency’s internal security teams explicitly flagged the action as "high-risk" with a potential for "catastrophic impact". The situation grew worse when officials admitted that data was improperly shared through an unapproved, third-party server network hosted by Cloudflare. A federal whistleblower, agency Chief Data Officer Charles Borges, revealed that the data transfer bypasses independent security monitoring and auditing protocols. Government lawyers acknowledged that the Social Security Administration cannot fully account for the data. They currently lack the access needed to verify who viewed the files, what exact information was shared, or if the records still exist on the outside server.

• 
  Aakash Reddy (@rayyyyyofsun) reported 19 minutes ago

  @CherryJimbo @Cloudflare The renaming and wanting to merge into workers phase and support during that duration was bad

• 
  Duyet (@_duyet) reported 21 minutes ago

  @born2code @CFchangelog No, Cloudflare Tunnel is not gone. The service (including Cloudflare Tunnel for SASE and Cloudflare Mesh) continues to operate normally. Only two specific legacy API elements are being retired on October 5, 2026: • CIDR-encoded route endpoints in the Zero Trust Networks API (replaced by modern route_id-based endpoints). • The connections field in tunnel list/get responses (you must now use dedicated per-tunnel connections endpoints instead). These changes make API responses smaller/faster and bring consistency to how resources are identified. (By Grok)

• 
  ℭ𝔬𝔳𝔢 (@ekojoecovenant) reported 21 minutes ago

  Spent the day migrating my PR review agent off waitUntil() and onto Cloudflare Queues. Turns out waitUntil() has a silent 30-second ceiling. Learned that the hard way when longer PR reviews just... stopped mid-analysis. Queues fix it properly instead of me hacking around a timeout.

• 
  Chibugo | AI automation (@__chibugo) reported 21 minutes ago

  there's a trend on instagram right now: everyone's building their own version of Tony Stark's Jarvis; a voice agent that runs like an actual OS. what nobody shows is everything people overlook when building one. so here's that part, since I built it myself. 🎯 the plan on paper vs. the plan that shipped the amount of planning you need to do is insaneee. first version had each agent loading one tool, fetching, verifying, then unloading before the next; all built around not blowing past a token budget. that's the part people underestimate: you don't know your constraints until it's running. once it was live, token budget stopped mattering. speed and cost-per-call did. so the whole approach changed: instead of mcp's, every agent just calls its tool's API directly, does the work in plain code, and only asks the AI to write the sentence at the end. 🎯 scope one AI that "does everything" sounds impressive but could be a nightmare to debug. so i split it into 5 sub-agents, each only knowing its own lane. a router decides which lane(s) a question touches. these sub-agents then report to the main agent orchestrator. similar to a team lead and team members 🎯 prompt chaining integrated ElevenLabs for voice, and a single voice reply isn't one AI call; it's a handoff, several times over: hear the words → figure out what's being asked → pull the data → write the sentence → speak it. every handoff adds seconds and cost, which can lead to latency. one reply once took 31 seconds. pulled the logs instead of guessing: a wasted double-check on an expired token, a slow handoff to an outside service, plus the normal chain. fix is running sub-agents in parallel and timing each call. 🎯 tokens and prompt caching each agent's instructions get cached, so it's not re-reading the same manual on every call. what never gets cached is live data; for instance, caching a bank balance is just caching a wrong number the moment it changes. that same cost-awareness came back around differently later: the AI account ran out of credit for a few hours, and every request failed with the same error. 🎯 local vs. web everything gets tested on a local copy first; headless browser opening the dashboard, checking for errors, a test message round-tripping through voice before go-live. if you're handing this to someone else, though, you commit, push to GitHub, and host it. for mine, i used Cloud Run for the brain, Cloudflare Pages for the screen. 🎯 vault write-back most builds only go one direction: ask, answer, forget. this one writes back because every full briefing gets saved as a dated file into a notes vault so the agents can keep training themselves with the data. if you ask a follow-up an hour later and it still knows, because that memory is shared across every way you talk to it. used Obsidian, synced through Drive. 🎯 security once, a message could've gone somewhere it shouldn't have. that only needs to happen once to be a problem. so now there are three checks before anything goes out: - it can never post to certain places, - it has to prove who it's speaking as before it speaks for someone, - and tests confirm both of those actually work. separate from that, I went through every access key this thing has and asked, "does it really need this much access?" a few did not. 🎯 the checks after every update, it runs a test and asks does a voice message go through? does it understand a normal sentence? does the screen load with no errors? also implemented something we call "error logging" in automation, but i call this "diagnostics" or "agent health status," which checks in every 15 minutes on its own, making sure the data is still updating. if it's not, it sends a warning without anyone needing to notice first.

• 
  Sandip Dev (@devsandip) reported 23 minutes ago

  holy **** @Glassdoor and @indeed all i wanted was to read a few interview questions for a particular company on glassdoor. now i have spent the last 10 minutes, filling 2 otp, 5 cloudflare capthas, yes/ok/continue on like 2 dozen screens and you still want more info. **** you

• 
  Chubby♨️ (@kimmonismus) reported 23 minutes ago

  Every Sunday we publish an exclusive interview in the Superintelligence newsletter. The last few: - Ahmed Awadallah, Partner Research Manager at Microsoft Research AI Frontiers, on small on-device agents that go toe to toe with the giants. - Phil Gurbacki, VP of Product for Weights & Biases at CoreWeave, on a research agent that reads your experiments and launches the next training run itself. Akshay Kothari, Co-Founder and COO of Notion, on a million custom agents. - Coming up: Cloudflare, Google Cloud, and several more I can't announce yet. - The part I still find hard to believe is that I get to sit down with the people actually building this. Every week, someone new. Subscribe for free down below:

• 
  Hyper (@HyperbooleanHB) reported 29 minutes ago

  @cremieuxrecueil I hate having to click a cloudflare box to visit a site. Something has to be done to maintain usability. Overuse of JavaScript was bad enough

• 
  Tzahi (@Tzahi458001) reported 29 minutes ago

  @BraydenWilmoth @irvinebroque i'm trying to upgrade my cloudflare plan and it keeps failing. i can't deploy my app without cloudflare. this is extremely critical. i urgently need someone to help me with this.

• 
  J7K (@J7K_dev) reported 34 minutes ago

  @TheThomHart damn 26 domains, i thought i was doing bad with my 20. youre giving cloudflare a run for their money here ha