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:

• 
  Keith Kaplan (@KeithTradeSmith) reported 4 minutes ago

  Cloudflare $NET just notched a new all-time high this week, adding fresh fuel to the bull market in securing the world's AI, computers, and data centers. Back in March, we introduced our Agent Supernova thesis, the idea that AI is now advanced enough to take over everyday tasks, from managing factory schedules to running financial analysis to writing software. Over the next 12 to 24 months, that list keeps growing. Within two years, the number of AI agents operating in the American economy isn't likely to grow 10X or even 1,000X. Try 10,000X. That kind of expansion needs infrastructure, security, and traffic management at scale, and that's exactly where Cloudflare $NET sits. Cloudflare is one of the world's leading Content Delivery Network firms, speeding up website content and cutting latency and bandwidth costs. Add in its cybersecurity services, AI agent management tools, and AI agent transaction services, and Cloudflare starts to look like an AI agent conglomerate. The numbers support the thesis. Cloudflare's revenue grew 29% in 2024 and 30% in 2025. Wall Street projects revenue near $2.79 billion in 2026, roughly 29% growth, rising toward $3.6 billion by 2027. After ten months of sideways consolidation, the stock broke out to new highs today. If the Agent Supernova unfolds as expected, Cloudflare's diversified position in security and agent management should keep driving growth well past this breakout.

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

• 
  Ramon 🎹 (@ramonpiano_) reported 9 minutes ago

  the apple signing stuff worked, so i guess lumakeys is an official app now :) well - i still gotta test it on my other mac tomorrow when im back home, but since earlier tests didnt make any problems i expect it to instantly work now i'm trying to finalize some simple onboarding and add update functionality + cloudflare r2 to host the updates i will send out some beta versions to test tomorrow, i already wrote some of you down, but please let me know if you wanna beta test. would love to hear your thoughts and feedback! and then, i guess from tomorrow things are getting real :)

• 
  bittermelon (@melon_thief) reported 9 minutes ago

  @AWSSupport Moving my domains and hosting to Cloudflare. There should have been a service bulletin on the billing page explaining the issue

• 
  David Escobar (@dbescky) reported 11 minutes ago

  @natmiletic Astro is mostly html and css. So it can render super fast because Cloudflare can cache it and you can make it super lean….. my site speed is sub 1 second on slow mobile. Sub 0.5 on slow desktop.

• 
  Hardik (@rezerov_) reported 15 minutes ago

  @Road_Kill11 @Cloudflare Might be a downstream consequence of AWS billing issue. Unlikely they'll 100x cost like this. Weird times man.

• 
  naps62.eth (@naps62) reported 15 minutes ago

  @oleg_fem Seems I had an issue with the "http -> redirect, and safari was smart enough to still redirect. a toggle missing on cloudflare should be fixed now!

• 
  NiSHAT  (@rednishat) reported 16 minutes ago

  If you turned on "Block AI bots" in Cloudflare, check your settings before September 15. Here is what is happening. Cloudflare just split AI crawlers into three categories. Search bots, Agent bots, and Training bots. Makes sense on paper. The problem is Googlebot, Bingbot, and Applebot do all three things. They index your site AND they feed AI training data. So when Cloudflare applies its strictest-rule logic on September 15, if you have AI bots blocked, those rules will catch Googlebot too. Not at the robots.txt level either. At the network level. Which means Google literally cannot get in. For WordPress site owners this is a real problem hiding inside what looked like a smart setting. A lot of people turned on "Block AI bots" months ago to protect their content from being scraped for training data. Totally reasonable call at the time. But nobody told them it would eventually take down their Google crawling with it. Less crawling means pages get indexed slower, rankings get affected, and you will not even know why for weeks. Go into your Cloudflare dashboard right now. Check which crawler categories you have blocked. Make sure Search is allowed. Then decide intentionally whether you want to block Training bots knowing Googlebot might get caught in that net too. The tradeoff is real. Protecting your content from AI training vs staying visible in Google. You need to pick one or find the middle ground before the deadline hits. September 15 is not far.

• 
  luna (@ImLunaHey) reported 19 minutes ago

  **** it.. building something self hostable on @Cloudflare using gpt 5.6 sol.

• 
  Anirudh Oppiliappan (@icyphox) reported 21 minutes ago

  @threepointone @AKuederle Not sure where all this anger is coming from. The folks on Bluesky (and me here) were poking fun at the banner text—which was apparently *meant* to be tongue in cheek! Wasn’t clear. Nobody’s trying to cancel Cloudflare. Let’s all chill out for a bit.

• 
  Keith C Wenzel (@keith_c3529) reported 22 minutes ago

  Never be desperate enough to buy tickets through @StubHub or @axs ….one of the worst customer experiences ever. You would be incorrect to think all those extra fees have gone into a good customer experience or a mobile application that actually works. Their inability to staff and manage their @Cloudflare leaves them inept at servicing customer access to their paid for tickets. Instead they force you to jump through hoops, stand in lines and waste your time at an event since they refuse to fix their stuff or hire competent employees who know how to properly configure their cloudflare. Pathetic.

• 
  Amanda Scott (@IleanaOlym75391) reported 22 minutes ago

  @its_ronc I had the same issue with Cloudflare. Switched to Qoest Proxy's residential proxies, and the challenge pages stopped being a problem.

• 
  Filip (@fristovic_) reported 24 minutes ago

  GitHub is down. AWS sending astronomical bills. Cloudflare bugging out. The end is near.

• 
  Delali (@delali) reported 25 minutes ago

  @DanielSmidstrup Even Vercel, Cloudflare, et al have challenges. For us founders, it never ceases. But I get your point. Let's keep pushing…

• 
  Ghost AI (@Ghostaisystems) reported 26 minutes ago

  Patreon’s blocking AI bots w/ Cloudflare now. Robots.txt was never enough apparently. From deploying real AI systems every day: this isn’t protection, it’s fear-driven stagnation. Creators deserve better than being cut off from the AI revolution. Or is that the point?