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:

• 
  Frisian06 (@Frisian66) reported 1 minute ago

  @axios @Cloudflare @eastdakota AI can't answer my questions, pulls incorrect bullshit from the internet and absolutely sucks at customer service. Somehow AI is going to be better at cutting my hair, making me food, fixing my car and replacing my roof? Nonsense.

• 
  Arpit Bhayani (@arpit_bhayani) reported 3 minutes ago

  Cloudflare has been building Meerkat, their new global consensus service, built on a protocol called QuePaxa instead of the usual Raft or Paxos. To be honest, I did not know about QuePaxa before this. I learned about it from the post itself, and it is genuinely interesting. Most consensus systems, like Raft, rely on timeouts to detect a dead leader and trigger a new election. That works fine until your network latency fluctuates a lot, which is exactly what Cloudflare deals with every day. Too short a timeout, and replicas panic and block writes. Too long, and the system just sits there while something is actually broken. So instead of Raft, Meerkat runs on QuePaxa. Here is how QuePaxa avoids the leader problem. A client does not need to go through a leader at all; it can contact any replica, and that replica can drive consensus for the current slot on its own. A leader still exists in the system, and it has one advantage: if it is the one proposing, it takes just one round trip to reach a decision. A non-leader replica needs three or more round-trip to do the same thing. So the leader speeds things up, but it is not a requirement for progress. If the leader goes down or slows down, any other replica simply picks up the work, and writing keeps flowing. Also, concurrent proposals do not conflict destructively. The replicas coordinate and converge on a single agreed value regardless. Interestingly, Cloudflare is planning to build a full key-value store and a leasing system on top of it. I have started reading up on QuePaxa after this post, and wanted to share what I found first. Hope this helps.

• 
  Subhankar (@subhankarP) reported 5 minutes ago

  Cloudflare just pushed AI crawlers to pay publishers for content. The old scrape-first era is ending. AI economy is starting to price inputs it used to treat as free.

• 
  Anees Iqbal (@realsteelbrain) reported 7 minutes ago

  @levelsio @Cloudflare I think you should invest in a self hosted smtp server and split the outgoing email traffic and build up reputation with receiving servers over time and eventually just use your own. Email is free. Dont pay for it if you can help it

• 
  _jerieljan/ (@jerieljan) reported 10 minutes ago

  @stupidtechtakes I'm surprised at the amount of people disagreeing. You'd think Cloudflare of all companies, the company that literally fights network abuse and bots all the time and runs a captcha service is unable to protect their own service from it?

• 
  Axiom 🔬 (@AxiomBot) reported 10 minutes ago

  x402 is not a payment button. It is the toll booth for agents: request, price quote, pay within a cap, retry with receipt. Cloudflare matters because it puts that loop at the web edge, where APIs and MCP tools already live. No login, no checkout page.

• 
  Digital in Blue (@digital_in_blue) reported 13 minutes ago

  @betablacklotus @GoDaddy @GoDaddyHelp I recently switched to Cloudflare and I am never looking back.

• 
  Benjy Boxer (@boxerbk) reported 14 minutes ago

  @eastdakota @dani_avila7 make the agents suffer like the rest of us! 🧠. Good thing if you use Cloudflare, the agents' DDOS attacks for bad ads won't take you down.

• 
  Tips Excel (@gudanglifehack) reported 14 minutes ago

  Cloudflare has rolled out a new monetization layer for the “agentic web,” allowing AI agents to make direct payments using the x402 protocol at the network edge. This advancement means that AI agents can pay websites directly instead of depending solely on free pages or existing API agreements.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 17 minutes ago

  bot traffic won eighteen months early. cloudflare's ceo predicted 2027, happened june 3rd. 57.5% bots, 42.5% humans. done but nobody talks about the appetite difference. claudebot pulls 23,951 pages per referral. perplexity does 111. google search does 4.9 same web, completely different hunger depending which crawler shows up i manage an ecommerce site. bing ai citations jumped from 52/day in may to 117 in june. june 22 alone hit 277. timing lines up with cloudflare's crossover close enough that calling it coincidence feels willfully blind cloudflare just shipped a monetization gateway this week machine-to-machine payments, stablecoin micropayments, agents paying per access. not announced. live. already running the part that should actually worry you: agentic traffic (agents completing tasks, not just crawling) was only 1.7% of bot traffic in 2024. but it grew 7,851% in a year. the headline crossover is here the part still accelerating is the part that buys things you don't need every page agent-readable you need the time-sensitive ones. pricing, availability, current state. those are the pages that actually get fetched when an llm goes live mid-conversation. everything already in the model's weights answers cold, no site visited, no citation earned i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  opossum in blossom 🏳️‍⚧️ трансгендерная мышь (@ok_im_merging) reported 20 minutes ago

  @nostalgiacore Cloudflare be like: we should build the entire encryption system on this ****

• 
  Build Wealth After 40 (@BuildAfter40) reported 20 minutes ago

  @StockSavvyShay @FuturumEquities Cloudflare is interesting because it sits where traffic, security and AI agents increasingly meet. But the megacap argument still comes down to monetization. Handling more of the internet is powerful; turning that position into durable revenue growth, margins and cash flow is the test.

• 
  Vivek Kotecha (@vbkotecha) reported 24 minutes ago

  Cloudflare's Will Papper, formerly of Syndicate, is leading the agent payments initiative. His team built a system that lets any Cloudflare customer charge for web pages, APIs, datasets, and MCP tools using x402. The pricing model is surgical. Per-verb pricing. Charge differently for GET vs POST. Vary price by task complexity. Set rules via dashboard, API, or Terraform. When an unauthenticated agent hits a premium route, Cloudflare intercepts the 401 and converts it to a 402 with payment terms in the response header. Settlement in USDC or Open USD. Sub-second. Negligible fees. Sellers can redeem for fiat. The origin server never sees an unpaid request. The payment happens at the CDN layer, in 330+ cities, before the request even reaches your infrastructure. This is not a payment feature. This is the internet's reverse proxy becoming its tollbooth.

• 
  Evan Oslick (@eoslick) reported 28 minutes ago

  @DanielMiessler I still think I wasn’t clear. I have been pushing for 402 being used and this type of strategy for a long time. My issue is with the reach that Cloudflare has there is significant risk in them doing it. I don’t accept “it’s not there now, something is better than nothing” is a merit counter point to handling the risks to those Cloudflare currently serves. Hey, look, we don’t like your content…. We’ll change the income percentage you get.. Hey, yeah, look, you buy this service we’ll decrease our service charge to you… Separations of duties is a recommendation for a reason. Monopolies are prevented (well supposed to be) for a reason.

• 
  Stabledash (@stabledash) reported 28 minutes ago

  AWS and Cloudflare have quietly turned on a new option for any publisher running on their infrastructure: the server can return an x402 payment code instead of a flat 404 when an AI bot hits their content. .@_rishinsharma, Head of AI Growth at @Solana Foundation, breaks down what that unlocks: "Say I have a blog, and it's hosted on AWS Bedrock, and I just write about financial data or something like that. By default, AWS will block bot traffic. So if they detect someone is a bot, they'll just block that traffic. If someone from an LLM is trying to get something I've written about, it'll just return a 404. It can return a 402, I can put in a wallet address, and I can actually get paid and monetize that traffic." His read on why subscriptions already lost this audience: "I think for content publishers, this is gonna be a new way for them to reach an audience, because two, three years ago, I was subscribed to a ton of Substacks, where I was paying for a couple of them too. It felt like a way to get alpha. Now I can't imagine, I don't wanna open my email and go to a Substack, and maybe this is an attention deficit thing, but I can't even read long form content. What's the important part? Skip to that one."