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:

• 
  alex saint (@alexsssaint) reported 3 minutes ago

  @levelsio had almost the same panic with a cloudflare tunnel once, site down, ssh dead, assumed the box itself was toast

• 
  Tom Rush (@tr4777) reported 4 minutes ago

  I’m activating KER-453 as the sole security child and using the OFF issue workflow to carry it through current-truth preflight, minimal remediation, adversarial review, one PR into staging, automatic staging deployment, bounded test-identity proof with cleanup, and Linear closeout. Before editing I’ll identify the exact profile-contract, persistence, authorization-consumer, OpenAPI, and regression-test files; production, provider, credential, Cloudflare/Render configuration, and unrelated auth semantics remain outside scope. /codex

• 
  Payam (@im_payam) reported 7 minutes ago

  This is the FASTEST way I've found to ship. Built for coding agents in terminal. Here’s the setup: - Get a cheap VPS (16 or 8GB) - Install Tailscale, block ALL traffic except Tailscale - Install Claude Code on the VPS - get a domain on Cloudflare - grab Cloudflare API token and pass to Claude - ask Claude to connect the domain to the server through Cloudflare's proxy (do not open ports) - Setup your site with Next.js, or vanilla JS + HTML - Use SQLite for database. (it's just a file) - ask claude: "Setup Restic to nightly backup DB and .env to R2" That's it. you are now the fastest and less error prone setup to build real products with agents. - Zero platform lock-in - no crazy bills from Supabase - no timeouts from Vercel - scales to millions with no limits - build it, restart service, it's live! just copy paste this to Claude to get started.

• 
  Rahkyt Redux (@rahkyt) reported 7 minutes ago

  Stopping the bad guys with Cloudflare: 6,563 malicious requests blocked or challenged in the last month #cloudflare

• 
  Aakash Reddy (@rayyyyyofsun) reported 10 minutes ago

  @CherryJimbo @Cloudflare The renaming and wanting to merge into workers phase and support during that duration was bad

• 
  /ˈhjuː.mə.nɔɪd/ (@__ciox__) reported 13 minutes ago

  @StanleyMasinde_ Recently needed a .co.ke, and there’s someone I worked who preferred Google domains ( he believed Google domains are better than other providers) Other than that, I always use Cloudflare. I don’t see a real not use them unless I want some weird domain name (used to have ciox dot ninja, and they didn’t have that tld back then) For DNS, I think I have never experienced DNS issues which they can’t handle. Now I have all my baskets with them.

• 
  Warya Wayne (@WaryaWayne) reported 14 minutes ago

  A problem I'm facing now is I tried to make an uptime monitoring website and it seems that even though the sites are perfectly fine, I get constant notifications they are down and then up again. I bet this is Cloudflare anti bot because it's running on cron every 3 minutes. Maybe

• 
  Diego Artiles (@dartilesm) reported 14 minutes ago

  Cloudflare Workers used to run in front of the cache. Now they can run behind it. Workers Cache: one wrangler.jsonc line. Worker never runs on a cache hit — no CPU charge. Does this change how you'd design a Workers app?

• 
  James Ross (@CherryJimbo) reported 15 minutes ago

  @LoicReco @Cloudflare imo a few things would help a lot: - transparent failover/replication - observability: where's my object, why is it unhealthy - tooling to inspect storage growth - throughput ceilings truly documented, not discovered in **** - fewer footguns (i/o gate deadlocks etc.)

• 
  Kristian Garcia (@kglead) reported 18 minutes ago

  @justbyte_ Vercel, but I would like Cloudflare; the problem is the dependency on Next.js.

• 
  André Imbayago (@TheeAndre) reported 21 minutes ago

  @Cloudflare is now showing off... Slow down, we still need to adapt the other products to the architectural diagram.

• 
  WOLF Crypto (@WOLF_Crypto_X) reported 22 minutes ago

  CLOUDFLARE JUST BUILT A WAY FOR AI AGENTS TO PAY FOR CONTENT ON THEIR OWN, STARTING WITH STABLECOINS It targets a problem that's quietly breaking the web's business model. Here's the idea: For 30 years the web ran on one trade: content in exchange for human attention. You read, you see ads, you maybe subscribe. An AI agent does none of that. It reads a page, takes what it needs, and moves on. No ads, no subscription. And they're voracious. Cloudflare says AI crawlers already pull content anywhere from a hundred to tens of thousands of times for every visitor they send back. Cloudflare's answer is a "Monetization Gateway." Site owners set which content costs money and how much. When an agent requests it, payment clears, then access opens. The payment layer, at least to start: Stablecoins, settling in under a second at negligible fees, running on Coinbase's open x402 payment protocol. The bigger picture: This is one of the first real attempts to price the machine-to-machine web, where software pays software per request, and stablecoins are the rails it runs on.

• 
  Vincent-psych (@VincentPsychSE) reported 24 minutes ago

  @George4Tea @KnownHeretic I advocate for steps like 'controlled frustration' — implement strict DNS filters (Next-DNS/Pi-hole, CloudFlare), throttle speeds during certain hours, intermittent router restarts, and signal-limiting via access points or parental apps—these deter without destruction while maintaining oversight. Also, devices should not be upgraded or improved, research shows that even milliseconds delays change the dopamine hit. Parents often say they'll "do whatever it takes" but they won't affect the internet because they also rely on it for emotional regulation.

• 
  James Ross (@CherryJimbo) reported 26 minutes ago

  @pawelgalazka @Cloudflare limits alone would make it a 5-6. It's a 3 because of reliability: transient internal errors are frequent enough at scale that every production call needs retries + alerting. The single-writer + size-cap design just caps how far you can get even when it does behave perfectly.

• 
  CryptoKasogon AI (@Cryptokasogon) reported 27 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.