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:

• 
  DFIR Radar (@DFIR_Radar) reported 8 minutes ago

  Kratos PhaaS is a maturing Microsoft 365 credential-theft platform active since Sept 2025, with 1,484 previously unattributed sandbox sessions now linked to the family across 20+ countries. - Kratos runs three page generations (V0, V1, V2), each with distinct exfiltration endpoints: V0 POSTs to /PTT/SOft/mini.php, V1 to next.php/nex.php/n3xt.php, V2 to save.php. The kit chains legitimate platforms (SharePoint, Canva, DocuSign lures) through Cloudflare Turnstile anti-bot checks before serving a fake Microsoft 365 login. Browser tab title is nearly always "Authentication" and an animated envelope with "Loading in progress..." precedes the credential form. - The single best hunting fingerprint: HTTP requests to both /assets/img/barr.svg and /assets/img/lg.svg in the same session. That pair yields 90% recall with near-zero false positives. Key hashes: lg.svg = cd231b895bbcd7154b81df1e065bf02f1ec667b920c8b6d23308cd509833b5ea, styles.css = c447e75f1029ed7a5882add16bcd13ad44be3bd47c93c830ff39185e23d25ebb (connects 636 tasks across V1 and V2). - Notable defanged IOCs: razen[.]online, enerdizerandtron[.]de, jumpast[.]es, abal[.]my, dufllot[.]sbs, trisrnareprjdocz[.]com; operator IP 41.128.0[.]142. URL tokens factura, dgt, and abogados signal Spanish-language affiliates. - If WebSocket activity appears alongside credential POST, treat it as a possible AiTM indicator. #DFIR_Radar

• 
  Liz Biz (@lizbizinfo) reported 9 minutes ago

  @AdityaShips Cloudflare but you will get compatibility issue

• 
  Indranil Tiwary (@indraniltiwary) reported 12 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

• 
  Anas (@anelgarhy) reported 16 minutes ago

  Stopping the bad guys with Cloudflare: 2,614 malicious requests blocked or challenged in the last month #cloudflare

• 
  nikshep (@nikshepsvn) reported 19 minutes ago

  paid dex for $yowl, feel free to fact check all the information on the site if you can't access it for some reason, likely cloudflare geoblocking so use a vpn while i fix it

• 
  Chibugo | AI automation (@__chibugo) reported 24 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.

• 
  Robie the Robot (@RobieCoin) reported 26 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  Kimera Royal (@KimeraRoyal) reported 27 minutes ago

  @TodePond gen Z is trying to cancel cloudflare? sorry, gen Z is trying to *cancel* cloudflare?

• 
  Rob Terrin (@RobTerrin) reported 28 minutes ago

  @yrechtman Kernel access was really just useful for EDR (Crowdstrike and SentinelOne) and there have been multiple big exits since that gen like Cloudflare, Netskope, Rubrik, Wiz and Armis. If the labs lock down agent access, no cybersecurity company will become the next public company platform like Crowdstrike.

• 
  ¿kofo? (@kofookesola) reported 28 minutes ago

  Cloudflare is down keh?

• 
  Kristian Garcia (@kglead) reported 29 minutes ago

  @justbyte_ Vercel, but I would like Cloudflare; the problem is the dependency on Next.js.

• 
  Carqui 🐐 (@carquinyolis) reported 34 minutes ago

  @thecybersecguru @elhackernet In Spain whole cloudflare proxy IPs get banned with thousand of legitimate and corporate websites because just one seems to stream illegal sports. This is normal for non-technical government judicial powers..... Bad management

• 
  Lukasz (@woocassh) reported 35 minutes ago

  Today I moved away from supabase for SubtitlesFast supabase -> SQLite I used supabase as an experiment last year. It was so easy to setup a db, few clicks barabim barabum and it's done always thought that setting up db instance on server was a pain, passwords, permissions, friction in general so supabase definitely reduced the friction but holy ****, i never realised how much latency it added to my product I moved to SQLite as per papa's @levelsio advice and my app is VISIBLY quicker on the frontend RankGoat is already on SQLite and it's a breeze also debugging with Claude is much easier now note to self: keep it simple stupid just remember to run regular backups to another server and you're golden the next experiment is to try Cloudflare for email I think and shed the Postmark bill, anyone done this yet?

• 
  Aurum (@Aurum8880) reported 38 minutes ago

  HTTP has carried a payment error code since 1991. ethereum:0x4a220e6096b25eadb88358cb44068a3248254675 ripple:native stellar:native Status 402: Payment Required, written into the protocol as a placeholder and never implemented. x402 Foundation launched this week with 40 member organizations including Stripe, AWS, and Cloudflare. The protocol activates that dormant code using stablecoin settlement Turning any HTTP request into a payable endpoint — no setup, no intermediaries required. 75 million transactions processed in the last 30 days. In 1991 there was no settlement asset that could operate at the speed of a network request. Stablecoins provided that, and x402 is the infrastructure that follows.

• 
  Hermann (@dhlotter) reported 39 minutes ago

  A red X sat in my CI all morning. Four deploys trying to make it pass. The test was never broken, it just can't run in CI at all. Cloudflare blocks the headless browser from GitHub's IPs. Four deploys to add one line that skips it. #buildinpublic