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:

• 
  Daniel Oon (@EauDoon) reported 6 minutes ago

  Agentic checkout is live. @Visa says AI agents can now search, select, and buy on merchant sites, with 30 European issuers enabled and merchants onboarding through its Trusted Agent Protocol and Agentic Directory, embedded through Cloudflare and Akamai. The hard problem was never moving the money. It is proving which agent may act for which person, and whoever owns that registry owns agentic commerce.

• 
  Ajay Sohmshetty (@AjaySohmshetty) reported 7 minutes ago

  For context- Cloudflare’s durable execution platform, Workflows, originally only charged for underlying Worker usage, which is CPU-time based rather than clock-time based. In fact, we picked Cloudflare for this exact reason: most of our workflows involve waiting (ex. polling, waiting for network requests to come back), so it was far cheaper for us to use Cloudflare than @temporalio or @inngest for instance. These other durable execution platforms also charge based on “steps” - which I always thought was dumb, because it disincentivizes the best practice of decomposing workflows into small units of work in the form of steps. But unfortunately it seems Cloudflare is following suit, without warning… Feeling blindsided after we’ve already fully built all of our durable workflows on Cloudflare

• 
  Ownership (@ownershipfm) reported 8 minutes ago

  "There was a campaign claiming I was some other individual arrested in Amsterdam, that this was a rug I was attempting, and the Polymarket odds started to collapse" Ranga, Co-founder of Solomon Labs, on the FUD campaign, the Cloudflare outage, and the wild final hours of the raise "Those three days leading up to the raise and conducting it were probably the most interesting days of my life. I didn't sleep for most of those days. Some of the previous projects had high amounts of commits, so I was expecting we'd get well over our target, but I didn't know to what degree. There was also this secondary market active during our raise, the Polymarket, betting on whether we'd raise anywhere from 10 million to 100 million" "The night before the raise closed, I got a DM from one of the Polymarket bettors saying they'd infiltrated the cabal orchestrating the FUD campaign, and that they'd be DDoS attacking and shutting down the site before the close. I brushed it off with a grain of salt, but messaged Kollan that someone's going to attempt this. Our target was 2 million and we had about 5 or 6 million in commits at that point" "The morning of, the largest Cloudflare outage occurred and the site went down. There were jokes about how the cabal took down the internet to take out the Solomon raise and win some Polymarket bets. It created a little FOMO, and then they started attacking the backup sites, which actually attracted more attention. Within a few hours prior to close, we jumped from about 15 million committed all the way to 100 million"

• 
  Umut Sevinc (@memselon) reported 9 minutes ago

  @levelsio Thanks for this advice @levelsio im working on a new SaaS for Framer and i got this problem, it is better than cloudflare ?

• 
  Saint John: Evernode 1:1 Freedom (@AverageJohnEVR) reported 10 minutes ago

  @BitcoinBombadil It has nothing to do with payments x) It actually originate from the creator of BitcoinJS and its purpose is to allow decentralized executions on-chain (multisign) Back in the days people wanted to automate functions, so for example, if you wanted to send fiat to a paypal account and get bitcoin automatically on your bitcoin wallet, then you would need a way to make that into an automated thing. This method would also allow to replace human beings and the human factor from standing in the way. A lot about Bitcoin originates to payments, when it came people wanted to use it for purchases and automated operations. Evernode solves these challenges without interfering with the original technology, it just executes whatever you want, based on whatever you chose. It also replaces traditional hosting with decentralized hosting (instead of having **** behind cloudflare and on jeff bezos servers, you spread it across the globe)

• 
  Chris baker (@derpy01) reported 11 minutes ago

  @marx1verstappen @SSolarite Sure, not with the concept of DNS, but any service that uses that DNS, which is cloudflare and runs most the internet, will not work properly

• 
  ALEXYZ (@Alexvx_nft) reported 11 minutes ago

  YOU'RE BURNING API DOLLARS ON TASKS THAT HAVE A FREE PATH. MOST BUILDERS USE EXACTLY ZERO OF THEM. — Zefi mapped every major lab's free tier for a week (verified July 2026) most people pay before they even check what's unclaimed: > Google AI Studio · ~1,500 req/day · 1M tokens/min · no card > Groq · 14,400 req/day · 300+ tok/sec > OpenRouter · ~26 free models · one API key > OpenAI + Anthropic · $5 trial credits each > startup stack · $25K + $25K API · up to $350K Google Cloud > student stack · Cursor Pro + Perplexity + Copilot = $0 full dev setup — the Claude Code hack is the part nobody bookmarks: point ANTHROPIC_BASE_URL at Groq / Cloudflare / OpenRouter agentic loop on free third-party inference not official. works anyway. — same week GPT-5.6 tier routing went viral and loops guides hit 1.2M views CT still argues model scores while leaving $440+ in free access on the table the leak isn't which model you picked it's which free path you never claimed full map quoted below

• 
  U N C L E BIGBAY ✨ (@unclebigbay143) reported 13 minutes ago

  Today's Engineering Concept: '𝗥𝗮𝘁𝗲 𝗟𝗶𝗺𝗶𝘁𝗶𝗻𝗴' 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗥𝗮𝘁𝗲 𝗟𝗶𝗺𝗶𝘁𝗶𝗻𝗴? Rate limiting is the practice of restricting how many requests a user or system can make within a specific period. 𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿? Without rate limiting, a single user or malicious bot could overwhelm your server, degrade performance, or abuse your APIs. 𝗥𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗲𝘅𝗮𝗺𝗽𝗹𝗲 Imagine a login endpoint with no rate limit. An attacker could attempt thousands of password combinations every minute. A simple rate limit can significantly reduce the effectiveness of brute-force attacks. 𝗛𝗼𝘄 𝗶𝘀 𝗶𝘁 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗲𝗱? Most systems track requests by IP address, user account, or API key. Once a predefined limit is reached, the server temporarily rejects additional requests, often with an HTTP 429 (Too Many Requests) response. 𝗪𝗵𝗲𝗿𝗲 𝗶𝘀 𝗶𝘁 𝘂𝘀𝗲𝗱? • 𝗚𝗶𝘁𝗛𝘂𝗯: GitHub's REST API limits how many requests you can make per hour to prevent abuse and ensure fair usage for everyone. • 𝗦𝘁𝗿𝗶𝗽𝗲: Every payment request can include an Idempotency-Key, ensuring a customer isn't charged twice if the same payment request is retried. • 𝗢𝗽𝗲𝗻𝗔𝗜: The API enforces rate limits on requests and tokens per minute, helping maintain reliability and preventing a single application from overwhelming the service. • 𝗫 (𝗳𝗼𝗿𝗺𝗲𝗿𝗹𝘆 𝗧𝘄𝗶𝘁𝘁𝗲𝗿): X limits actions such as following many accounts, liking posts, posting, or sending DMs within a short period to reduce spam and bot activity. • 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲: Cloudflare lets website owners configure rules like "block or challenge any IP that makes more than 100 requests in a minute" to protect against abuse and DDoS attacks. ...and almost every public API uses rate limiting to protect its infrastructure, ensure fair usage, and maintain service availability. 𝗧𝗵𝗲 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆 A reliable system doesn't just answer requests. It also knows when to say "not now. It's too many from YOU."

• 
  Cap-EO 👨🏾‍💻 (@EOEboh) reported 17 minutes ago

  The second real problem: backups With Postgres on a managed service, backups are a checkbox. But with SQLite, the database is just a file on my server, and if that server dies, so does my business 🥹 My fix: automatic snapshots shipped to Cloudflare R2 Cheap, but I had to build it myself (there are probably better approaches like a VPS backup).

• 
  Maran (@TheMaran) reported 21 minutes ago

  > raised $0 from vcs > launched their token on a network nobody heard > been live since 2024, literally no one heard about them until Robinhood > made ~$10,000,000 within a week on robinhood chain > paused new token launches to get rid of vamp attacks > main domain went down because of a cloudflare issue > diverted 100% fees to the creators & pools > launched a new site, may be a drainer I think this is an unserious project that made serious money in a short duration

• 
  justinmiller's cat (@___727__) reported 27 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Sachin Joshi (@Sachin_is_here) reported 40 minutes ago

  R2, Zero Trust and Cloudflare One followed the same playbook: Find an expensive or complex infrastructure category. Offer a simpler product on the existing network. Reduce setup friction. Then let customers adopt one service before expanding into others.

• 
  Pi Changelog (@PiChangelog) reported 40 minutes ago

  Fixed (continued): - /login amazon-bedrock now prompts for and saves a Bedrock API key. Bedrock ambient AWS credentials keep using SigV4, including for custom model IDs. - Cloudflare Workers AI and AI Gateway authentication fixed to use ambient account and gateway IDs when stored credentials contain only an API key.

• 
  Piyush (@PyDataWizard) reported 42 minutes ago

  Total monthly cost to run a startup: ~$20 - Claude ($20/mo) = coding - AWS Free Tier = hosting & DB - Vercel = frontend (free) - Stripe = payments (2.9%/txn) - GitHub, Clerk, Cloudflare, Sentry = all free Never been a better time to ship. What’s stopping you? 🚀

• 
  Eiji Murasaki (@next20220424) reported 42 minutes ago

  Again. Web server is returning an unknown error There is an unknown connection issue between Cloudflare and the origin web server. As a result, the web page can not be displayed. Error reference number: 520 Cloudflare Location: Osaka