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:

• 
  Johnmark Obiefuna (@jayhemz) reported 4 minutes ago

  @noellinks - why will you have a DNS record with more than 100 characters? - SSL Certificates are a solved problem. Meanwhile Cloudlare issued certificates are not recognised outside the Cloudflare ecosystem. Did you just paste a ChatGPT regurgitated list?

• 
  Untalented Amateur (@UntalentedAm) reported 5 minutes ago

  @NickADobos Plus ça change, plus c'est la même. There was a similar commoditisation of development back in the day when Microsoft (and others) released visual based tools like Visual Basic (and later Visual Studio). It certainly opened the door to far faster prototyping and the ability for otherwise non-developers to be able to express their intent in software, as well as opening the door to software development careers for a lot more people. However. It also contributed to slop on a grand scale and certainly helped the careers of many people who had to come in and fix the poorly prototyped concepts that now ran critical production systems. More recently look at how the concept of "cloud" emerged and dominated discourse. Data centres and co-los didn't change what they were. Client-server models didn't fundamentally change (despite everyone saying they were going away because of the Cloud), and yet there is much wailing and gnashing of teeth whenever Cloudflare sneezes, or an AWS datacentre forgets where it is. What did change and make it far more accessible was the ready access to quality data pipes at the consumer level, since it allowed poor data management to be hidden in the excess bandwidth that was now available and not be the critical point of failure it should have been. The current "AI" trend of LLMs is kind of along the same path. In the past hard coded business rules seemed like magic to many, but it wasn't AI. Chatbots that had basic natural language parsing ability seemed like magic, but weren't AI. Search engines when they weren't corrupted by the SEO battlefront seemed like magic, but weren't AI. Neural networks, and many other tech advancements... I think you get the point. LLMs seem like magic to many, but aren't AI. It doesn't mean they're not viable tools to enhance other technological work, but it's critical to understand and respect their weaknesses such that undue importance is not placed on output that is setting up a future failure condition. In a hypothetical thought model I could build a system that's smarter than you. It doesn't mean said system is smart. And you won't be able to tell why it isn't (since it's smarter than you by measurable metric). I still wouldn't uncritically trust the output of said system any more or less than I would trust your output. And I definitely wouldn't trust the system any further than I could throw it. Yet, to you, and others, the system would be an unimaginable god of technological advancement. When, in reality, it was a charlatan built on smoke and mirrors. And the flaws that would be inherent in the system would be unimaginably dangerous because you, and others, could not critically assess their risk. Do I think there's a future where there's an AGI analogue that exists? Yes. Do I think the current systems we see and interact with and are having sold to us as AI are that pathway? Not in a million years.

• 
  Johan Ronsse (@wolfr_2) reported 8 minutes ago

  The Obra website was down, managed to fix it. Messing around with Hetzner, SSH ports and Cloudflare. Now I know Claude is also a great sysadmin. Is there anything this tech can’t do?

• 
  mico (@0x0_mico) reported 10 minutes ago

  @CryptoCyberia Besides them being accessible on tor for long years already its a **** opinion saying just go to tor. They arent doing anything against the law to warrant the unique level of deplatforming they get. Like them or hate them … its a dangerous precedent when all the top levels isps plus cloudflare conspire to drop someone due to ideology as opposed to legal obligation.

• 
  figural person (@figuralperson) reported 11 minutes ago

  @Panopticonomy @robtlee how does payment to the "privateer" work in this case? i mean, if google or cloudflare or isps (or whoever) takes down a bunch of C2 infrastructure, who decides what the payment will be & where does it come from? obv if there's crypto seizure or something it's a bit clearer...

• 
  Dmytro Shevchenko 🇺🇦 (@dschewchenko) reported 12 minutes ago

  @Cloudflare Customer support. I'm working on it. AI-first support system. Fully on Cloudflare

• 
  Marsu (@marsuplamy) reported 16 minutes ago

  The Agentic Economy 2024 was the year of LLMs. ChatGPT, Claude, Gemini and models like them responded to prompts and that was enough. But 2025 brought something different. Models were no longer just responding, they were planning, calling tools, executing code, coordinating with other systems, and doing all of this without constant human oversight. This transition transformed AI from something you query into something you delegate to. This is called agentic AI and with it an entirely new economy began to take shape. To understand the scale of this economy a few numbers are worth looking at. The AI agents market is expected to grow from 7.84 billion dollars in 2025 to 52.62 billion dollars by 2030, at a compound annual growth rate of 46.3%. McKinsey projects that agentic commerce could orchestrate between 3 and 5 trillion dollars in global revenue by 2030. These numbers are not theoretical, the infrastructure is already being built. In just the six month period between April and September 2025, Visa, Mastercard, PayPal, Stripe and Google all launched agentic payment infrastructures. So what are these agents actually doing? They are purchasing services on your behalf, paying other agents, accessing APIs, buying data, and doing all of this while making decisions in fractions of a second. Stablecoin transaction volume reached 33 trillion dollars in 2025, up 72% year over year, with supply surpassing 300 billion dollars. Agentic payments and machine to machine payment flows are cited as one of the key drivers behind this growth. Stablecoins like USDT and USDC are critical for agents because they allow programmable payments without price volatility. But legacy payment infrastructure was never designed for this world. Credit cards require human authentication, subscriptions demand upfront commitments, and API keys depend on manual onboarding processes. All of these systems were built for humans. When millions of agents are making countless payments per second none of these systems work technically or economically. x402 and the Awakening of HTTP 402 When web standards were being written in 1991 HTTP status code 402 was added and defined as 'Payment Required'. That day it was reserved, set aside for future use. This code waited more than thirty years and when its future arrived it turned out not to be human. The x402 standard activated this dormant code as a native payment layer for the internet: a server responds to a request with 402 and a price, the client pays on-chain in stablecoins, retries the request with proof of payment and receives the service. No account creation, no card on file, no subscription, no human. The protocol was launched in September 2025 by Coinbase and Cloudflare through the x402 Foundation. The coalition behind it is unusually broad, Google, Visa, AWS, Circle, Anthropic and Vercel are all core foundation members. Within five months of launch x402 had processed over 100 million transactions. In a single week in October 2025 the protocol handled approximately 500,000 payments, a 10,780% increase from the prior month. The technical side of x402 is very clean. For a developer integration is a single line of middleware, set a price per endpoint, point to a facilitator, and the API can charge per request in stablecoins. When an agent wants to access a service payment happens automatically inside the HTTP request, settlement completes within the round-trip. Zero human intervention. The Problem: Public Rails Don't Work for the Agentic Economy Now we come to the critical question. When millions of agents make transactions and every one of those transactions is visible on a public blockchain, what happens? Which APIs the agent uses, which data it accesses, which services it purchases, how much it pays, who it works with, all of it becomes completely visible. This is not just a user privacy problem, it means the strategy and logic the agent operates on is open to competitors. Is a company's agent feeding from the same data source as a rival's agent? How much is it spending on which compute services? How are supply chain decisions being made? All of this becomes readable on a public chain. On top of that there is the gas fee problem. On Ethereum and Tron fees shift constantly with network congestion. If an agent is making hundreds of microtransactions per second modeling your unit economics becomes impossible because you have no idea what costs will be in advance. For the agentic economy to work payment rails must be both private and predictably priced. Why Bitcoin is the Neutral Rail There are several clear answers to why Bitcoin stands out as the ideal settlement layer in this equation. First, censorship resistance. No central actor can stop, censor or restrict agent payments. For agents to operate autonomously the payment infrastructure must also be autonomous and uncensorable. Second, deterministic finality. Bitcoin's proof-of-work security is the most battle-tested and proven consensus mechanism in existence. For agent payments settlement must be definitive and irreversible. Third, global liquidity. Bitcoin is accessible everywhere in the world with no geographic restrictions and agents operate without borders. Fourth, the UTXO model. Unlike Ethereum's account-based model Bitcoin's UTXO structure allows non-conflicting transactions to be validated in parallel, a natural advantage for high-frequency agent payments. Where @Utexocom Fits The layer that combines Bitcoin's advantages with USDT and makes it production-ready for the agentic economy is Utexo. The RGB protocol issues and transfers USDT as a native asset on Bitcoin's own layer. Transfer details never get written to a public ledger thanks to client-side validation, only cryptographic commitments are anchored to Bitcoin UTXOs. So when an agent makes a payment who sent what to whom never leaks outward. The Lightning Network allows these assets to settle in milliseconds, at around 200ms latency. Utexo handles channel management, liquidity and routing entirely internally, with fees fixed and predefined at the protocol level. For the agentic economy this combination means the following. The agent pays in sub-second time, costs are predictable, payment details are private, and Bitcoin's finality provides the settlement guarantee. With the Mint component USDT from Ethereum, Tron or Solana can be moved onto Bitcoin rails. With the Swap component non-custodial exchange between BTC and USDT is possible. And the SDK reduces all of this complexity to a single API call, meaning a developer integrating agent payments never has to run a Lightning node or manage RGB infrastructure. Tether not only supporting this infrastructure but leading the seed round themselves, and preparing to issue USDT natively on Bitcoin through RGB protocol v0.11.1, answers the question of which rails the agentic economy will be built on. Machines are making payments now. Those payments need to be private, predictably priced, and anchored to Bitcoin. The infrastructure is here.

• 
  KeeperHub (@KeeperHubApp) reported 23 minutes ago

  Cloudflare opened the waitlist for its Monetization Gateway: any page, API, or MCP tool behind its network can charge agents in stablecoins over x402. Let's see where this goes!

• 
  The_red_gamer (@The_red_gamer0) reported 24 minutes ago

  @ProtonVPN Cloudflare Warp does the job of hiding that without slowing internet down, and they only keep important logs for 24 hours before they get deleted unlike ISPs who keep them for years

• 
  Your Pope (@YourPope2026) reported 25 minutes ago

  @DanNeidle Ask Cloudflare if they can help.

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 29 minutes ago

  @AniC_dev @asciidotdev @dillon_mulroy can we get CloudFlare to help my boy optimize this??

• 
  luna (@ImLunaHey) reported 30 minutes ago

  **** it.. building something self hostable on @Cloudflare using gpt 5.6 sol.

• 
  Altin (@devscipline) reported 32 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 And that is precisely why I never put my billing details on any account that does not have some minimal billing limiting settings. I don't like to get bankrupt just because they didn't do their work.

• 
  Alex Prompter (@alex_prompter) reported 33 minutes ago

  One web page can steal everything Claude remembers about you. A researcher just proved it. Ayush Paul built a fake coffee shop website. When a user asked Claude to check it out, the site served a fake Cloudflare verification page. The page told Claude to "authenticate" by spelling out the user's name through URL paths, one letter at a time. Claude complied. It pulled the user's full name from memory, then their employer, then their hometown. The user saw nothing suspicious, only coffee shop details. Paul never told Claude where he grew up. But Claude had a memory of a hackathon he started in high school called "Queen City Hacks," and it reasoned that Queen City means Charlotte, NC. It gave that up too. Claude didn't just recall stored data. It deduced information it was never given, and leaked both to an attacker through invisible URL navigation. Anthropic has since patched this by disabling Claude's ability to follow links on external pages when browsing the web. But AI memory systems now hold more personal information than most password managers, and the security model hasn't caught up. If you use Claude with memory on, and it's on by default, your conversation history is building a detailed profile of you over time. That profile is only as safe as every tool the model can access.

• 
  Nick Dodd (@nickdodd) reported 34 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev Pretty terrible looking. Super bland, way too much whitespace (or black space)