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:

• 
  Michael Bates 🇺🇸🇬🇧🇦🇺🇳🇿🇮🇪🇮🇱 (@BatesLine) reported 4 minutes ago

  DNS service can screen out bad actors by refusing to resolve the domain name. Check the comments for alternatives to Cloudflare

• 
  ticktechh (@sprki999) reported 5 minutes ago

  @OmegaNekoSimp @NoboKik Does cloudflare use PoW? Never noticed a temperature spike from those and the ryzen in my thinkpad likes to spike 15 degrees just from looking at it

• 
  🍄 DO NOT FOLLOW TIMO 😈 (@liltechnomancer) reported 11 minutes ago

  @thdxr Because you have process issues. If you didn't extensions would work on cloudflare.

• 
  Security Weekly Podcast Network (@SecWeekly) reported 11 minutes ago

  That CAPTCHA may not be protecting you. A click-fix attack can use a fake Cloudflare CAPTCHA to convince users to open PowerShell or Terminal and paste a command themselves. Once the command runs—especially with administrator privileges—the attack chain can begin. What should organizations block before social engineering gets a user to execute the attack for them? #Cybersecurity #PowerShell #SocialEngineering

• 
  David Haddad (@daveying99) reported 15 minutes ago

  @levelsio @Cloudflare Easy decision. Only thing I would like more is domain favoriting (considering buying) and more tld support (namecheap has more and godaddy much more)

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 15 minutes ago

  @Cloudflare Fix human verification

• 
  Dr. Owlo R.D. (@Drowlord101) reported 18 minutes ago

  @NOTfunnyparanR Lols. Claude never crashes out on me. I (perhaps anthropomorphize claude a bit and) get the impression it's frustrated with me sometimes, or frustrated with a task, or frustrated with constraints (like cloudflare, hosting provider, storage solution, data) and fights back a bit on changing the constraints. But it's always as respectful as a professional, and I try to be positive or professional with it, because I know there's no malign intention in the AI. I'm better with AI than people, because I know people will lie, intentionally subvert tasks, and then try and blame me for choices they made.

• 
  COLLINSEO (@alexcollinseo) reported 20 minutes ago

  Breaking news! Your site might start blocking AIs from September 15th.. And if you block them, you won't show up in AI answers. The good thing? It takes a sec to unblock! This setting is inside Cloudflare. You might not even know your website uses Cloudflare because it works in the background as a CDN, helping your website load faster. If you check your website using the tools I mention, you can find out whether Cloudflare is being used on your site. Cloudflare seems to have taken this step because of how AI companies are crawling websites, and honestly, I don't completely disagree with the reason behind it. But having AI crawlers automatically blocked from September 15 could be a problem if you want your business to appear in AI answers. The setting is inside Security Settings. Look for the AI crawler control and make sure it is set to allow rather than block. This is especially important if AI visibility is part of your strategy. With one of my clients, we went from zero to around 500 visitors from AI traffic in two months. And what I did was exactly what I explained in the video. If your AI crawlers are blocked, you're potentially closing the door on that traffic before it even has a chance to reach you. #SEO #DigitalMarketing 👇🏼 Comment VIDEO for the FULL VIDEO BREAKDOWN

• 
  Jloasxhq (@pcapdodger) reported 24 minutes ago

  @NYBackpacker @Real_RobN No, not quite lying. When I hand Harry Hauri exposed it in NOV 2020, they denied it and by Feb 2021 after I mapped their entire network, they hid behind CLOUDFLARE and AWS. They denied it constantly, even when we exposed Goran in Canada who had been going between Serbia and Canada.

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 29 minutes ago

  AI-generated Rivet Actors / Workflows are (finally) here 🥂 Some design notes on Dynamic Apps: Powered by agentOS → provides lightweight sandbox-as-a-library V8 isolate runtime → generated apps scale to 0, cold starts in ms, 22 MB per app, native JS performance (not slower WebAssembly like QuickJS) Novel Node.js-compatible runtime → ground truth agents already know & existing libraries work, native performance No nested virtualization → pure userspace, like Chromium & Cloudflare Workers Self-hostable → Dynamic Apps can run anywhere, including Kubernetes, Railway, EC2, etc (which don't support microVM / KVM) SQLite sharded by actor → scalable, fast, cheap, uses no compute when idle A Rivet namespace per app → isolates its actors, separates billing, and nothing to provision Builds run inside agentOS → npm install & build steps in the WASM sandbox, like a Dockerfile without the Linux VM Dynamic Apps also supports plain REST backends & static frontends deploy the same way

• 
  Dave Bettin (@dbettin) reported 29 minutes ago

  @dillon_mulroy @EffectTS_ Where is the cloudflare support?

• 
  BucketShop (@RealBucketShop) reported 33 minutes ago

  Sigh. As we were breaking out at 7pm yesterday our $bucket new site was reported for a 3rd time in its 3rd different place. Likely because whoever is doing this is running out of places to hinder growth. Nothing has been compromised. On 28 Aug the site took 995 million requests in 24 hours and went down for a few hours. The protocol never stopped. Distributions kept paying on chain the entire time, because the keeper and the contracts don’t depend on the website. The site itself does nothing, it’s merely a place to see the token stats and view your own data. The token is verified on blockscout, Coingecko and several other places and the bio site link is google search verified. Contracts are immutable, LP is burned, ownership is renounced. All checkable without trusting me. @X blocklist isn’t cleared because they have no team. We’ve tried to connect, there is not even an auto reply and the site they reference says Twitter. @Cloudflare was appealed immediately. Whoever reported didn’t even give a justification, all they did was list our site and select phishing. It’s market as in review, we have no clue how long they take. It’s becoming increasingly obvious this is coordinated. We’ve appealed to cloudflare on who’s reported this. Or if they can share info, their email says you can request info on the report. That being said. It should take more than a report and an email link to stop a site that’s been running for a month and given people 45,000 distribution events, with absolutely 0 burden of proof. For now. Just use the old site that’s Google safe search reviewed and approved. It’s identical anyways. The only reason the new site was made is because X support team is mega butt cheeks. Full timeline below.

• 
  SyntaxError » CEO of "CEO of..."-names (@SyntaxError2505) reported 34 minutes ago

  @NewAgeRetroNerd It never failed on me Cloudflare should have a look

• 
  Wyatt Stephens ⚛️ (@whyitscurations) reported 36 minutes ago

  @elithrar sending something your way this week after going down a rabbit hole on this re cloudflare artifacts, vibe coding sdk, wallet. if it has merit, might want to forward to @Cloudflare startup team.

• 
  Harshit Sehgal (@harshit10sehgal) reported 37 minutes ago

  Cloudflare is basically trying to create an identity layer for ai bots. Their new BotBase for Operators lets crawler/agent developers declare: Who operates the bot. What it does. How it uses site content. And keep that information updated inside Cloudflare’s bot directory. This sounds boring, but the web has a weird problem rn. A website might see traffic from: Search crawlers. Training crawlers. Retrieval bots. Shopping agents. Browser agents. Scrapers. And increasingly autonomous users acting through agents. Blocking all bots destroys useful traffic. Allowing everything means losing control of your content. So we probably need something between: allow and block. Identity + declared behaviour isn’t enough to guarantee a bot behaves honestly. But imo the agentic web eventually needs something similar to: robots.txt + identity + permissions + economic rules.