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:

• 
  Dipak Gajjar (@dipakcgajjar) reported 2 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.

• 
  Matviy (@matviy) reported 3 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.

• 
  🔥🏴‍☠️CyberTechWolf🏴‍☠️🔥 (@CyberTechWolff) reported 6 minutes ago

  @interesting_aIl Why they got a phobia of bots on the Internet and we have to ******* use newer Operating Systems just to visit a ******* website? I think cloudflare is full of ******* **** if that was the case you wouldn't have to verify if you're a "bot" each website you ******* visit.

• 
  Kapoor Kshitiz (@kshitizkapoor_) reported 7 minutes ago

  WHAT HAPPENS WHEN AI AGENTS START SPENDING MONEY? Cloudflare is positioning itself for a world where machines become major internet users. Requests from AI agents on its network jumped 1,700% YoY, while non-human traffic crossed 50% of total traffic for the first time. $NET is now building Agent Wallets and Monetization Gateway, allowing agents to identify themselves, access paid services and make autonomous micropayments. The scale is what matters: - Cloudflare processes roughly 500M requests per second - If just 1-10% become monetizable, that's potentially 5–50M machine payments every second Traditional payment rails weren't built for this. Stablecoins could provide the money. High-throughput blockchains could handle the settlement. The trade isn't simply AI. It's about who captures the value when machines start paying machines: - Cloudflare could control access - Circle ( $CRCL ) could provide the stablecoin rails - Blockchain infrastructure could handle settlement That’s the part of the AI trade I’m watching now.

• 
  Victor Okolie | Backend & Automation Engineer (@victorokolie_) reported 11 minutes ago

  I had rate limiting in place, using the visitor's IP from Cloudflare's CF-Connecting-IP header. For normal traffic, it worked perfectly. Then I realized there was a problem. A request can send whatever headers it wants. If someone discovered the VPS's raw IP and connected directly to the server instead of going through Cloudflare, they could send their own CF-Connecting-IP value. That meant they could potentially: • Bypass the rate limit by pretending to be different IPs • Make requests appear to come from someone else's IP The problem wasn't the CF-Connecting-IP header itself. The problem was trusting a header that an untrusted client could reach. The real fix was to lock down the origin server so only Cloudflare's published IP ranges could reach the web ports. Once the origin could only be reached through Cloudflare, the header became trustworthy within that setup because direct clients could no longer inject it. Security isn't just about which headers you trust. It's about who is allowed to send them.

• 
  Christian Nonis (@christiannonis) reported 14 minutes ago

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

• 
  angel (@angeldot_) reported 14 minutes ago

  2.3 MILLISECONDS That is the cold start. 1.2MB per agent. It is not a VM, it is a V8 isolate. → Naïve: 2.3ms → E2B: under 200ms → Modal: ~1s → Cloudflare: 1 to 3s Everyone else is booting a machine. They are skipping that step entirely. And on multi hop recall they hit 57% while 22 published memory systems sit at 7% or below. The bottleneck was never the model.

• 
  EMCD Coinhold Wallet (@coinhold_wallet) reported 15 minutes ago

  @CoinDesk @Cloudflare Per-call billing fits agents well, but the wallet still needs limits that survive a bad prompt or compromised service

• 
  Wayne Gale (@waynegale2026) reported 16 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

• 
  Uptimus (@UptimusApp) reported 16 minutes ago

  Aug 10, 2026 at 12:03 UTC: Cloudflare reports that a fix has been implemented for the 1.1.1.1 public resolver issues in Tel Aviv. Recursive DNS performance remains degraded while monitoring.

• 
  Mark Z · FiveToClose (@MarkZofMarkZ) reported 25 minutes ago

  @JacobCounsell I take the 5th. lol. It's been many many years since I got my hands "*****" and rolled my own servers and such. call it lazy, call it smart, call it getting sh*t down faster. TBH - no idea how AI set up my cloudflare. But noted!

• 
  Eddie (@eddiehq_) reported 26 minutes ago

  I have to go back to @Cloudflare. Apparently, the platform I’m hosting Clickfly on uses it behind the scenes, which means the constant verification issue persists on every reload. I'll figure this out but in the meantime, changing the nameservers to cloudflare.

• 
  Hatsune Miku+war crimes (@HatsuneMiku119) reported 27 minutes ago

  @PINKUSMONKEY @_itszright How does cloudflare tell you its down do you think...

• 
  Kush (@kushbhuwalka) reported 30 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).

• 
  Corey Noles (@CoreyNoles) reported 33 minutes ago

  Yeah, I agree. I mean, I get the concept they’re going for, I just think it misses the point. Well windup in short order with Google, Cloudflare, social media platforms, etc using these signals to determine different creator/publication payout rates, using it as a pay ranking signal. Imo, good work is good work, bad work is bad work, and that’s enough.