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:

• 
  TBPN (@tbpn) reported 5 minutes ago

  FULL INTERVIEW: Cloudflare CEO @eastdakota joins TBPN to discuss why agent traffic has surpassed human web traffic, the company's acquisition of VoidZero, and why concerns about data center water usage are overblown. 2:13 - Why today's infrastructure can't support billions of AI agents 7:38 - Bot traffic vs. human traffic 11:51 - Long-running AI agents are the future, not chatbots 15:15 - The 3 reasons companies are moving AI inference to the edge 17:29 - On concerns about data centers using too much water 19:41 - Matthew Prince on lawsuits from Spain and Italy over piracy 22:10 - Why being a public company is healthier than taking VC money 28:57 - Matthew Prince on hiring 1,111 interns

• 
  Aryan Esfandiari (@arian88) reported 8 minutes ago

  Never push to main on a Friday @Cloudflare

• 
  Nathan (@nthglsn) reported 11 minutes ago

  @mofeeni @Cloudflare damn...

• 
  Sarthak Rawool (@sarthakcore) reported 11 minutes ago

  my tool graveyard: Notion for project management. too complex. back to markdown. Obsidian + Hermes for a knowledge vault. never found the use case. Super X for managing my account. replaced it. Codex for writing code. now it only runs test passes. every tool i abandoned taught me the same thing: if it doesn't fit how i actually work, it dies. current stack that survived: Claude Code 6+ hours/day. Claude Design for UI. PlanetScale. Dodo Payments. Cloudflare + GitHub Actions. the tools that stick are the ones i forget i'm using.

• 
  Shane | GTM Engineer (@shanefgtm) reported 12 minutes ago

  @KeithRamphal I’ve been working on some deeper signal work involving cloudflare workers/scraping and i get hit with restrictions, have to roll back to opus for that stuff

• 
  Jay.TL (@JayTL00) reported 12 minutes ago

  Both Visa and Mastercard launched agent payment rails this week. Zero real transactions have cleared through either. Visa Intelligent Commerce gives AI agents tokenized card credentials — your agent gets its own identity on a network processing 300 billion transactions a year. Mastercard's Agent Pay for Machines (AP4M) went further: agents paying other agents, machine-to-machine, no human in the loop. 30+ partners including Stripe, Coinbase, Solana, Polygon, Aave, Cloudflare, Ripple. The optics are undeniable. Two payment networks that move $30 trillion+ annually are building for a world where the buyer isn't human. But the substance is mostly slide deck. Three things the press releases don't mention: 1. Zero production volume. No transaction counts, no throughput benchmarks, no live merchant integrations with actual agent checkout flows. The 30+ AP4M partners are logos on a launch graphic. Every "early adopter" is testing in sandbox. Visa's own CFO Chris Suh said plainly: agentic commerce and stablecoins "won't pay off in the next six months, but could over the next six years." That's not a launch. That's a forward-looking statement with a PR budget. 2. The authority problem has no answer. Payment rails move money. They don't decide who's allowed to move it, when, or how much. When your agent spends $2,000 on cloud compute from another agent, who set that limit? Who audits it? Who's liable when the agent hallucinates a purchase? Visa's model (human-delegated tokens with spending caps) at least has a governance story. Mastercard's machine-to-machine model has a governance vacuum. The "fraud detection" and "spending limits" mentioned in press releases are features that don't exist in production yet. They're on the roadmap — which is where most agent infrastructure lives in 2026. 3. Five competing agent payment protocols launched in 2026. ACP. x402. MPP. AP2. AP4M. Each with different trust models, settlement layers, and identity frameworks. The fragmented landscape is a feature for early experimentation and a disaster for adoption. Merchants won't integrate five agent payment protocols. Agents won't carry five wallets. The consolidation hasn't started because nobody has enough transaction volume to matter. The real signal isn't the technology. It's that the two largest payment networks on Earth decided in the same week that agent commerce is real enough to allocate engineering resources, partner integration teams, and public marketing budgets. They're not building because agents are buying things today. They're building because if agents ever do buy things at scale, whoever owns the rail owns a tax on autonomous commerce. The bet is simple: the marginal cost of building agent payment infrastructure in 2026 is tiny compared to the cost of being locked out of a new transaction layer in 2028. Whether that bet pays off depends on a question none of these announcements address: what happens when the first agent makes a $50,000 mistake at machine speed on a rail designed for that speed? That's not a technology problem. It's a liability problem. And nobody has underwritten that policy yet.

• 
  TBPN (@tbpn) reported 13 minutes ago

  The smartest thing @eastdakota did before Cloudflare's IPO was offer shares to people who could help the company in the future. "The most clever thing that we did [for the IPO], and this was advice that I got from Qualtrics Co-Founder Ryan Smith, was he said, 'What are you doing about friends and family?' because you can take 5% of the IPO and allocate it to friends and family. I said we weren't going to do it." "He said, 'No, you're thinking about it wrong. Think about the people, who if they owed you a favor, could make a meaningful difference in the future of Cloudflare, and then offer them the ability to invest in the IPO.'" "I said, 'Some people are going to have conflicts.' He said, 'It doesn't matter. Even just the fact you offered it, even if they can't do it, they'll always remember that super fondly.'"

• 
  Trent (@TrentBuysValue) reported 18 minutes ago

  @LazyPepper @AmoremPatriae @PaulineHansonOz More likely a DDOS attach to prevent people from donating. Looks like Cloudflare has just been added to help mitigate it.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 18 minutes ago

  @Arref000 @NovaXCode the whole path: $5 vps, a single docker compose or dokku, point cloudflare at it, done. write it down once and "deploy" stops being a 49th-hour decision.

• 
  Samuel Archibong (@ArchibongS90116) reported 19 minutes ago

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

• 
  Smakosh (@smakosh) reported 19 minutes ago

  Yo @Cloudflare what's the point of your status page if it doesn't report that your stuff is down?

• 
  Puneet Patwari (@system_monarch) reported 20 minutes ago

  Caching at the CDN? Easy. Knowing when to clear it? That's where it gets fun. Scenario: you deploy a bug fix. API now returns corrected data. But CDN edges worldwide are still happily serving the old, broken response. And they'll keep doing it until the cache expires. Three ways to deal with this: 1. TTL-based expiry (the simple one) Set a timer. Content expires automatically. Some rules of thumb: - Changes every few hours → 5 min TTL - Changes daily → 1 hour TTL - Versioned assets (app-v2.3.1.js) → 1 year (filename changes with each version, so it doesn't matter) The tradeoff: if TTL is 60 seconds, users might see stale data for up to 60 seconds after a change. That's it. For 80% of use cases, totally fine. 2. Purge API (the manual override) Force-clear content from all edges immediately. Every CDN has this. CloudFront invalidations, Fastly instant purge, Cloudflare cache purge. The catch: if you purge 10,000 URLs after a deploy, all edges suddenly have empty caches. They ALL go fetch from origin at the same time. Thundering herd. Your origin gets crushed. Good for: targeted fixes on a few URLs. Bad for: bulk clearing after every deploy. 3. Stale-while-revalidate (the one you should actually use) This is my go-to for almost everything: Cache-Control: max-age=60, stale-while-revalidate=30 What this means: - Content is fresh for 60 seconds - After that, serve the stale version instantly to the user - But in the background, go fetch the fresh version from origin - Next user gets the updated content User never waits. Ever. Freshness catches up within seconds. No thundering herd. If you take one thing from this entire thread: use stale-while-revalidate. It fixes 90% of CDN cache headaches.

• 
  Maximum YT (@Maximum__YT) reported 25 minutes ago

  @ppennguu Seems like it’s Canada wide issue, cloudflare is also down in Canada including telus

• 
  Daniel Romero (@HyperTechInvest) reported 26 minutes ago

  Cloudflare $NET believes CPU demand could 20x with AI agents $AMD $INTC $ARM The company argues that AI agents could create a massive CPU/server infrastructure problem if every worker runs multiple agents using today’s cloud model The math: US: ⏩ 100M knowledge workers × 1 agent each ÷ ~10 agents per CPU = 10M CPUs Global: ⏩ 1B knowledge workers × 10 agents each ÷ ~10 agents per CPU = 1B CPUs Cloudflare compares this to current global server CPU production of only ~35M–45M per year, implying the current approach could require ~20x current annual CPU production $NET is pitching Agent Cloud as a solution This is how it would work: 1. Dynamic Workers instead of full containers Agents can be spun up on demand and put back into cold storage when idle, avoiding one heavy always-on container per agent 2. Durable Objects for state Agents need memory/state for tasks, files, sessions, progress, and tool outputs. Durable Objects give each agent/app a stateful object with local SQLite-backed storage 3. Workflows for long-running agents Agents may run for minutes, hours, or days while waiting for approvals, retries, external events, or scheduled steps. Dynamic Workflows allow these processes to hibernate between steps instead of constantly consuming compute 4. Project Think / Agents SDK Project Think adds agent-specific primitives like durable execution, crash recovery, checkpointing, sub-agents, persistent sessions, and sandboxed code execution 5. Sandboxes only when full computers are needed For coding agents or tasks requiring bash, ***, file systems, browsers, or arbitrary binaries, Cloudflare still offers Sandbox containers. But the idea is to use them only when necessary, not as the default runtime for every agent

• 
  Jason Fleagle (@jjfleagle) reported 27 minutes ago

  @Cloudflare The useful frame is the operating loop, not the AI label. If agents can sense and recommend but cannot validate, escalate, log evidence, and support rollback, they are still demo tools.