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:

• 
  Tsinoiz Itna (@TsinoizItna) reported 5 minutes ago

  @QuinnyPig @Cloudflare Try adding an IP access rule sometime... Google-level poor UI.

• 
  Tay 💖 (@tayvano_) reported 6 minutes ago

  @candyflipline No that’s not how the world works. Do you know how much malicious **** exists on Amazon? How often it’s used to harm? But Amazon is immune bc it’s not them. Same for Cloudflare. Google. Apple. Windows. GitHub. All of them lmao.

• 
  sam (@samgoodwin89) reported 6 minutes ago

  @Cyb3ristic Yes, @Cloudflare is notoriously bad at this. It's insane that a Cloud provider thinks it's ok to just release breaking changes to their API. We are pretty much running tests all the time because of Alchemy dev, so we just respond as quickly as possible. Not ideal.

• 
  That Boosted Snep 🔜 Megaplex (@witch_the_snep) reported 11 minutes ago

  @joesmith1457 @DoorDash_Help It looks like its cloudflare thats having issue. That who hosts doordash’s website

• 
  Victor (@echo_vick) reported 11 minutes ago

  I can’t seem to access CloudFlare using my MTN network, but it immediately opens once I switch to Airtel. Does this happen to anyone else?, is this common?

• 
  Bo Montgomery (@BoBilbo28) reported 13 minutes ago

  @Dr_Crossroads I think this is a part of my thesis for investing in $NET. They are helping websites monetize the AI traffic that crawls their content. @eastdakota has talked about publishers and others working with Cloudflare to help them monetize their content with this move away from no clicks.

• 
  surya murugan (@SuryaMurugan_) reported 16 minutes ago

  @elithrar @dok2001 @Cloudflare Please add support for r2 data localization in India. Cannot use r2 for any DPDP act complaint services. 🙃

• 
  Roy (@__roycohen) reported 17 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)

• 
  Jason Fleagle (@jjfleagle) reported 17 minutes ago

  @Cloudflare A 10x scan throughput gain only matters if the downstream loop keeps up: prioritization, owner routing, safe remediation, validation, and evidence that the fix actually reduced exposure.

• 
  Michael Heredia (@michaelheredia) reported 17 minutes ago

  What 'you own the deployment' actually means: Source code in your repo API keys in your accounts Hosted on your infrastructure (Cloudflare, your server) Customer data in your database You can hire any developer to modify it You can stop paying me and it keeps running

• 
  Sameer Khan (@sameerr_dev) reported 19 minutes ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  Jims (@JimsYoung_) reported 21 minutes ago

  Anyway, checking in at 20k registered users. 🎉 Some recent takes: — Agents are massively underestimated. Given how fast context windows are evolving, something like Fable can now grind on a task for a full day, fast and good. You can already offload the vast majority of your work to it. The real bottleneck is that most agent runtimes and multi-agent workspaces on the market are way too complex to set up, so the number of people who can actually use them is tiny. The ones who can are using them every single day, but even they keep getting bogged down by runtime and agent management. — One very tangible shift: a lot of legacy infra just can't keep up anymore. Cloudflare outages, for example, have gotten noticeably more frequent. Agent traffic to websites has already surpassed human traffic, and it's only going to grow from here. Infra needs a new foundation. I've got friends already building new switch programming, even chip-level protections. — Defining the problem clearly matters far more than execution. The longer I do this, the more I disagree with certain bets: a) "Agentic payments will necessarily be small-amount, high-frequency." Probably the most off-base one. Agents are going to take a meaningful chunk of transactions, regardless of size or frequency. Say an agent transfers money for you based on an invoice — the amount doesn't matter at all, it's just whatever the invoice says. No reason it has to be small. And frankly there's a whole class of demand here we never even anticipated. b)"Agentic payments must use stablecoins." Not strictly necessary. But a substantial portion will be stablecoins — it really depends on how you define agentic payments… c) "Agentic payment = using an agent to shop for people." Feels like there are ten thousand AI shopping assistants that can already do this — see Shopify's UCP — and after all this time, basically nobody uses it. A lot of the time people just can't articulate their own needs. We need much better ways to collect context. — A lot of the big players really are all talk, surprisingly slapdash. When we were running our security rotation, a prompt injection straight-up exfiltrated the agent wallet private key from a major company whose name starts with "S"… The biggest security problem in agent payments isn't in the payment — it's in the agent. Which is exactly why the right environment and guardrails matter so much. — Whether agents use cards is a genuinely interesting question. If you're ambitious enough, there's a real shot at building a new rail in virtual environments that kills the card networks entirely. At its core, payment is just an authorized, trust-based act of bookkeeping. What cards fundamentally provide is convenience — not having to type in a bank account, being able to complete a transaction at a terminal, a fixed network of transfer channels and information exchange. Every one of those things can be solved by agents instead. Honestly, you can let your imagination run wild here.

• 
  BornToLose💀🍀🏆 (@__BornToLose__) reported 25 minutes ago

  Spectrum can bite my ***, wdym 30mbps down is fine? Was really hoping it was just a cloudflare thing or something on my end but nope, I'm genuinely just stuck with the world's shittiest ISP and nothing I can do about it.

• 
  Shashwat (@theshashwat20) reported 27 minutes ago

  @Cloudflare Your domain checkout page needs some real transparency. Just bought a new domain. It showed $26.00 throughout the entire process. Got charged $30.68. The extra $4.68 in taxes was never mentioned once during checkout. Only found out via the invoice email. Please show the final all-in price (taxes included) upfront. It's a small change that greatly improves customer trust. Fix this.

• 
  Ozgur Ozer (@ozgrozer) reported 27 minutes ago

  Today I decided to archive some of my failed projects. I never made money from them so it's time to let them go. I spent more than a year and some money on these 5 failed projects but still it's not a lose. I learned a lot about idea validation. I started my indie hacker journey 2 years ago with Next AI Tool directory. I scraped the internet so the site wouldn't look empty. There were 46k AI tools in the website on launch but a couple of weeks later Google blocked the domain on the search results lol. I made my first internet dollar with AI Renamer so it teached me lots of things about making a useful product, educating and supporting customers, marketing etc. It made $7k in the last year and still making a little so I'll keep it. Now my focus is on Grape, the AI note taking app. I only made one post on Reddit about the beta version of desktop app and since then it made 5 lifetime sales and currently has 1 active subscription. Now working on the mobile app. The failed projects, they were on my VPS using the CPU and memory. I removed their auth and dashboards to only keep their landing pages. That way I turned them into static sites and moved them from my VPS to Cloudflare Pages to host free. I'll still renew the domains because I still want to see them in the future. I can fail again but always will be learning from my mistakes and keep building until I make it.