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:

• 
  Alphonse (@Alphonste) reported 4 minutes ago

  Day 1 of asking why cloudflare doesn't have a first class postgres service within a private network

• 
  Sam (@bySamBoffa) reported 4 minutes ago

  I swear, Cloudflare products might be good as hell idk...but there are so many fragments and "idk, wtf is this?" and the docs man...

• 
  Ross (@402Signal) reported 8 minutes ago

  One nuance to this 93% figure - its dollars settled. @Algorand x402 settlements recently jumped ~30x in 5 days, while @solana has also seen strong payment growth. More txs with fewer dollars may actually be the machine-commerce signal. Agree on @Cloudflare. Q4 should test whether distribution turns into repeat paid usage. $ALGO $SOL

• 
  Cuong Thach (@cuongthach_) reported 14 minutes ago

  Good docs reduce support tickets. Great docs drive revenue💸 Rewriting nearly 100 pages from scratch wasn't easy, but the ROI is clear: 🔹Reduce churn rates 🔹Boosts sales conversion 🔹Build brand Sneak peek of the new @bepublish documentation powered by @Cloudflare Nimbus below 👀

• 
  Shraddha Bharuka (@BharukaShraddha) reported 15 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Lý Quang Tùng (@LQuangT60430837) reported 16 minutes ago

  Hi @Cloudflare, I'm being wrongly billed for R2 storage deleted a year ago. Opened ticket 02264237 a week ago with no reply, and my account faces suspension on 26/08. Can someone please escalate this to the support team? Thanks! PS: Past tickets were never answered either.

• 
  AI Genesis (@AIGenesis_) reported 20 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Onramp (@OnrampBitcoin) reported 21 minutes ago

  More of the internet's traffic is now agents than humans. Cloudflare expects a thousand to one within five years. The whole web runs on you showing up to look at an ad. If a model reads the page for you, nobody shows up and nobody gets paid. The fix has been sitting there unbuilt since the nineties.

• 
  Azad Satkarni (@7karni) reported 21 minutes ago

  @Cloudflare "running your mouth on security but you use network=hos-" dont worry about it kitten.. i have fixed it..

• 
  Fernando Dilland (@fernandodilland) reported 23 minutes ago

  @venkateshdotdev A CAPTCHA token (such as Cloudflare Turnstile) should be required in the header or body of registration and login endpoints, with the server validating it on the back end to ensure it is valid, thereby preventing a large portion of these attacks.

• 
  Aaron Boodman (@aboodman) reported 24 minutes ago

  Think of DOs by analogy to a serverless function. A better (and much funnier) name might have been "serverless objects". A "serverless function" is a stateless javascript program you upload to, say, Vercel. The external interface is a function. It is reachable at a URL. You send a request to the URL, Vercel instantaites your program, sends the exported function the request, gets the function result, send the result to you as an HTTP response, then destroys the program. DOs are exact same thing, but stateful. You upload a JavaScript program to CloudFlare. The external interface is a *class*, not a function. DOs are reachable at a URL. You send a request to the URL and CloudFlare invokes your program, instantiates your class, and sends a particular method on the class the request, gets the result, and send it to you as an HTTP response. So far, just a more complicated version of serverless functions. The difference is that CF keeps that class running for awhile. If another request comes into same URL, CF routes it to the same running program and the same exact JavaScript object in memory. So you can keep state in that JS objects across invocations. That's it, that's the whole pitch. These little javascript programs are low-power (last I looked max ram was maybe 1GB?). But they are cheap to run so you can have zillions of them. This makes them a very useful primitive for certain kinds of problems, like say chatrooms, multiplayer games, etc.

• 
  thePodKAS (@thePodKAS) reported 24 minutes ago

  I have an idea 💡 You build it ✨ If it makes profit Send some to cx312.kas Here it is The first decentralized CLOUDFLARE replacement The first cheapest network ever that does the same But never shuts down like it always happens with AWS or CloudFlare Yeah Oh yeah $KAS 🍀

• 
  Adam Szaloczi | DataBard (@AdamSzaloczi) reported 30 minutes ago

  @a_shimanski @Namecheap @Cloudflare I never experienced any downtime. But the whole ecosystem is so bloated and the admin process is confusing.

• 
  VJay (@nceevij) reported 32 minutes ago

  I’ve spent a good amount of time over the past few months in conversations and brainstorming around designing an agent economy protocol, particularly agent-to-agent payments. Nothing has shipped yet. It’s still early. But one problem from those conversations keeps coming back to me: Looping payments. Agent wallets and spending caps are already starting to ship. Cloudflare rolled out its own approach this month. Most of the safety model around these systems rests on a fairly simple assumption: Each agent’s financial risk can be controlled independently. I think that assumption breaks once agents start paying other agents directly. Here’s the problem. Imagine: Agent A → Agent B → Agent C → Agent A Each agent has a spending cap. Each individual transaction is valid. Each agent stays within its own limit. And yet the system can continue circulating money in a loop while producing zero useful work. That loop could potentially be triggered by: • Prompt injection • A pricing or settlement bug • Misaligned incentive logic • Agents recursively purchasing services from one another The problem is that most current safeguards operate at the wallet level: • Spending cap • Merchant allow-list • Maximum transaction size • Per-transaction authorization Those controls answer: “Is this agent allowed to make this payment?” They don’t necessarily answer: “What is happening across the payment graph formed by multiple agents?” And that distinction becomes important in an agent economy. Interestingly, this isn’t really a new class of problem. It looks a lot like an old distributed systems problem wearing a new mechanism: Deadlock. Model each agent as a node. Model each pending or dependent payment as a directed edge. Now instead of looking only at individual wallet state, look at the graph. If: A is paying into B B is paying into C C is paying back into A you have a cycle. Distributed systems have dealt with similar global-state problems for decades. Techniques such as Chandy-Lamport distributed snapshots allow nodes to capture a consistent view of a distributed system without requiring everything to stop simultaneously. Applied to agent payments, the idea could look something like this: Agent Wallet = Node In-flight Payment = Directed Edge Payment Network = Dynamic Graph Then continuously inspect that graph for suspicious cycles rather than evaluating every wallet completely in isolation. And importantly, detecting a cycle doesn’t necessarily have to mean: “Block everything.” It could mean: Freeze the specific loop → identify the participants → inspect the intent → release or terminate one leg of the cycle. Similar to how databases handle transaction deadlocks rather than allowing the entire system to grind to a halt. Why does this matter now? Because agent-to-agent payments are moving from demos toward production systems. As agents increasingly become economic actors that can hold balances, buy services, negotiate prices, and pay other agents, wallet-level controls alone may not be enough. We may need graph-level financial safety primitives. The question I keep coming back to is: Is per-agent spending limits + payment-graph cycle detection enough to prevent looping payments? Or is there a deeper failure mode that even this architecture misses?

• 
  R (@dnagabut) reported 34 minutes ago

  Cloudflare announced programmable wallets built for AI agents, with preset spending limits and merchant restrictions in the design. Nothing has shipped yet. Right now you can reserve a handle. Funded account wallets, virtual wallets and programmable agent spending are all due in the coming months. Read the feature list again, because it is a permission model, not a payments product. The moment you let an autonomous agent buy things, you inherit a problem crypto has been failing at in public for years. How do you grant a program the ability to spend without granting it the ability to spend everything? DeFi's answer was token approvals. The result is a very long list of drained wallets where nothing was hacked at all. Someone approved unlimited spending to a contract years ago and forgot. So Cloudflare's version is delegated authority with a cap and an allowlist, plus anomalous-spending alerts that escalate to a human. Sensible. Also the bare minimum. And these are stablecoin wallets settling over x402, so this isn't a payments industry learning from crypto's mistakes. It is crypto. The layer above it is still wide open. An agent that can be talked into a purchase by hidden text on a web page is still an agent that can be talked into a purchase. Caps limit the blast radius. An anomaly alert only fires once the spending already looks strange. Neither one touches the trigger. Follow @dnagabut if you like your tech news with the catch included.