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:

• 
  Punit Arani (@punit_arani) reported 5 minutes ago

  @RhysSullivan I use @Cloudflare a lot now but damn I miss the DX of @vercel

• 
  Jay at AmericanTorah.com (@AmericanTorah) reported 8 minutes ago

  @RestoredMySoul My website is very slow to respond right now. I'm not sure if it's my site, Cloudflare, or something else happening.

• 
  Himanshu (@codingstark) reported 9 minutes ago

  @schanuelmiller i thought next.js was so mature, so I should switch to next.js and server action. but, after realizing the performance and cloudflare deployment issue, I was like, “I really got stuck here.” so I just moved back again and revamped my whole codebase to tanstack.

• 
  Turtle. (@TurtleOne_) reported 11 minutes ago

  @LanceHalo @MarathonDevTeam Probably a combination of cloudflare being flooded + some unfortunate save data syncing error. Sometimes it's better not to disclose the issue to prevent bad actors from attempting to stress test the fix

• 
  AwesomeAI (@Awesome_AI_News) reported 11 minutes ago

  Cloudflare launches a groundbreaking web search API, enabling AI agents to access real-time public web pages, addressing information lag and errors caused by training data cutoffs, breaking traditional monopolies..... Cloudflare推出颠覆性网络搜索功能，通过API让AI智能体实时访问公开网页，解决大模型因训练数据截止日期导致的信息滞后和错误问题，打破传统巨头垄断。

• 
  Josh Whiton (@joshwhiton) reported 13 minutes ago

  @Cloudflare your AI agent shows promise but has a big problem rn. It says, "Let me try to..." [do something that it promises to do] but then just sits there doing nothing, leaving the user waiting for nothing. Very frustrating. Also shut down @CloudflareHelp if it's not active.

• 
  Dr. Valerie Thomas (@Valerie32844654) reported 15 minutes ago

  I'm currently having significant problems with Cloudflare. Their lack of integrity to resolve customer issues is not reputable.

• 
  Marquivion (Marq) Orr (@0xprimex0) reported 15 minutes ago

  Mature General-Purpose Libraries (PQC-Ready 2026) Battle-tested libraries with shipped NIST algorithms: • OpenSSL: Production-ready via oqs-provider or native 3.5+. Supports ML-KEM, ML-DSA, SLH-DSA & hybrids. Choose OpenSSL if you need maximum compatibility with existing infrastructure and web servers. It is the standard choice if you are already using OpenSSL and can integrate the oqs-provider module or upgrade to version 3.5+ for immediate ML-KEM/ML-DSA support without rewriting your application logic. • Botan: Full native C++ support. Most complete NIST suite (ML-KEM/DSA, SLH-DSA, FrodoKEM, Classic McEliece). Choose Botan if you are developing in C++ and want the most comprehensive algorithm coverage out-of-the-box. It is the best choice if you need immediate access to the full NIST suite (including alternative KEMs like FrodoKEM) with a modern, object-oriented API, rather than waiting for C libraries to catch up. • Bouncy Castle: Dominant in Java/.NET. v1.83+ supports ML-KEM/DSA, hybrid certs (RFC 9883), and composite signatures. Choose Bouncy Castle if your stack is Java, Kotlin, or .NET/C#. It is the undisputed leader for JVM and Microsoft ecosystems, offering the only mature, native implementation of hybrid certificates (RFC 9883) and composite signatures required for complex PKI migrations in enterprise environments. • Mbed TLS: Emerging support. ML-DSA prototype available; ML-KEM planned for late 2026. Best for constrained IoT soon. Choose Mbed TLS if you are targeting highly constrained embedded devices (low RAM/Flash) and can wait slightly for full ML-KEM stabilization (expected late 2026). It is ideal if you need a small footprint and are already using the ARM PSA Crypto architecture, provided your timeline allows for the final ML-KEM integration. • Google Tink: High-level API. Delegates PQC to backends (AWS-LC, BoringSSL, OpenSSL). Easy integration for apps. Choose Google Tink if you want a language-agnostic, high-level API that abstracts away the underlying crypto engine. It is the best choice for application developers who want to enable PQC (via a supported backend like AWS-LC or OpenSSL) with minimal code changes and without managing low-level cryptographic primitives directly. • CIRCL(@Cloudflare): Go-native. Focused on PQC research & hybrids (Kyber/X25519). Used in Cloudflare services. Choose CIRCL if you are building services in Go and need cutting-edge, research-grade implementations of hybrid schemes. It is the preferred choice for Go developers who want to leverage Cloudflare’s production-tested PQC research and need flexible, low-level control over key exchanges in network protocols.

• 
  Alex Yeung (@miyagiyang) reported 15 minutes ago

  @eastdakota Hi Matthew, I wonder what's your take on agents running on edge cloud? Some people say that would never happen because the terminal (like computers or cell phones) can take that job.I'm always a big fan of Cloudflare, and I'm a Cloudflare developer.I'm also a Cloudflare investor

• 
  Fayaz Ahmed (@fayazara) reported 15 minutes ago

  Login with Cloudflare

• 
  Matt 'TK' Taylor (@MattieTK) reported 21 minutes ago

  I've written a Cloudflare-First issue tracker for agents and dogfooding building it with Claude Code (Claude writes issues to it to improve how it can write issues to it) and this feels like the Product Manager equivalent of working on your esoteric Pi configs.

• 
  Daniel Smith | Building ClawQL Agents (@DanielSmithDev) reported 23 minutes ago

  @LowLevelTweets @kentcdodds It was mostly in context of them vs cli tools directly. Argument was MCP would bloat. So many bad engineers cried about it and gave up. Then @Cloudflare came along with code mode and now Claude and others have dynamic tool loading and there are several ways to solve the issues.

• 
  Official Layoff (@LayoffAI) reported 24 minutes ago

  ORACLE LAYOFFS OFFICIALLY BEGIN AMID COMPLAINTS OF TERRIBLE SEVERANCE TERMS The 60 days of notice is up, and the first of the 30,000 are hitting the door. All will be out by June 15. As per Time Magazine, one long-tenured employee lost approximately $1 million in restricted stock units (RSUs) that were just four months from vesting. Oracle did not accelerate unvested RSUs for any departing worker; any shares that had not cleared their vesting date by the termination date were forfeited permanently, even when those grants had been issued as retention incentives or in lieu of salary increases. Stock compensation made up roughly 70% of that employee's total pay. At least 90 laid-off employees organized and signed a public petition asking Oracle to match the terms of comparable layoffs at Meta, Microsoft, and Cloudflare. Meta's package began at 16 weeks of base pay plus two weeks per year of service. Microsoft's voluntary retirement program, offered to eligible long-tenured employees, provided stock vesting for six months post-termination, a minimum of eight weeks' pay, and additional weeks based on seniority. Cloudflare, which cut more than 1,100 employees globally at roughly the same time, offered base pay through the end of 2026 plus full healthcare coverage and equity vesting through August 15. Oracle responded by email: the terms were final. Four weeks of base pay for the first year of service, plus one additional week per year of tenure, capped at 26 weeks. All unvested options forfeited.

• 
  rob (@rob_x_ai) reported 24 minutes ago

  @Cloudflare @CloudflareHelp Your "Startup Program" pitch: build on us, founders. 🚀 The reality: billed $50 you admit I don't owe, account flagged past-due while in good standing, locked out of adding my own domain, and a support ticket that closed without a fix. Case 02104813. This is the founder experience? Do better.

• 
  David Macias (@dmacias) reported 28 minutes ago

  @NoamTenne @Cloudflare I don't know Reddit posts about their lack of support are plenty.