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:

• 
  Wayne Gale (@waynegale2026) reported 3 minutes ago

  The next question is: how do we solve this in the personal-computing Agent era? Do all of these Agent environments really need to live on the local machine? Could the runtime, file system, browser, terminal, caches, and other resource-heavy components be separated from the laptop and pushed into the cloud, while the local computer remains mainly the interface and control center? I think this is increasingly something products like ChatGPT need to solve at the infrastructure level, rather than leaving users to solve it simply by buying machines with more RAM. Cloudflare seems to be moving in a similar direction: pushing more of the Agent infrastructure and execution layer into the cloud. As Agents become truly parallel, the question should probably shift from “How much RAM does the user have?”to “How much compute can the product dynamically provide to each user?” @thsottiaux — this might be an interesting problem to think about for the future of ChatGPT/Codex. $MU $SNDK $SKHY

• 
  AdevAarons (@AdevAarons) reported 5 minutes ago

  Cloudflare just launched AI visibility reporting (AEO). Early access is open. When a company that much of the internet runs through starts measuring "does AI recommend this business," it stops being niche. The category just now got validated. The funny part: Cloudflare made it easy (often default) to block AI's crawlers, and their tool now reports exactly that, the 403s. That's the #1 thing my free audit keeps catching. 100 of 123 businesses I tested were blocking AI without knowing. They're about to show a lot more people they're one of them. Their dashboard shows the wound. My audit shows the whole chain and what to fix, on any site. Glad they built it.

• 
  Matviy (@matviy) reported 6 minutes ago

  @svpino How will that apply to logic with customer data or third-party API calls billed per call? Sure, you’ll find out it doesn’t work in the logs or maybe with a new shiny fat bill. But the bill could easily go into thousands, or customer trust is gone. No one who is “pro-code review” says the whole thing should be read and reviewed. What we are arguing is that key areas of the code must be checked because the cost of going wrong is very high. Literally a few days ago a guy wrote a viral post about how he was charged $8k by Cloudflare because his code had a loop in the wrong place.

• 
  TeleLLM (@Telestijl) reported 14 minutes ago

  @levelsio Private Relay is a likely culprit — iCloud → Private Relay (or Safari's "Hide IP Address") routes DNS/traffic through Apple/Cloudflare relays per network, and macOS applies it more aggressively on a fresh hotspot connection than iOS does on its own cellular link. Toggling it off for that specific network usually fixes the "works on iPhone, not tethered" split.

• 
  flavio (@flaviocopes) reported 15 minutes ago

  Too bad Cloudflare Pages and Workers still don't have a “cancel the current deploy when a newer commit arrives” option. Agents might push 3 commits in quick succession and the build takes minutes, I really only care about the latest. Let me cancel-in-progress 🥹 @CloudflareDev

• 
  Root Logic (@Root_Logic_0) reported 19 minutes ago

  @Cloudflare do you have spend caps? thats one major thing preventing me from using any service at cloudflare.

• 
  Jordy.app (@Jordy_vD_) reported 20 minutes ago

  @johnennis Nah, with n8n you get to self-host/ host on-prem for enterprise With Zapier you get a platform specifically designed to max uptime & world-class customer support. I’d do cloudflare workers if your time is of little value, and you can spend hours debugging / building from scratch N8N to self-host & extend as it’s opensource - running an automation platform inside your home network can do cool things as it can reach local devices =) Zapier to set it and forget it + big coverage + the other tools Zapier provides like SDK and MCP. Not speaking on behalf of Zapier atm, just as a dev; I like that the Zapier SDK isn’t just for workflows, it actually powers a bunch of my agent’s skills. I’ve had to get Google API keys a few times for OpenClaw and friends & it was a pain. Nice to not have to worry about that stuff

• 
  Kush (@kushbhuwalka) reported 20 minutes ago

  If I had to summarize the problems of coding agents today, they would be, in order, > reliability & naivety > infrastructure inertia > safety >cost > speed 1) Reliability & Naivety - The agents are not consistent and are prone to degrading, going down weird rabbit holes, and simply performing in random ways. They sometimes make very dumb decisions, especially on long horizon tasks. 2) Infrastructure inertia - Clicking around the computer is actually a terrible way to do things, and thanks to cloudflare & captchas, many products and sites make life very hard for agents to operate. Memory is fallible too. 3) Prompt injection - this is unsolved, although you can mitigate this by running a small model on any incoming inputs. A well-crafted prompt can trick both the AI security layer and then the agent. As AI-pilled as I am, I would not give my agent unfiltered access to my bank account. Things like codemode & permissioning help, but you can't expect to permission everything you give an agent. 4) Cost - frontier models are too expensive. The subsidization is unscalable (I max out two codex plans ~ 20-28k/m). Even for the average user, to have an always on running agent thats actually doing work will cost atleast ~$200 a month ($100 for tokens, $100 for compute). 5) Speed - SOTA models churn out tokens at around 30 tokens/second, which is unimaginably slow. Although I imagine cerebras will solve this (for eg. SWE 1.7 by @DevinAI is somewhere around 1000 tokens/second, and is so fast you don't really see it streaming in).

• 
  Uptimus (@UptimusApp) reported 21 minutes ago

  Aug 10, 2026 at 12:19 UTC: Cloudflare reports the incident affecting the 1.1.1.1 public resolver in Tel Aviv is resolved. The issue lasted 123 minutes, and DNS services are operational.

• 
  Jamil (@mjamilmoughal) reported 24 minutes ago

  AI agents are about to make human internet traffic look tiny. Cloudflare data already shows machines generating more than half of all traffic, and their forecast says non-human activity could reach 1,000 times human levels within five years. A single request from you can send an AI agent racing across thousands of websites. Humans won’t disappear. We’ll just become a rounding error. Starlink is the only system currently scaling fast enough to handle that explosion. With V3 satellites, the network capacity could jump 10–50x (or more) over today’s global bandwidth. The internet is shifting from people browsing to machines working at full speed. The companies and networks ready for that shift will define the next decade.

• 
  willard shoko (@WillarShoko) reported 27 minutes ago

  Cloudflare says humans could become a "rounding error" as bots generate 1,000 times more internet traffic Just a couple of months after Cloudflare revealed that bots have officially surpassed human traffic online, the company has given its view on what things will look like in five years. It's not good news for us fleshy meatsacks: non-human traffic could be up to 1,000 times higher than human traffic. CDN and cybersecurity giant Cloudflare held its Q2 earnings call on Thursday, during which chief financial officer Thomas Seifert gave a concerning prediction about what the web will look like in the future. "If the current trends continue, we think in five years, non-human traffic will be as much as 1,000 times as much as human traffic," he said. "In other words, humans will be a rounding error on the internet, not because human traffic goes down, but that's just how fast we're seeing non-human traffic grow."

• 
  Logan Weaver (@LogWeaver) reported 30 minutes ago

  We think we are the main user of the internet. That’s wrong. Machines now make more than HALF of all web traffic. This report comes from Cloudflare, and even Google and Meta should be nervous about this. Cloudflare runs the plumbing for about one in five websites. So it sees a big slice of all web traffic. The machines are mostly AI bots and agents. They scan the web to train and feed AI models. They read pages far faster than any person can. A person might visit a few websites to buy something. An AI can visit thousands in the same moment. Not long ago bots were about 20 percent of traffic. Now they are more than half of it. Cloudflare expected this to happen around 2027. It arrived a full year early instead. Its finance chief gave investors a blunt warning: Human activity could become a rounding error in five years. Bots could outnumber people by a thousand to one. Picture a web built almost entirely for machines. Now here is the part the market keeps ignoring. The free internet runs on ads shown to people. More and more, an AI reads the page for you. You get the answer and never visit the site. That site gets no visitor and no ad money. Google and Meta are the kings of the ad model. Their fortunes depend on human eyes and human clicks. But those humans are becoming the smaller half. Bots do not watch ads or buy products. These are some of the most valuable companies alive. Their whole engine sits on a shrinking base. Even Cloudflare admits the old model is breaking. It now wants to charge the bots to visit. That risk barely shows up in the headlines. The crowd sees AI as pure good news for big tech. This is a slow shift, not a crash tomorrow. But slow shifts are the ones that reprice giants. The biggest changes are often the quietest ones. The crowd chased the obvious story. The data told a different one. That's the whole game. Surmount runs on clear rules and real data, not hype. If you want a system that follows facts, start here:

• 
  Keetard (@TheKeetard) reported 33 minutes ago

  "if the current trends continue, we think in five years, non-human traffic will be as much as 1,000 times as much as human traffic. humans will be a rounding error on the internet." that's cloudflare's cfo, thomas seifert, three days ago, on the company's earnings call. not a forecast from a crypto account. a company sitting directly in the flow of internet traffic looking at its own data. the number that got him there is already real. cloudflare says machine traffic crossed human traffic in may, years ahead of its own prior prediction. bots weren't supposed to catch up until 2027. think about what happens when that traffic stops retrieving information and starts conducting commerce. agents discovering services, calling apis, buying data, exchanging assets and settling payments at whatever multiple of today's volume seifert is describing. financial infrastructure stops operating at human speed. it starts operating at machine speed. this is the context keeta's manifesto was written into four months before seifert said any of this. it describes an ai agent transacting on a business's behalf and states plainly that the eventual requirement isn't millions of transactions per second. it's billions. that sounded like a strange thing to build toward in march. keeta's public stress test, run on google cloud and independently verified by chainspect, reached 11,122,116 tps across more than 30 million accounts and 25 billion transactions, with 400ms finality. it is a proof point, not a ceiling, and the architecture was designed to scale horizontally from there. keeta is also building the other things autonomous economic actors will need. identity. programmable permissions. compliance. x402. multi currency settlement. routing between financial systems that don't share an owner. four months ago, a network was designing for billions of transactions per second because its own manifesto said that's what the agentic economy would eventually require. this week, the company watching internet traffic at global scale said humans could become a rounding error. maybe 11 million tps wasn't built for today's financial system. maybe it was the first benchmark for the next one.

• 
  Pils10 (@PilsZehn) reported 33 minutes ago

  @linkrobinsllc @Samaytwt Agreed. Had some good experiences with Namecheap, their support is super fast and helpful, even if I dislike their "surcharges". Cloudflare is great, but I hate them limiting new domains to 200 rather than 1.000 DNS records. Hostinger is ok-ish, but I personally use Netcup.

• 
  Dipak Gajjar (@dipakcgajjar) reported 35 minutes ago

  @csaba_kissi I still use Namecheap for my domains. The dashboard and support have been reliable for me over the years. Renewal costs might be higher than Cloudflare but I haven't felt the need to switch yet.