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:

• 
  Christian Nonis (@christiannonis) reported 8 minutes ago

  @Samaytwt I started with @GoDaddy, great customer care 10++, poor dev experience, migrated to @Cloudflare

• 
  Nick Emb (@nicolasembleton) reported 10 minutes ago

  @jpschroeder Sorry to hear that... That's what I'm the most scared about on CloudFlare and makes it impossible to use in production. Just too damn scary. If anything goes rogue, Cloudflare is having a field day but you're broke.

• 
  Ryan Kramer 🛠️+⚙️=📈 (@ryankramerllc) reported 10 minutes ago

  @BrianRoemmele Cloudflare spent a decade selling bot mitigation, now they're shipping the bot's browser. the real product isn't rendering, it's agent identity. whoever issues the credential owns the traffic. did they say if Kitesurf ships signed agent headers day one or is that phase 2?

• 
  Eric Schweizer (@ericschweizer) reported 10 minutes ago

  @masoncapitalllc @remarks They did this with cloudflare last week. Put AI in charge of report tickets screening. It was a total disaster. AI was shutting down legitimate sites hundreds of them. A site dedicated on preventing sites from being shut down was the one doing the shut downs. AI not reliable.

• 
  Jamil (@mjamilmoughal) reported 12 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.

• 
  Mike (@ozzorag) reported 12 minutes ago

  @jpschroeder I had a similar problem ~$1000 in overages I wasn't expecting on a fun personal project. @Cloudflare support took months to respond and then told me I'm out of luck. They did give me a $250 credit for future bills. Pretty terrible service and no automatic kill switch.

• 
  Boyd (@0xBOYD) reported 13 minutes ago

  Ah, turns out the budget alert for account wide spend is new and added by Cloudflare, but didn't take effect during the last billing cycle. We had alerts for workers but that would not have caught this. This is a very bad feeling that we will make sure we never feel again.

• 
  akshat (@aiproductguy) reported 13 minutes ago

  @CloudflareDev @CloudflareHelp @Cloudflare Please help!

• 
  Joy (@Joytimmermans) reported 14 minutes ago

  @MikeBradleyAI @0xSero This is wrong. Because once you on the device if the rig is not on a seperate network / vlan you can still access everything… cloudflare tunnels would not solve a single thing of his concerns

• 
  vu (@_vu) reported 14 minutes ago

  @jpschroeder I had the same issue. Cloudflare did not give a ****. Honestly **** their durable objects

• 
  Vlad | AI Build Lab (@VladBuildsAI) reported 18 minutes ago

  @winsontang This is a good example of why I like measuring AI workflows at the boundary, not at the model output. The source shows the visible part: "Winson Tang · 3 год Discover insights like never before with Cloudflare Radar Researcher". The useful next question is what has to be true around it for the result to survive real work. I would check 5 things: input quality, human review minutes, retry behavior, permission boundaries and recovery after the handoff from research to execution. If those are not measured, the demo can look like automation while the hidden cost sits in cleanup. The metric I would want is retry rate after the first failure. That tells you whether the workflow is reducing total work or just producing more artifacts that somebody else has to validate.

• 
  kiruwaaaa (@kiruwaaaaaa) reported 20 minutes ago

  Base just admitted by quietly killing its own social app... @base spent 2025 building a consumer social network on top of the chain. In July 2026, that got walked back entirely - the app handed off, and the entire chain repointed at three things: trading, payments, and AI agents. > 92.8% of all AI agent payments on the internet right now settle on Base > 99.8% of those payments run in USDC through x402, the protocol Coinbase built with Cloudflare > Base alone has processed over $19 trillion in stablecoin volume this year - more than most G20 economies move annually This isn't a pivot. It's an admission that agents, not people, are about to be the largest customer base ever handed to Coinbase in one product cycle. Stripe is chasing this with MPP. UnionPay has APOP. OKX shipped APP. Four protocols launched in twelve months because everyone can see where the money is going - software paying software, instantly, without a human clicking approve. Base didnt lose the social experiment. It just noticed the actual customer walking through the door wasn't a person at all.

• 
  Maik Pietzka (@MPi_IT) reported 20 minutes ago

  @Cloudflare Shadow AI is an inventory and control problem before it is a model problem. Teams need to know which agents exist, which identities and data they can access, what tools they call, and how actions are audited. Visibility first; policy second; safe automation third.

• 
  Grigori Karapetyan (@GregKara6) reported 20 minutes ago

  Disagree with this 100% Code mode is a nuisance. Extra abstraction that pretty much didn’t go anywhere. (We had code mode before cloudflare and anthropic) The agents are masters of the terminal and have 0 issues calling tools and are pretty efficient. If you need safety sandbox the agent.

• 
  Synapse Brief (@Synapse_Brief) reported 22 minutes ago

  Three separate companies just told you where AI capex is actually going, and it's not more GPUs. AMD bought Taalas Thursday. Toronto startup, undisclosed price, does something genuinely different: etches model weights straight into silicon instead of running them on general compute. Their HC1 chip runs Llama 3.1 8B at ~17,000 tokens/sec on a 6nm TSMC die, which Taalas claims is roughly 48x a comparable Nvidia setup on that specific workload. That's a vendor number, not an audited one, but AMD didn't buy this for the marketing. Design-to-silicon in about two months because they only touch 2 of ~100 metal layers per model swap. Lisa Su has been saying GPUs stay the majority of the market because they're flexible. This is the bet on the workloads that aren't: stable, high-volume, latency-sensitive inference where a chip that can only run one model is a feature, not a bug. Same day, SpaceX and Tesla confirmed Terafab: a $16.8B first-phase fab in Grimes County, Texas, on the site of a shut-down coal plant, pulling water from its old cooling reservoir. Logic, memory, packaging, and testing under one roof, chips going into Optimus, Cybercab, and orbital data centers. Worth knowing: SpaceX's own May IPO filing proposed $55B initial and up to $119B total for this project, and called the whole arrangement a "general framework" with no binding commitments on either side. $16.8B is real money and a real site. It is not the whole plan, and Musk's framing has moved the topline number around before. Also Thursday: Cloudflare shipped Kitesurf, a browser built for agents instead of humans, running in V8 isolates on Workers instead of Chromium. 3 to 7x less CPU and memory on screenshot and extraction workloads, already passing 215,000+ Web Platform Tests, drop-in compatible with Puppeteer and Playwright. The insight isn't the perf number, it's what it's for: every research agent and scraping pipeline has been eating Chromium's full resource bill for tasks that never needed a rendering engine built for 50 human tabs. Cloudflare's making the same "stateless, cheap, disposable" bet across its whole agent stack this week. Three different companies solving the same underlying problem from three angles: chips too generic for the workload, fab capacity too scarce for the demand, browser infra too heavy for what agents actually do. None of this is about better models. It's about whether the stuff underneath them can afford to run.