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:

• 
  nikshep (@nikshepsvn) reported 3 minutes ago

  paid dex for $yowl, feel free to fact check all the information on the site if you can't access it for some reason, likely cloudflare geoblocking so use a vpn while i fix it

• 
  Zatkobratko (@Zatkobrat) reported 8 minutes ago

  Bizarre is perhaps not the word I used since it's only been a day. I do not agree with them disabling it and fixing vamp is perhaps not good. Since the first dever can be an idiot, but apperantly they got attacks on their site on cloudflare. So it seems that they are right now not only fixing vamp, but also their website and transferring it to another decentralized hosting server. Might take a few more days tbh

• 
  Rahul Pramod Jaguste (@RahulJaguste) reported 12 minutes ago

  1/ Cloudflare just published why they are migrating to ML-DSA and not the compact post-quantum signatures. Their title: "Why we cannot wait for better signature algorithms." Correct call for the web. But a blockchain is a different problem, and the difference flips the answer.

• 
  SAMARA (@thee_samara) reported 12 minutes ago

  It’s over for robinhood memes Noxa shutdown due to DDoS attack BEWARE! The main problem: website flagged by browsers its the biggest launchpad on Robinhood, responsible for 75% of memecoin launches. over $10 million in fees, the past week but Noxa dumped over 86%, from $11 to $1 Rumor is they might have intentionally done this, to buy at a lower price, and also their name servers aren’t set to cloudflare. The solution (kinda): here are alternatives @ >virtuals_io >ponsdotfamily >apedotstore >Launchhood >bowdotfun be safe out there and goodluck.

• 
  Koen Bok (@koenbok) reported 12 minutes ago

  There are so many apps I can't login to because @Cloudflare turnstile just never works.

• 
  batuhan içöz (@batuhan) reported 12 minutes ago

  all the stocks i got in the last few months are down but cloudflare is up enough to cover

• 
  Hot Aisle (@HotAisle) reported 16 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev wish they'd move off salesforce for their support system...

• 
  lolnotacat (@lolnotacat) reported 22 minutes ago

  @TheOtherMassie I just got a verification. Try a couple different servers and regions. The IP you're using was probably flagged by cloudflare or other DNS service.

• 
  Stake Exposed ⚖️ (@formatpal) reported 24 minutes ago

  @Stake Code Segregation and Infrastructure Concealment To protect the development team and systematically obfuscate the physical location of the backend infrastructure, a highly secure code-deployment strategy is enforced: Siloed Access (Microservices Dependency): No individual developer in Belgrade has access to the complete monolithic codebase. Tasks are strictly divided: one engineer manages the wallet integration, another maintains a specific game, and a third works on the Risk Engine. Automated CI/CD Pipelines: Code written in Belgrade is committed to enterprise GitHub/GitLab repositories and deployed automatically via secure pipelines (using Docker, Kubernetes, and Terraform). The code is deployed directly to cloud servers hosted by Amazon Web Services (AWS) located in Frankfurt (Germany) and Dublin (Ireland) to minimise latency for European and Middle Eastern players. Cloudflare Enterprise Cloaking: The backend servers are never directly exposed to the public. All incoming traffic is routed through Cloudflare's Enterprise reverse proxy, which masks the real AWS IP addresses. When users attempt to trace the platform's servers, they see IP addresses mapped to the US or Western Europe, completely masking the technical engine room operating from Belgrade.

• 
  Aurum (@Aurum8880) reported 28 minutes ago

  HTTP has carried a payment error code since 1991. ethereum:0x4a220e6096b25eadb88358cb44068a3248254675 ripple:native stellar:native Status 402: Payment Required, written into the protocol as a placeholder and never implemented. x402 Foundation launched this week with 40 member organizations including Stripe, AWS, and Cloudflare. The protocol activates that dormant code using stablecoin settlement Turning any HTTP request into a payable endpoint — no setup, no intermediaries required. 75 million transactions processed in the last 30 days. In 1991 there was no settlement asset that could operate at the speed of a network request. Stablecoins provided that, and x402 is the infrastructure that follows.

• 
  Pinzari Andrei (@PinzariAndrej) reported 29 minutes ago

  @Cloudflare Making the exception machine-readable is a meaningful improvement over silently weakening validation. Will Cloudflare publish telemetry on how often EDE 33 is returned and how long exceptions remain active? That would help quantify both operational value and the risk of temporary bypasses becoming sticky.

• 
  Rahul K (@rknkhanna) reported 30 minutes ago

  you mean 3 people are trying to cancel cloudflare?

• 
  Sherlock | DeFi Researcher (@Sherlockwhale) reported 31 minutes ago

  At $139.26, $SPCX is still 3.2% above the offer price, so it has not actually undercut its IPO price yet. But I still don't think it's cheap at $139. For my research, I looked at 31 major tech listings, including Amazon, Nvidia, Google, Tesla, Meta, Alibaba, Uber and Airbnb. Three of them, Spotify, Palantir and Coinbase were direct listing (not a normal IPO), so the final sample was 28 companies. Out of those 28 IPOs: 17 traded below their offer price within one year. 20 fell at least 20% below their first public close within one year. 16 fell at least 30% below their first close. 13 fell at least 40% below their first close. Only eight of the 28 held above the initial closing price during their first year: Nvidia, Google, ServiceNow, Shopify, Zoom, Cloudflare, Unity and Airbnb. Now compare that with the actual IPO price and these eight companies have never traded below it: Nvidia, Google, ServiceNow, Shopify, Twilio, Zoom, Datadog and Airbnb. Now for the actual $SPCX price levels. The median first year low among the 28 traditional IPOs was 37.76% below the first close: $160.95 × (1 - 0.3776) = $100.17 The full 31 company sample and the closest mega platform group both will give you almost the same level, around $100.90. There is also a second way to calculate it. The median first year peak to trough decline was 56.75%: $225.64 × (1 - 0.5675) = $97.59 So, two completely separate measurements converge around $98-$101 and that is why I think $100 should be your first serious bid. If I only use the IPOs launched since 2017, the typical company traded 43.4% below its first close during year one. Applying the same decline to $SPCX gives a price of roughly $91. And among the most heavily hyped listings, the typical decline was around 54.3%, which would put $SPCX near $74. Using its listing high instead gives similar levels around $86 and $79. That is why I see $75-$100 as the most reasonable accumulation zone. The valuation story is also another reason to wait. At $139.26, SpaceX is worth roughly $1.82 trillion, or 97.5 times its 2025 revenue. Even at $100, it would still carry a $1.31 trillion valuation and trade at around 70 times revenue. So, SpaceX could become one of the greatest company ever built, but even a great company can be a bad investment at the wrong price.

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

• 
  Sandip Dev (@devsandip) reported 37 minutes ago

  holy **** @Glassdoor and @indeed all i wanted was to read a few interview questions for a particular company on glassdoor. now i have spent the last 10 minutes, filling 2 otp, 5 cloudflare capthas, yes/ok/continue on like 2 dozen screens and you still want more info. **** you