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:

• 
  Roh (@Rohthebuilder) reported 7 minutes ago

  @hieuSSR @algoceo @Cloudflare True, agreed. But when I read it, I felt more related to my problem when I read “unlimited free custom emails”. And when I read “gmail alternative”, my head just told me “no way”. Idk why. Need more UX study on it maybe. Anyway, glad you made this!

• 
  Revanth x (@svsairevanth) reported 10 minutes ago

  @Cloudflare @CloudflareDev Urgent help needed , our R2 access was suspended after payment verification failed. We added a second valid card, but the account remains blocked and Billing shows no invoice or Pay Now option. Please escalate this to the Billing/R2 team.

• 
  Jloasxhq (@pcapdodger) reported 11 minutes ago

  @NYBackpacker @Real_RobN No, not quite lying. When I and 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.

• 
  Arijit (@arrzzt) reported 12 minutes ago

  @Cloudflare @eastdakota I cancelled Workers Paid today, just a day after the new billing cycle started. I haven’t really used anything from this month’s paid limits, but I’ve already got a $5.90 invoice. Any chance you can cancel this renewal and void the invoice? 🥹🙏🏻

• 
  BOOZBOY (@Dorvskima) reported 12 minutes ago

  @RomixUS @kick Kick sits behind Cloudflare, and Cloudflare aggressively blocks traffic coming from data center IP ranges, which is what almost every VPN server uses. It's not actually a DNS issue on your end. The site detects the VPN IP, flags it as a fraud or bot risk, and serves a blank or broken page instead of a real error. That's why clearing cookies, clearing history, and excluding the site inside your VPN app all did nothing. The block happens before your browser even gets a proper response back Try one of these - Test each fix on its own so you know exactly what actually worked. ** Switch to a residential or stealth IP if your VPN offers one, instead of the standard server list. Standard VPN IPs get burned fast because thousands of people share the same address. Try a different protocol inside your VPN app. If it has WireGuard, OpenVPN, or something labeled Stealth or Obfuscated, switch to it. Cloudflare sometimes blocks based on traffic patterns, not just the IP itself. Manually set your DNS to 1.1.1.1 or 8.8.8.8 instead of using whatever your VPN assigns automatically. Sounds strange to use Cloudflare's own DNS to fix a Cloudflare problem, but the resolution step is usually where this actually breaks, not Kick's servers. Change your VPN server location entirely. If you're on a US server try Netherlands or Germany, or the reverse. Some countries have far less flagged IP ranges than others. Turn off IPv6 on your device in network settings. A lot of VPN and Cloudflare conflicts happen because your device leaks traffic around the tunnel through IPv6 instead of going through the VPN's IPv4 route. Fully close and reopen your browser instead of just clearing cookies. TLS session data gets cached separately and survives a normal cookie clear. Test on mobile data with the VPN still on. If it suddenly works, your home router or ISP DNS is the real problem, not the VPN. Start with the DNS change and the residential or stealth server option since those two fix this exact Cloudflare versus VPN conflict most of the time.

• 
  Harshit Sehgal (@harshit10sehgal) reported 13 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.

• 
  Ulaş Difficile (@ulasdifficile) reported 16 minutes ago

  @levelsio Cloudflare verification not working.

• 
  Tomáš Kafka (@tomaskafka) reported 18 minutes ago

  1. Self hosting a service 2. Having to put it behind cloudflare proxy due to bot attack attempts 3. Now my own server is asking cloudflare whether they deem me worthy to enter every time I try to use it Weird future.

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

  Hermes agent just added 44 new one-click app connections, and there's a setting that stops them from slowing your agent down. Cloudflare, Datadog, Metabase, GitLab, Railway, Deep Wiki, and plenty more in the catalog. Before this, you found the server yourself, read its docs, and hand-edited a config file. One typo and nothing connected. Now you open the catalog, hit enter on the app you want, and it handles the key or the login for you. You never touch a config file. But here's the setting most people miss. Every tool you connect sends its instructions to your model on every single turn. Connect enough apps and your context is full before you've asked anything. Cloudflare alone exposes around 3,300 tools. Just the names come to roughly 32,000 tokens. The fix is called Tool Search. Instead of loading every tool description, Hermes swaps them for three tiny helpers. One finds the right tool. One loads its details. One runs it. Your agent only pulls what it needs, when it needs it. That's why you can add 44 connections and not wreck your setup. Two more things: Every connector is off by default, and Hermes hands you a checklist of what each one can do. Reading issues, yes. Deleting things, no. And you can point the terminal at a Docker container instead of your own machine if that makes you nervous. Want the SOP? DM me. 💬

• 
  Anne (@FmailLiam) reported 20 minutes ago

  "Using an in-house bot on an in-house browser to buy a car from the same founder’s company isn’t an AI revolution—it’s an internal API test wrapped in marketing hype." "Call me when Grok bypasses three Cloudflare Captchas, handles 3D Secure verification, and successfully orders an out-of-stock item on a broken Shopify site without special whitelisting."

• 
  Veda Valor (@vedavalor) reported 20 minutes ago

  The hard part nobody talks about: getting playable audio clips. Spotify killed preview_url for new apps in Nov 2024. YouTube's embed rules ban hiding the player (why Heardle clones got taken down). iTunes blocks Cloudflare IPs. Deezer works but its search API is geo-flaky.

• 
  Kamran Khan (@itskamrankhan) reported 22 minutes ago

  @Jordenbs @Taniyatweets_ Jorden, the problem comes when you renew it, GoDaddy will charge hefty fee....you might have got the deal better at initial stages....they will show their colour when you renew,,, My domain still in Cloudflare, Cloudflare has flat pricing they don't charge like GoDaddy...

• 
  colinhacks (@colinhacks) reported 24 minutes ago

  @SheltonLouisGT it's possible down the line. it's more responsible to put this out first as an opt-in to make sure there's no behavioral drift or unexpected issues before seriously thinking about default-on. main issues: 👉 it requires `new Function()` which is blocked by many Content Security Policies (incl the one used by Cloudflare Workers) 👉 bundle size — the compiler adds about 7kb gzipped. may be worth it in regular Zod (though obviously not Zod Mini) in any case, it's more responsible to put this out first as an opt-in to make sure there's no behavioral drift or unexpected issues before seriously thinking about default-on. In the meantime, it's easy enough to use the side-effect import to enable compilation project-wide

• 
  Anubrat (@anxbrt) reported 24 minutes ago

  I thought Cloudflare had solved our scalability problem. It hadn't. We were building a centralized data-annotation platform. The backend was running on the Cloudflare stack, and we had a CDN in front of our assets. So when I looked at the architecture, my thinking was pretty simple:=> Cloudflare + CDN → we're good. At least until we started testing it. Someone would add an annotation to an image,or make a small modification to an existing label,Nothing particularly expensive-looking,But every-modification generated a new pre-signed URL The CDN would cache the image, right? Then we started seeing the system struggle with barely ~10 users. We were making the CDN's job almost useless. Every time the image changed, we generated a new pre-signed URL. From the CDN's perspective: new URL -> new resource -> cache miss ->render/fetch the image again. And image rendering itself isn't cheap either. So a seemingly tiny action “modifying an image annotation” could trigger expensive image processing and effectively bypass the caching advantage we thought we had. p.s - Scalability isn't just about choosing infrastructure that scales. You can put the most scalable infrastructure in front of your application and still build a system that falls over with 10 users.

• 
  Jigs (@debugsenpai) reported 27 minutes ago

  @RueNahcMohr Cloudflare or implementation issue? 🤔