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:

• 
  Katewerk (@katewerk) reported 4 minutes ago

  @Cloudflare Adding @Cloudfare broke my site so badly I had to suspend it within days. Now, despite cancelling my paid subscription, and removing the domain, your website won't allow me to remove my credit card from your records -- and your support bot is ghosting my tickets. Fix it.

• 
  U N C L E BIGBAY ✨ (@unclebigbay143) reported 8 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."

• 
  Rifat Ahmed (@Rifat_EE) reported 10 minutes ago

  For two years every chain kept saying "the agent economy is coming", meanwhile @base quietly ran off with 95% of it and stopped answering at the phone👀!! $52 million in real money moved through agents on $BASE . Not next quarter, not "soon", its already gone!! And nine out of every ten x402 payments that ever happened, on any chain, in any country, landed on Base.(Superbb) What these things look like :: --> 169 million agent transactions processed on Base by July 2026 --> 20 million transfers in one 90-day window alone --> Payments over $1 grew from 49% to 95% of all volume, agents are moving real money now, not cents --> 95% of every x402 payment across every chain lives on Base The stack building around Base : )- @AskVenice takes x402 for inference, Exa for search, Wolfram Alpha for math )- TripAdvisor, FlightAware, Amadeus take it for travel )- Apify plugged 20,000 tools into x402 on Base last month )- @Cloudflare , Amazon Bedrock, Stripe, Google are all sitting in the x402 Foundation The other half of the story : )- Agents are not just spending on Base, they are earning too )- The Felix agent has pulled over $261,000 in real revenue from paid services )- This is a two way economy, not a one way experiment anymore Every other chain is still pitching the agent economy. Base already banked it and boominggg,, And they never even said the word "narrative", cause they also know people currently loves to see into eyes, not a fake hype or big words without any basement what do you think? Where this Unstoppable base will stop???

• 
  Mohit (@mohitdotdev) reported 12 minutes ago

  Encrypt docs & PII end-to-end on Cloudflare Workers: client wraps random DEK with your password key, server adds outer master-key wrap; share securely by re-wrapping the DEK for others, grant edit rights with consent - server never sees plaintext. This is my way forward to keep every bit of user data encrypted. Fully and provable.

• 
  Aaryan Bansal (@NotUnHackable) reported 13 minutes ago

  @CloudflareDev @cloudflare, i request you, please just fix the env variables being so hard and for no reason keeps failing silently in the background in the workers page

• 
  SecureChap (@SecureChap) reported 14 minutes ago

  A Mac user pastes one Terminal command after a fake Cloudflare CAPTCHA. The script blocks Ctrl-C with a trap and runs a fake 10-second progress bar while it pulls down payloads. Then comes a password dialog. Cancel it, and two LaunchAgents start firing. They kill Finder, Dock, Spotlight, Terminal, Activity Monitor, browsers and NotificationCenter in 210-millisecond bursts. One loop runs up to roughly 83 hours. The second fires every 0.2 seconds for as long as 3,000,000 seconds. NotificationCenter stays dead for six hours to hide Gatekeeper alerts. A background process then queries Keychain for Chrome's Safe Storage AES key. That surfaces a genuine macOS password prompt. The user must answer it to regain usability. The same credential decrypts Login Data and Cookies offline. The stealer pulls from eight browsers, 31 wallet extensions and six blockchain networks, then ships it out through Telegram bots. The goyim implant stays behind as SystemUIServerl, one character off the real process. It uses GSocket relays to gsnc[.]eu:67. Everything else self-deletes and forges timestamps. Group-IB tracked it across 100-plus targets in 33 countries, over half in Europe, since May 2026. No CVE. No exploit. Uploaded to VirusTotal on 9 June 2026 with zero detections. The victim types the password only because the machine has become unusable, and the prompt they finally accept is real.

• 
  Ethan Walker (@maria6186551590) reported 15 minutes ago

  Follow me and I’ll help you cut through market noise and focus on the stocks with real growth potential. $SNOW — Snowflake — Don’t buy $NET — Cloudflare — Don’t buy $ZS — Zscaler — Don’t buy $NOW — ServiceNow — Buy at $92-$99 $DDOG — Datadog — Buy at $242-$249 $VEEV — Veeva Systems — Buy at $183-$188 $SAP — SAP — Buy at $144-$154 $CRM — Salesforce — Buy at $156-$164

• 
  BTC Live (@btcliveco) reported 16 minutes ago

  JUST IN: 🤖 Cloudflare adopts the x402 protocol, enabling websites to charge AI agents directly for data access via crypto payments. Bitcoin and Lightning Network are positioned as primary rails. Machine-to-machine payments just found their native money.

• 
  Eiji Murasaki (@next20220424) reported 16 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

• 
  Porkbun (@Porkbun) reported 17 minutes ago

  @liltechnomancer @joshmanders That looks like something Cloudflare requires, not us. They appear to have a transfer process that includes extra steps because they require the domain to be using their DNS. It looks like the actual transfer was never submitted to Cloudflare because they were / are waiting on this step. If you changed your name servers after expiration, 10 days after expiration we disrupt DNS as required by ICANN and that would have prevented what Cloudflare seems to be waiting for. It's honestly best to renew / transfer before expiration to prevent wonkiness like this.

• 
  Alpernoth (@Alpernoth) reported 18 minutes ago

  This website has some serious issues with Cloudflare bullshit, and I'm getting really ******* sick of it.

• 
  VictualBro (@Victual_Bro) reported 20 minutes ago

  Back to dealing with this bullshit every day. Have we all had enough with Cloudflare ****?

• 
  Geo Chris (@GeoChrisN) reported 22 minutes ago

  @php4fan @Cloudflare I just close all the proxies and the side come back correct with not any issue ....

• 
  Ajay Sohmshetty (@AjaySohmshetty) reported 25 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

• 
  Christopher Molin (@Chrimle) reported 27 minutes ago

  @KentonVarda No, no human would ever imagine writing the crazy bugs that AI hallucinates. There is no thought-pattern, and the feedback is a waste of time - because the "author" won't learn anything... The whole industry has code-review, did Cloudflare pick that up recently, or...? Would explain the recent issues...