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:

• 
  Beshoy Samy (@_besh0y) reported 8 minutes ago

  @CloudflareHelp @Cloudflare I have two open urgent tickets since yesterday and nobody is taking any action. What on earth can I do to get some support?

• 
  Vedant Anand 🐲/acc (@Vedantsx) reported 8 minutes ago

  @eastdakota @Cloudflare Any luck fixing opennext/cloudflare issue @eastdakota ??

• 
  Max (@overton4242) reported 12 minutes ago

  @DanielLockyer aka when cloudflare is down

• 
  George (@GeorgePZotos) reported 18 minutes ago

  @claudeai @AnthropicAI On macOS, the desktop app throws a Cloudflare error and then closes out whenever I try to use Cowork. It won’t load at all. Works fine on my iPhone, just not Cowork on the Mac. How do I fix this issue?

• 
  Ben Baptist (@oha1th3r3) reported 18 minutes ago

  @ansizinolanlar @jpwexperience @Vultr Oh weird! I've been trying to figure out why my *all* of my Cloudflare-backed websites are down right now (running on diff domains) but running thru a Vultr VPS. Nothing changed on my end and everything *seems* fine. Now I'm starting to think there really is a CF issue.

• 
  OpinionEver (@opinionever) reported 19 minutes ago

  @MickamiousG I bet it connects to the internet. Stops working if Cloudflare has an outage. Bricks itself on firmware updates. Or if it is working it analyses your passings which you can view in an app, which it also sends back to the government if it detects drugs.

• 
  Kene 🐘 (@spatocodex) reported 21 minutes ago

  We recently migrated Partnac from @hCaptcha to @Cloudflare Turnstile. On the surface, it looked like a small engineering task. But the reality was a little more interesting. Our goal wasn't just to block bots. We wanted to reduce friction for legitimate users signing up for partnerships. Every extra click, puzzle, or image challenge creates drop-off. The challenge is finding the balance between security and user experience. After testing Turnstile, a few things stood out: • Lower friction for real users • Better completion rates on forms • Faster page interactions • Less user confusion • Simpler implementation than we expected One thing I find interesting about infrastructure decisions is that users rarely notice when they're done right. But they do notice when a signup flow feels slow, annoying, or broken.

• 
  Vladislav Kyslik (@VKyslik) reported 23 minutes ago

  @THBitcoinBuddha @Investanswers Some companies are already transitioning to post-quantum cryptography; e.g. Cloudflare has largely already made the shift. They don’t have a problem. The problem with BTC is that old addresses won’t be possible to migrate, which is why there are proposals like BIP361 or BIP360.

• 
  QFS17 (@riabcevv) reported 23 minutes ago

  remember talking about how ai coding is great, but the deployment phase is still a pain? well, openai is trying to fix exactly that. they just announced a feature called sites, designed to deploy projects directly from codex with zero server hassle. basically, you prompt an mvp into existence and go live immediately in the same interface. cloudflare and others have been making moves to support agents, but native deployment inside the llm environment is a game changer. the rollout just started, so most of us are still on the waiting list. but the direction is clear. we are moving fast toward complete end-to-end automation. anthropic is definitely working on a response to this for claude code. are we witnessing the end of traditional devops for small projects, or is this just hype? opinions? 💻

• 
  Rishabh Khandelwal (@AIrishabh) reported 23 minutes ago

  The AI infra story this week isn't another model launch. It's the token bill. Cloudflare adding spend limits to AI Gateway is the operator signal: agents are moving from "can it work?" to "can it run without silently torching budget?" Cost controls are now product safety.

• 
  Bhargav Shivarthy (@bshivarthy) reported 27 minutes ago

  A lot of my internet habits still feel very human. I keep tabs open because I am afraid I will lose the thread. I send myself links I may never reopen. I reread the same page twice because I forgot why I came there. I ask someone, “do you remember where we saw that?” That is the web I grew up with. It was built for people trying to find, compare, remember, and decide. @eastdakota just pointed to Cloudflare Radar showing bot traffic passing human traffic for worldwide HTML requests. I think this is one of those moments we will point back to. Not because a line moved on a chart. Because the web started serving a new audience. Software is now a reader too. That can sound cold, but I do not think it has to be. Every time we scale an audience, we have to build new ways to support that audience. More readers means more surfaces, more formats, more infrastructure, more trust, more context. This is not zero sum. There will be uncertainty. There will be dislocations. Change always creates some discomfort before the new workflows feel obvious. But I do not think this means there is less to do. I think it means there is much more we can finally do. There are too many problems bottlenecked by attention, memory, monitoring, translation, coordination, and follow-through. Health needs more eyes on more signals. Science needs more ways to connect scattered work. Climate needs more systems that notice change early. Companies need better context. Governments need better feedback loops. People need tools that help them keep up. The next audience for the web will not only click and skim. It will watch, compare, trace, and act. That is going to change how information is published, structured, trusted, and maintained. Our 20s is not slowing down. If anything, it is just getting us warmed up.

• 
  Normal Guy (@Normal_2610) reported 27 minutes ago

  57.5% of web traffic is now bots, Humans are a minority on their own internet, The cause is multiplication. A person shopping for a camera visits five sites, An AI agent doing the same task visits five thousand. OpenAI alone generates 69% of all AI bot traffic. The real damage hits publishers, Their servers pay to serve pages that earn zero ad clicks, zero subscriptions, zero revenue. The ad funded web was built for human attention, now it taken by machine attention. AI agents that browse the web on your behalf, That is the product. What it trains you to do is stop visiting websites yourself. What it kills is the click, Agentic AI traffic grew 7,851% in one year. Three sectors ate 95% of that load. Retail, media, travel. Publishers now serve pages to machines that never subscribe, never see an ad, never convert. Every site built for human eyeballs now pays more bandwidth to serve robots that bring in zero revenue Means Money will go to Infrastructure that proxy of Agentic AI The internet just split into two economies, One is human, built on ads, subscriptions, and pageviews. The other is machine, built on data extraction at scale. US already hit 71.5% bot traffic on Cloudflare, AWS is redesigning its cloud for agentic workloads that spike and disappear in seconds. Cloudflare launched pay per crawl so publishers can charge bots for access. Parag Agrawal built a whole startup around paying publishers when AI agents use their work, The web keeps running, it just has a different customer now. Well, Personally i does 100x use of what i use earlier though Agentic AI, still i have efficiency issue but in last 3 month it become smarter a lot and fast not need much training So, What yu have look at is Infra

• 
  トラッキー (@RYUSEI2020_0203) reported 28 minutes ago

  This is honestly insane. Cloudflare just shared new data — bots and AI traffic now make up 57.5% of all HTML requests on their network. Humans? Just 42.5%. They handle about 20% of the whole internet, so this isn't a tiny sample. Their CEO says the agentic AI wave

• 
  Arpit Bhayani (@arpit_bhayani) reported 28 minutes ago

  SYN Flood is one of the oldest denial-of-service attacks, and it is still effective today. Here's what happens under the hood... A TCP connection is established with a three-way handshake: the client sends a SYN, the server responds with a SYN-ACK, and the client completes it with an ACK. What's interesting is that during this process, the server allocates memory for each half-open connection in a backlog queue. In a SYN Flood, an attacker sends thousands of SYN packets but never completes the handshake. The server keeps waiting for ACKs that never arrive, and the backlog queue fills up. Once it is full, legitimate users can not connect anymore. Thus, a DoS attack. What makes this attack effective is the 'asymmetry' - the attacker sends tiny packets with minimal effort, but the server has to allocate resources for each one. A single low-powered machine can overwhelm a much more powerful server. Fun fact: SYN floods have taken down GitHub, Cloudflare, and several databases in the past. To defend against SYN flooding, we can: 1. Cap the number of SYN packets from a single IP 2. Drop packets from known malicious sources 3. Or, the most effective, use SYN Cookies With SYN cookies, the server does not store anything. Instead, it encodes all the necessary connection information (client IP, port, and a timestamp) into the initial sequence number of the SYN-ACK packet it sends back. This sequence number is cryptographically generated, so it cannot be forged. SYN cookies make the handshake effectively stateless on the server side until it's fully verified, so the server does not reserve any resources until it knows the client is real. By the way, most modern operating systems have SYN cookie support built in. On Linux, we can enable it with `net.ipv4.tcp_syncookies = 1`. If you are interested, the Wikipedia pages are pretty well written for understanding this, and as always, you can use your favorite LLM to dig deeper.

• 
  Filip (@filip_a__) reported 29 minutes ago

  @saltyAom @elysiaJS Worker size is often the biggest problem with cloudflare workers and platform as the whole than start up time 🫩