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:

• 
  Gennaro (@fourweekmba) reported 3 minutes ago

  Mastercard just launched Agent Pay for Machines. AI agents can now buy things autonomously. micropayments down to fractions of a cent. machine-to-machine. always on. 31 partners: Coinbase, Stripe, Adyen, Cloudflare. settlement: cards + stablecoins via Polygon, Solana, Base. Apple gave agents eyes and hands. Mastercard just gave them a wallet.

• 
  Colin Charles (@bytebot) reported 4 minutes ago

  Thin is in. Thin clients. The network is the computer. Oracle actually allowed the Sun Microsystems trademark lapse, and Cloudflare now owns it.

• 
  David Siewert (@david1gp) reported 5 minutes ago

  Cloudflare Pages not working? Or I the only one who is affected? ```json {"text":"POST /pages/assets/upload -> 502 Bad Gateway"},{"text":"Cloudflare Ray ID: a0a71049ef6c7049-FRU"}],"kind":"error","name":"APIError"} ``` @CloudflareDev

• 
  Jay.TL (@JayTL00) reported 6 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.

• 
  Interfacing Linux (@intlinux) reported 7 minutes ago

  Cloudflare Dashboard is down and now Facebook is exploding. Going to be an interesting Friday.

• 
  Tushar Dwivedi (@tush_2708) reported 11 minutes ago

  @kritikakodes For 50 users, get an adult "chhotu" to do the job that the system is supposed to do. A chhotu to run and call the cab. A chhotu to run and take documents to your CA, download and email, download and print, scan and email, whatever be the pain point. For 50 users, you need a validated business model, not a software system. My milkman caters to more users than this. If interviewers ask stupid questions, they should expect stupid answers. For 50 users, you can choose the worst design decisions intentionally and can still justify them. 1. Database Schema: "I will store all the data in an xlsx file, and will reread the file every time an API request comes. I will use another .lock file to control access when writing new data to this file" But what about "linearly degrading performance?" "What degradation? My API will still respond within 200 ms to all your 50 users" 2. Cloud deployment strategy: "What cloud deployment? I will run this system on a Raspberry Pi connected to a hard disk, with a cron job to do backups on 2 other hard disks connected to another Raspberry Pi. And I will set up Cloudflare tunnel to it, for your 50 users" 3. Disaster control? "I will use this 2000 rupee router power backup device"

• 
  topmass (@topmass) reported 12 minutes ago

  @pushmatrix of course - I will note / fix any dependencies there in the readme, the cool thing about the project is, you'd sign up for cloudflare free and could muck about all day long with projects and tools and toss some AI in there for free too, The workers paid (5 dollar plan) would add almost infinite request usage and a lot more ai usage too - durable objects are a nice stateful home for this project too so I couldn't resist

• 
  chan (@chantastic) reported 14 minutes ago

  @jeflopo I'm annoyed because the frontend of these sites has to do SO little. all the serious work is Cloudflare Workers, Queues, AI Gateway, and Durable Objects. so it's just an annoying speed bump to have UI framework issues

• 
  Roy (@__roycohen) reported 19 minutes ago

  @tekbog Damn even I got into Google Startups, I actively think that I got in out of sheer luck at this point cause everyone else denied (including Amazon/Cloudflare)

• 
  MBrant75 (@MBrant75) reported 20 minutes ago

  @nickSfishes315 @JackDan110 Heh Really? Cloudflare issue or something?

• 
  Jake (@JakeKing) reported 20 minutes ago

  Surprised to see that only 50% of internet traffic is now automated. the old "human good, bot bad" binary is dead. @Cloudflare scores every request 1-99 on behavioral trust instead.

• 
  Jeff Liford (@JeffLiford) reported 23 minutes ago

  @Cloudflare @CloudflareSys @CloudflareDev Cloudflare is operational again at this time, however I am encountering an issue with one domain name being redirected to an improperly spelled domain. Currently investigating root cause.

• 
  Sussycat Bloomberg (@LeSussyCat) reported 24 minutes ago

  @Cloudflare Put a smile on my face because atleast DDoS is using my ****

• 
  whizzy 🎭 (@lexzy07) reported 28 minutes ago

  🪙 Mastercard Launches AI Agent Payment System Mastercard has introduced Agent Pay for Machines (AP4M), a system enabling automatic payments between AI agents without human involvement. The service targets high-frequency micropayments that agents execute independently in the background. Early adopters include Adyen, Stripe, Coinbase, Cloudflare, OKX, Ripple, and around 20 other companies.

• 
  lylo (@lylo) reported 28 minutes ago

  Trying Cloudflare Email Sending (beta service) for password resets on Pagecord. So far, so good. Will result in faster delivery I think, and it's far cheaper than non-SES equivalents.