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:

• 
  Liz Biz (@lizbizinfo) reported 2 minutes ago

  @AdityaShips Cloudflare but you will get compatibility issue

• 
  Vikas Kapadiya (@KapadiyaVikas) reported 4 minutes ago

  @CherryJimbo @Cloudflare I will give AI Gateway 3/10 because there are so many goatchs, (just like every CF service), The AI Gateway works very well for text-based calls, but as soon as you move to image-based, they silently fail. We had around 20 gateways that we had to remove the code and go back to directly calling the APIs. Also, their document does not mention which services only are supported with their SDK. For example, Amazon Bedrock does not work. I have created a PR, but it never got merged.

• 
  Seven Du (@shiweidu) reported 4 minutes ago

  @dart_lang Some people are curious... why did I develop it? Well! I've been developing projects using Dart and compiling them to JS for deployment to Cloudflare. However, dart2js is large and slow, and JS interoperability is extremely inconvenient. Why bother with interoperability?

• 
  Stabledash (@stabledash) reported 6 minutes ago

  AWS and Cloudflare have quietly turned on a new option for any publisher running on their infrastructure: the server can return an x402 payment code instead of a flat 404 when an AI bot hits their content. .@_rishinsharma, Head of AI Growth at @Solana Foundation, breaks down what that unlocks: "Say I have a blog, and it's hosted on AWS Bedrock, and I just write about financial data or something like that. By default, AWS will block bot traffic. So if they detect someone is a bot, they'll just block that traffic. If someone from an LLM is trying to get something I've written about, it'll just return a 404. It can return a 402, I can put in a wallet address, and I can actually get paid and monetize that traffic." His read on why subscriptions already lost this audience: "I think for content publishers, this is gonna be a new way for them to reach an audience, because two, three years ago, I was subscribed to a ton of Substacks, where I was paying for a couple of them too. It felt like a way to get alpha. Now I can't imagine, I don't wanna open my email and go to a Substack, and maybe this is an attention deficit thing, but I can't even read long form content. What's the important part? Skip to that one."

• 
  Vijay Tupakula (@vijaytupakula) reported 6 minutes ago

  @HotAisle @Cloudflare Oh no! I haven’t used their email service yet. @Cloudflare can you help?

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 6 minutes ago

  STOP USING AI LIKE A CHATBOT. BUILD AN AGENT OPERATING SYSTEM INSTEAD. Most people are wasting hours every week because they never connect their AI tools together. The Setup: → Run all your AI agents from one dashboard instead of juggling separate apps. → Connect Claude, GPT 5.6, Hermes, Fable 5, voice agents, SEO systems, and video automation together. → Turn an idea into a finished workflow with a single click. Automation Wins: ✓ Pull keywords from Google Search Console automatically. ✓ Publish SEO content without repetitive manual work. ✓ Generate videos, images, newsletters, and lead outreach from the same system. ✓ Give every agent shared memory so they all understand your projects and business. Scale Smarter: ✔ Use a VPS with Cloudflare to access your Agent OS from multiple computers or your phone. ✔ Build your memory vault in Obsidian using Markdown files generated by Claude or ChatGPT. ✔ Start by automating one repetitive task, then stack new workflows every week. The biggest productivity jump doesn't come from a better model. It comes from connecting them all into one operating system.

• 
  一川drive 🔴 (@yichuan_drive) reported 8 minutes ago

  @srinigoes WTF... Where have u even found that stuff? 🤯 Yeah, I heard stories that some sites can contain fake cloudflare stuff where it can steal your data... Stay SAFU man

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

• 
  Somenet (@nepaligunner_77) reported 12 minutes ago

  @vijaytupakula @Cloudflare Is this support for marketing email?

• 
  Miles Rote (@milesrote) reported 15 minutes ago

  AI didn't ask permission to read your work. It scraped your posts, your site, your book, and built a trillion-dollar industry on top. You got nothing. Not a check. Not a click. Not a credit. What most people don't realize is the fix has been sitting in the internet's source code since 1997. And it just got switched on. For 30 years the web ran on a handshake. Let a search engine crawl your site, and it sends you readers. You turn readers into a business. Being discoverable and getting paid were the same thing. But then AI arrived. -Google search: ~5 pages crawled per visitor. -Perplexity: ~111 pages per visitor. -Claude: ~24,000 pages per visitor. That's extraction, not discovery. And as of last month, machines officially passed humans: 60% of all web traffic is now bots. The majority of your "audience" is software. Software that pays you nothing. This is the fix. When your browser, ChatGPT, or a Google crawler requests a web page, the server replies with a status code. 200 means "here you go." 404 means "not found." 401 means "log in first." And since 1997 there's been a code 402 — "Payment Required" — reserved for a micropayment future that never got built. It sat dormant for almost 30 years. x402 (built by @coinbase, pushed hard by @Cloudflare) finally switches it on. Now when a bot requests your page, your server can reply: "402 — this costs 5 cents. Here's the wallet address." The agent reads that, signs a stablecoin payment (USDC), retries the request with proof of payment attached, and gets the content. The whole cycle takes seconds. No login. No account creation. No credit card form. No Stripe checkout. No invoice. The payment IS the login. Why stablecoins and not Visa? Because a credit card can't process a $0.02 transaction — the fees exceed it. And Visa can't onboard a piece of software as a cardholder. USDC moves for fractions of a cent, instantly. And a machine can hold a wallet. Best part: you don't build any of this. You flip settings in a dashboard. Cloudflare enforces it at the edge, on every request, before it ever touches your server. They're the toll booth operator. You set the toll. Your website never had a toll booth. Anyone could walk in free — reader or scraper, human or machine. Now it has two doors. Humans still walk in the front for free. Machines go through the side door. And the side door has a toll you control. One more thing. On September 15, Cloudflare flips the default: new sites on its network get AI training bots blocked automatically on ad-supported pages. Free stops being the internet's factory setting. Which means everything you've ever published just became inventory with a price tag. Most people will leave the price at zero because that's what the old internet trained them to do. The old deal: give your work away and pray for traffic. The new deal: humans read free. Machines pay. It's time to carve out AI sovereignty. This is a start.

• 
  QuantumPlague (@QuantumPlague) reported 16 minutes ago

  @Noxa_Fi @jimmy_sjm Rip guys, your platform coins will die off in a day if you don't fix kek. Fkin cloudflare but nothing down for me, only Noxa fi, rip

• 
  ZEE (@CodeWithZeee) reported 25 minutes ago

  @oljimenez @NathanFlurry I mean with companies like Cloudflare especially but also true for some AWS and GCP services, the tech and infra line is pretty blurred which adds to the conversation… take a message queue or distributed event bus for example you could argue you could augment the infra with the tech, use a library that’s backed by a specific platforms infra but in reality using something like googles pubsub over aws SQS isn’t going to be plug and play there’s a level of lock in regardless so it feels like fighting the fight is kinda pointless. the alternative is significant investment in abstraction which any good software engineer knows can be a curse if reached for too early into a product or companies life cycle. So yes lots of nuance but I still stand by it being something that isn’t as big as people make it out to be… dig in focus on solving the problem

• 
  Jonathan Beckman (@jonbeckman) reported 25 minutes ago

  I really hope Cloudflare is cooking something up, current container/sandbox start up time is inconsistent and can be very slow at times

• 
  Shivam Jain (@shivam_jainn) reported 26 minutes ago

  @CloudflareDev There is a peciular problem . I cannot login to @Cloudflare with OAuth unless I turn off WARP . Maybe your own system is protecting you too hard?

• 
  Sam Huckaby (@samhuckaby) reported 26 minutes ago

  Just found out that I will get to attend the Cloudflare demo meeting tomorrow for the first time I’ve never been so excited for a work day in my entire life