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:

• 
  Jack Cooldev (@jackcooldev) reported 1 minute ago

  Agent memory has become one of the most crowded corners of AI infrastructure - Cloudflare, open-source projects, and startups have all shipped memory products this year. A launch from last week stands out anyway, because it competes on a different axis: not how much the agent remembers, but whether you can prove and govern what it remembers. AgentPrizm released its AgentMemory platform on July 9, a REST API with MCP support that gives agents persistent memory across sessions, working with Claude Code, Cursor, and any MCP-capable agent. Persistence alone wouldn't be news in this field. What separates this one is the governance layer: every memory carries a confidence score and a validity window, contradictions between old and new facts are handled explicitly, and audit receipts can trace each memory decision back for the user, with right-to-forget controls built in. That design answers the question enterprises actually ask before deployment, which is not "can the agent remember?" but "can I prove what it remembered, and delete what it shouldn't?" Teams in legal, support, and sales automation have been answering that with internal tooling or by not deploying at all.

• 
  Abhi Bavishi (@abhibavishi) reported 5 minutes ago

  I moved Smartify off WordPress last month. Honestly, the trigger was embarrassingly simple. Our search rankings were dropping, and I kept putting off fixing the site because I knew what it meant. Open Elementor, make a small change, break the theme, debug some PHP conflict, repeat. It was hell every single time. So I just... didn't. And the site kept suffering. Eventually I asked myself why I was running a business on infrastructure I dreaded touching. So I migrated to Astro + Cloudflare Pages using Claude Code. The entire site is now pre-built at deploy time. Every page is a static HTML file served from Cloudflare's edge network. No server. No CMS login. No PHP. No database queries on page load. No plugins to update. No attack surface. Hosting costs went to zero. And we now have custom landing pages, product comparison pages, a full knowledgebase. Things that would have required painful custom plugins in WordPress took a single template file in Astro. I'll be honest though. The migration wasn't a clean win from day one. Google was only indexing about 33% of the pages initially. Fast static files aren't enough if the content is thin. We had to go back and actually make pages worth indexing. WordPress made sense in 2008. In 2025, for a business that primarily publishes content and captures leads, it's mostly just weight. Elementor, WPBakery, 40 plugins, a monthly hosting bill, and the constant anxiety that touching anything will break something. I was holding on to it because migrating felt hard. But I was paying for that laziness in rankings every single month.

• 
  Dharmesh Dev (@DharmeshDev) reported 6 minutes ago

  Ran two branches at once today on the AI consultancy business. One track building the website, the other working on the business foundation. Parallel execution instead of sequential — felt like the right call given how much ground both need to cover. Started the website with Codex using Code planning mode to map the build out first. Then implemented the plan and got a working vibe coding prototype up. Version-01 is live and looks solid, though it still needs iterative improvement. A significant chunk is done. Also ran the same website workflow through Claude Cowork and Claude Code specifically to test the Fable-5 model. The output wasn't as impressive as expected — though the problem statement probably wasn't the best test case either. One thing Fable-5 did nail: it suggested a single-page static design with React and Next.js compiled, hosted free on Cloudflare instead of paying for hosting. That's a genuinely useful architectural call worth keeping. On the business side, Claude on Opus 4.6 with medium setting helped identify the 4 key pointers needed to launch the consultancy. Starting with the "Foundational Layer" setup — that's the next piece alongside continuing the website design.

• 
  Vatta (@forkvat) reported 8 minutes ago

  @lenondenonn I FOLLOWD FINALLY IT LET ME WHEN THE CLOUDFLARE THING NEVER LET ME 🥹

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

• 
  Anselme (@theMissionBoy) reported 8 minutes ago

  @mattzcarey i don't disagree; in this case it's a skill issue but data loss is a distraction here cc @ashleybchae the actual infra gap is that his "agent expanded $HOME command" incorrectly and that there was nothing to catch that "semantic" error before the command's execution (or that the error was allowed to happen in the first place) i don't think sandboxing solves that, and agents still make such correctness error regardless of the end user's skill that's what i call "correctness layer" and that's what i am attempting to build (i have something in alpha phase and will be open source) but otherwise you and the folks are Cloudflare are doing great work

• 
  Trevor Hudson (@trevhud) reported 10 minutes ago

  With cloudflare tenant separation (one D1 per customer for example) you could just start giving read access to your customers which would go a long way for trust and integrations.

• 
  Ξric Juta (@ericjuta) reported 10 minutes ago

  @whoiskatrin @OpenAI tl;dr - everyone's got faster independent connections with deltas but are paying more due to caching algo + incremental delta metering not being as efficient then eventually get throttled on the connections limit level by cloudflare anyways causing slower convos overtime lol multi agent v2 doesn't help on that front either

• 
  Mian Shahzad Raza (@MSR_Builds) reported 12 minutes ago

  @fulligin lol 'no problem' while your brain is doing CDN vs DB vs 'wait is cloudflare down again' triage in real time 💀 the real flex is sounding calm on the phone while frantically alt-tabbing

• 
  komm64 (@komm64) reported 12 minutes ago

  @Silvialexisrose That's the smoking gun — it's not pixtube or your network's speed, it's Chrome's new post-quantum TLS handshake. Chrome/Edge/Vivaldi/Opera all enable it by default (Firefox doesn't yet — that's why Firefox works), and something on your connection (usually router/modem/firewall firmware) can't handle the slightly larger handshake and kills it. Your phone works because it takes a different path. Quick fix in your Chromium browsers: 1. Go to chrome://flags (or edge://flags, vivaldi://flags, etc.) 2. Search "post-quantum" (also try "kyber" or "ML-KEM") 3. Set the matching flag to Disabled, restart the browser. That should make them all work. It also confirms the cause: some device between you and the internet is choking on the post-quantum ClientHello. Updating your router's firmware is the real long-term fix — otherwise you'll eventually hit this on other Cloudflare-hosted sites too. Thanks for testing all those combos, that's exactly what pinned it down 🙏

• 
  Piyush Chandwani (@piyushxcreates) reported 23 minutes ago

  @AdityaShips I'm running 3 next.js apps for a client on a $10 vps with 8gb ram and 150gb SSD with coolify with cloudflare tunnel for max security and have faced no issues till now no matter how much th traffic

• 
  Duyet (@_duyet) reported 26 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)

• 
  Anurag Goel (@anuraggoel) reported 26 minutes ago

  @Shpigford @Cloudflare It's surprising how often they go down for a public company.

• 
  Anti Lying (@aimtomisb3hav3) reported 29 minutes ago

  @Support X just put me through a Cloudflare anti-bot verification. I'm a verified account. I PAY YOU monthly. Please stop being lousy.

• 
  Zatkobratko (@Zatkobrat) reported 30 minutes ago

  Bizarre is perhaps not the word I used since it's only been a day. I do not agree with them disabling it and fixing vamp is perhaps not good. Since the first dever can be an idiot, but apperantly they got attacks on their site on cloudflare. So it seems that they are right now not only fixing vamp, but also their website and transferring it to another decentralized hosting server. Might take a few more days tbh