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:

• 
  Coobyk (@Coobyk_) reported 4 minutes ago

  @Riric65off @theo Btw I haven't mentioned it but they have personal beef with Cloudflare and want to charge them too instead of just the consumers so Cloudflare traffic is really slow during the day and sometimes it's completely blocked

• 
  veucit (@Njbbear) reported 8 minutes ago

  @AstaRoth1486655 the requirement was here from the start, otherwise even 2 people using the service on a shared cookie would just rate limit all the time use your brain. it’s not possible unless i somehow get higher ratelimits or tons of accounts to use for the website and $10/mo is very affordable it’s just called monetizing. I need to pay for cloudflare plans, and other plans for services needed for indexing and embedding asset information

• 
  RifatOfficial (@RifatOfficiall) reported 12 minutes ago

  @nguyenthambt @Cloudflare Yeah it costs nothing and worst case you just get the name.

• 
  Sky (@0xrichboy) reported 14 minutes ago

  @RifatOfficiall @Cloudflare Securing your preferred handle early is never a bad idea.

• 
  Stark (@Stark_of_Zenon) reported 15 minutes ago

  Zenon Network isn’t competing with cRyPTo. The stakes are on the scale of publilc infrastructure. ai slop research on $ZNN devolve into trading-volume, charts, and momentum-signal comparisons. That’s the wrong lens. Project Zeno specs a Domain Settlement layer — a runtime-agnostic settlement surface where isolated execution domains run off-chain and anchor their commitments, custody, and state back to L1. Think of it as the settlement and verification layer in a broader stack, the kind of foundational substrate that higher-level systems (agent workspaces, sandboxed apps, company-context platforms like Cloudflare OS) could eventually sit on or interoperate with — not as a peer competitor to typical smart contract execution chains.

• 
  Sushant S (@SikareSushant) reported 16 minutes ago

  @arpit_bhayani Cloudflare AI assistant sucks hope they first fix that.

• 
  AX1 (@ax1vc) reported 17 minutes ago

  Coinbase made the specification freely available. Cloudflare proved that was the costly piece of it. HTTP 402 appeared in the spec as far back as 1997. For nearly three decades, it was an answer without a sequel: the server would reply "Payment Required", and there would be no established protocol of the follow-up. Coinbase wrote the sequel, calling it x402, and making it open. The name is literal: an extension of code 402, the sequel to a thirty-year-old status code. Making a standard freely available is the way to get the larger player to adopt you. The value was never the spec itself. Coinbase runs a facilitator, and Base is their chain. The spec was free, because the settlement was the product. It worked. Last September Cloudflare joined them in forming the x402 Foundation, and yesterday they announced the addition of agent wallets on top of it: what is live now is a handle at cloudflarepay, a human-readable identifier linked to the agent's key. The standard was adopted by the company sitting in front of more of the web than any other. That September post contains the portion worth reviewing again. Along with the announcement of the foundation, Cloudflare proposed a deferred scheme within x402: the client signs the HTTP message signature, the server delivers the resource, settlement aggregates later, either using traditional rails, or via stablecoins. And their own description of the handshake step says outright that no blockchain is involved. Notice what it implies. The protocol still supports per-request settlement onchain, nothing was removed. There are several payment schemes within x402, and the server chooses which one to offer in the 402 response. Choice of rails moved from the protocol itself to the operator of the endpoint. The company in front of most endpoints demonstrated which scheme it designed for itself. There is nothing wrong with any of those actions. Suggesting schemes is what members of an open standard do. Coinbase chose openness to be the weapon precisely because it was the one weapon a larger player had to accept. The same mechanism which helps you to get adopted takes away your settlement. Where the settlement goes, the record follows. Onchain payments on a per-request basis are transparent for everybody. Batched behind the signature, they reside in the logs of whoever has validated it. Coinbase's counter-bet is real: batched settlement between strangers still requires a neutral unit both sides trust, Cloudflare's wallet is denominated in stablecoins, and not credits, and even the volumes may find their way onto the rail eventually regardless of which handshake carries it. Two observable factors will determine it. Will the deferred payment make it to a major update of the specification? And how much pay per crawl will charge once the private beta ends? We run our agent wallets on Base, so it is not just a spectator issue. Open standards help you getting adopted by companies larger than you. Adoption and settlement are two separate prizes.

• 
  Neko Ninja (@NinjaNeko42) reported 17 minutes ago

  filling profiles with one eye open in morning for backlinks sees captcha verification copies it into terminal cool malware got in it asks keychain access next cancels 1 time prompts again whole eye opens this is fuking malware kills background process and delete its files and drop connections Good morning never do **** when u just woke up copying captcha thing into terminal was most stupid **** lol #malware these domains are malwares i have thrown out in 2 minutes @Cloudflare topbilliondirectory , stv4ec5 , sea6km3y.nesplowell , nesplowell these all attackers came from ur front buddy hiding their IPs behind your servers i will report it later on ur portal

• 
  Simple Mining (@simpleminingio) reported 23 minutes ago

  Cloudflare just gave AI agents wallets to store stablecoins. Until now agents could talk, plan, browse but they couldn't pay for anything without a human swiping a card. That's the shift. Software with its own wallet can now buy an API call, hire another agent, or settle a bill without asking permission first. Which means the interesting problem isn't capability anymore. It's authorization. Every fraud model built for humans clicking buttons assumes a human is clicking the button. Once the buyer is a script with a balance, the whole trust chain gets rewritten. Cloudflare just decided who writes it first.

• 
  jem is looking for a job (@sheherenow_) reported 27 minutes ago

  I've been building Trails ~ a personal project intelligence platform that keeps track of all of the 1000 projects you work on across harnesses/models/computers and reminds you what you've been doing anyway. it's all self-hosted/open source on your own network and i'm deciding what that means for how I handle LLM inference. I really hate to build anything with """user accounts""" and imho data is sensitive enough that i don't want to touch it, but inference for summarization is currently done on (my) cloudflare worker i could just do BYOK or local summarization but that feels like it will have way more complex onboarding (but maybe that's ok?) would love thoughts/prayers bc this is the part of the thing i hate the very most

• 
  Cockpit (@cockpit_xyz) reported 32 minutes ago

  🚨JUST IN: Cloudflare has unveiled Cloudflare Wallets, giving AI agents programmable stablecoin wallets to autonomously pay for APIs, digital content, and online services. The wallets support spending limits and human oversight, with stablecoin micropayments powered by Coinbase's x402 protocol. CC: @cointele

• 
  Makoto | ..... (@mareni_musashi) reported 32 minutes ago

  @DmytroKrasun In many cases, I would agree. Then I have an experience like just earlier today when I needed to send a deck out for a stealth project we have underway. I want to have strict controls over who can view the deck and how. Normally, DocSend is the go-to. Instead, I just spun up a subagent, gave it both general and specific directions as to the features I wanted and access to the environment we deploy into and how I wanted to manage it. An hour later, I have a DocSend that is actually better than DocSend hosted for free on Cloudflare. It is very secure (I directed this part) and can be completely controlled from a cli on my computer (so no admin dashboard needed -- call it AI native). Colleagues tried it and were like "wtf, this is amazing!" It will not require much maintenance at all because we are the only consumer -- and here is where your last argument fails. Not saying ScreenShotOne is something that falls into this category, but there are defo a million (now way overpriced) SaaS tools that do.

• 
  Julian Engel (@julianengel) reported 33 minutes ago

  I took my own app down mid-development by hitting Cloudflare KV's daily write limit. Nobody tells you the free tier has a cliff until you're at the bottom of it. Cache reads, batch writes, respect the quota you forgot existed.

• 
  Gulf Air (@GulfAir) reported 34 minutes ago

  @amitxgupta @Cloudflare Hello! If Captcha does not load, please press F5 on your desktop device at that exact moment, or reload it, then it should appear. If the issue still persists you may try either from a different internet browser, internet connection or by using our mobile app!

• 
  linie (@linie_oo) reported 34 minutes ago

  @ninedol first it was cloudflare, now it’s claude this one is not that crucial to be down at least