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:

• 
  Helena De La Cruz V. (@dlc_helena) reported 3 minutes ago

  Stopping the bad guys with Cloudflare: 4,651 malicious requests blocked or challenged in the last month #cloudflare

• 
  CodeGlitch (@codeglitch) reported 3 minutes ago

  Cloudflare just open sourced an agent workspace. The part worth copying is not the operating-system label. It is the boundary around the work. Cloudflare OS combines an agent chat UI, sandboxed apps, and Gatekeepers for external services. Its repository says a Gatekeeper narrows access, logs actions, and can queue side effects for human approval after the run. That is the useful idea: give an agent one workspace, one capability, and one checkpoint that proves the change. Today's lesson The concrete Claude Code version: inspect one issues API wrapper, add a read-only list in one dashboard folder, run one test, show the diff, and record DONE, NEXT, or BLOCKED. No ambient connectors. No secrets in the first pass. No approval without a record. Cloudflare labels the August 2026 release early access. Study the design, then verify your own permissions. Also in today's brief Cloudflare OS says its local quick start is for trying the stack, not production. The repository uses Gatekeepers as a capability-based layer around external services. The HN front page carried the release among its leading current stories. The X sweep also surfaced DeepSeek V4 Flash 0731 on NVIDIA hardware and LongCat 2.0 in OpenCode, but those were not selected as today's lead. Full lesson and brief below.

• 
  RifatOfficial (@RifatOfficiall) reported 7 minutes ago

  @nguyenthambt @Cloudflare Yeah it costs nothing and worst case you just get the name.

• 
  Rheza Pahlevi (@rheza) reported 7 minutes ago

  @Cloudflare useless company with zero support. please dont expand for nonsense.

• 
  Agentic Adam - DeployAIWorkers.com (@AdamAutomates) reported 10 minutes ago

  @Cloudflare has such a killer support team. From bug report open to two different replies and a specific date given for when the fix will be in place. Total time - 13 hours Incredible

• 
  BigBagX (@BigBag_X) reported 12 minutes ago

  @Cloudflare allows Ai Agents to pay for APIs @SoFiTechSol built the blockchain agnostic API stack that banks, fintechs and credit unions will need to simplify their life … to be born in the 70s, 80s or 90s and have NO CLUE about the changes on the horizon… **** around 🫢😬

• 
  daily netizen (@dailynetizen24) reported 14 minutes ago

  NETIZEN UPDATE: CANVA GLITCHING FOR 3 DAYS? CANVA KEEPS SAYING IT'S FIXED, BUT SUBSCRIBERS SAY THE SAME GLITCH HAS PERSISTED FOR THREE DAYS Canva insists everything is running normally, but many frustrated subscribers say reality tells a different story. Despite Canva's official status page showing "All Systems Operational" and no active global outage, users, particularly in the Philippines, continue reporting painfully slow loading times, login failures, blank white screens, and designs that refuse to open even after the company said it had already deployed a fix. The disconnect between Canva's official messaging and users' real-world experience has fueled growing criticism online, with many questioning why recurring complaints have persisted for nearly three days if the issue has supposedly been resolved. "Canva is down? It's been 3 days, my Canva is so slow. My internet connection is fast," one X user wrote . Another subscriber said they had exhausted virtually every troubleshooting step without success. "@Canva 3 days down, so slooooooow. Tried different browsers, different phones, even different accounts. My internet is fast... I need to get a lot of things done." Others said the platform has become unusable for creative work, with one user lamenting that they could no longer create Wattpad covers because Canva had remained inaccessible for days. Canva acknowledged a temporary "snag" on August 4 and announced that a fix had been deployed. Yet complaints have continued pouring in afterward, leaving many subscribers wondering whether the underlying problem has truly been resolved for everyone. While Canva's global monitoring systems continue to report that core services are operational, the pattern of complaints suggests that some users, especially in parts of the Philippines, may still be experiencing regional or ISP-related disruptions. Such issues can stem from content delivery network (CDN) routing, ISP peering, DNS resolution, or other localized infrastructure problems that may not appear as a full global outage. That distinction, however, has done little to ease the frustration of paying customers who say they have spent days unable to access a service they rely on for work, school, and business. Critics argue that repeatedly announcing that issues have been fixed while many subscribers continue experiencing the same problems risks undermining user confidence. Although partial regional outages can be difficult to detect and may not warrant changing a global status indicator, users expect clearer communication when widespread reports persist after an announced fix. For those still affected, common workarounds include switching between Wi-Fi and mobile data, using a VPN, changing DNS servers to Cloudflare (1.1.1.1) or Google (8.8.8.8), clearing browser cache, using Incognito mode, or trying a different browser or device. If none of those steps work, the problem may be tied to a temporary regional network issue beyond the user's control. For now, Canva maintains that its systems are operational, but many users say their experience tells a very different story.

• 
  SaltyAom (@saltyAom) reported 19 minutes ago

  Ok, I'm going to be annoying here But what's stopping Node.js from implementing a native HTTP server based on Web Standard Request/Response? Like really? What's stopping it? It's very clear the industry has moved into this Runtime: Bun, Deno, Workerd/Cloudflare Worker, Vercel Function, Netlify Edge Function, Fastly Compute, Supabase Edge Function, even in your browser via Service Worker Meta framework: Nextjs, Nuxt, Angular, SvelteKit, Tanstack Start, Astro, Remix, Waku Even backend frameworks: Hono, Elysia, H3, every single Deno/Bun/Cloudflare Worker framework Every single one uses Web Standard Request/Response, but the only major runtime that doesn't support it is Node.js? I would urge that not implementing it is hurting the ecosystem It makes the library/framework author have to implement their own adapter to convert from Node IncomingMessage/OutgoingMessage to Web Standard Request/Response just for the user to use it properly in a runtime that doesn't support it as an exception It noticeably adds unnecessary work to maintainers and additional overhead in both compute and memory usage for YOUR servers If you are using a meta framework, you are having a performance degradation compared to what it should be because Node.js simply decided not to implement this specific feature over the past years "Oh but it is slow" Implementing it in runtime native code has many more optimization options available than in userland, like lazy initialization, like how Deno does And it can't possibly be worse than every framework paying adapter cost today "Oh but that would be a breaking change" No, Web Standard Request/Response exists but is just never used outside of fetch doesn't need to be removed; just create a new function that doesn't intersect with it, and that's just literally it Node.js was even on the WinterCG committee (now WinterTC) to draft this standard, just to implement the bare minimum for fetch and not an HTTP Server? Like come on I'm willing to bet if you ask a maintainer of a framework that supports API routes how they feel about this, every single one will say they're not happy or at least annoyed Personally, it felt like it's starting to get from the understandable zone into a really questionable zone I know how frustrating it is for maintainers to get a request to support this or that, as I myself also don't like one either But come on, when there's a standard already agreed on and used by everyone for years that even you yourself helped draft but just decided not to use it, you can't expect people not to complain about what makes their work harder Do I have to draft a page requesting support and ask for the author of each framework/runtime to sign so we can have the evidence that the majority library/framework wants it? Or do you need help to draft an API or implementation? I'm willing to bet that many people would want this feature natively supported on Node.js, even I would be willing to help with it where I can

• 
  Arpit Bhayani (@arpit_bhayani) reported 23 minutes ago

  Cloudflare published a blog on how they serve Kimi K2.6 and GLM 5.2 at scale, and the memory math behind it is worth digging into. For these models, it is usually not the model weights that fill up GPU memory first. It is the KV cache. For Kimi K2.6, Cloudflare stores the cache in FP8 (8-bit) precision instead of the default BF16 (16-bit). That halves its size, and it takes the max context held in memory from about 686,000 tokens to 1.37 million tokens. Pretty solid. Here is the interesting part... At any fixed concurrency, BF16 is a few percent faster per token (~5-9%), since the FP8 kernel has to convert its 8-bit cached values to 16-bit precision before it can do the attention math. BF16 skips that conversion entirely. But BF16 stores each cached value at double the size, so it runs out of cache room at 32 concurrent requests and cannot admit a 33rd. By using FP8 instead, Cloudflare keeps admitting requests up to 64, and that is where the 41% higher peak throughput comes from, by fitting more requests onto the same GPU at once. For GLM 5.2, they go further and compress the weights themselves, from FP8 down to INT4. This makes per-GPU memory go from about 88 GB to 52 GB. We might feel that cutting the bit width in half, twice over, sounds like it should cost something in quality. It actually does not. FP8 KV cache and BF16 land within a point of each other across benchmarks. INT4 weights stay within 0.8 points of FP8 across every benchmark they ran. So this is the trade Cloudflare is making: smaller storage everywhere, with benchmarks confirming nothing is lost, in exchange for far more concurrent requests on the same GPU. Hope this helps.

• 
  TechGuard (@sysguardion) reported 23 minutes ago

  @bc1cindy Cloudflare is going in a direction I never thought they would, and that makes me happy. As a long-time customer, I've had very few issues with them, and I hope the same quality carries over to this new venture.

• 
  Makoto | ..... (@mareni_musashi) reported 29 minutes ago

  @DmytroKrasun In many cases, I would agree. Then I have an experience like just earlier today when I needed to send a deck out for a stealth project we have underway. I want to have strict controls over who can view the deck and how. Normally, DocSend is the go-to. Instead, I just spun up a subagent, gave it both general and specific directions as to the features I wanted and access to the environment we deploy into and how I wanted to manage it. An hour later, I have a DocSend that is actually better than DocSend hosted for free on Cloudflare. It is very secure (I directed this part) and can be completely controlled from a cli on my computer (so no admin dashboard needed -- call it AI native). Colleagues tried it and were like "wtf, this is amazing!" It will not require much maintenance at all because we are the only consumer -- and here is where your last argument fails. Not saying ScreenShotOne is something that falls into this category, but there are defo a million (now way overpriced) SaaS tools that do.

• 
  fred (@F7203607Fred) reported 29 minutes ago

  @FreedomIsntSafe @LoveIsBitcoin21 Cloudflare uses "DIY entropy", must not be that bad.

• 
  Gulf Air (@GulfAir) reported 29 minutes ago

  @amitxgupta @Cloudflare Hello! If Captcha does not load, please press F5 on your desktop device at that exact moment, or reload it, then it should appear. If the issue still persists you may try either from a different internet browser, internet connection or by using our mobile app!

• 
  Linas (@LinasLekavicius) reported 30 minutes ago

  There’s a way for @Cloudflare to get a lot of real users for these wallets quick: Add a Privy-like offering where any app that uses stablecoins can embed Cloudflare wallet One click sign in with google/email to the user’s CF account (or a new one is created if it’s their first login to Cloudflare) -> a virtual wallet for that app is created or selected (if already signed in to that app before) that the user can control from inside the app Privy and others are charging a lot for this, if it was free many apps would use it instead

• 
  🎩 Krzysiu (Chris) (@Krzysiu_91) reported 32 minutes ago

  This is where Reactive Network (base:0xedacc73ae9f73235934f72a43388404e4a2c4a24) clicks in perfectly. Reactive Contracts let you write normal Solidity that literally listens to events on other chains and executes on its own. No keepers. No off-chain bots. Just pure on-chain “if this, then that.” So the AI agent (powered by Cloudflare) can decide and signal; Reactive handles the secure, autonomous execution. Pay for an API, confirm on-chain, automatically trigger the next step, rebalance, unlock access, or settle somewhere else. All keeperless. Cloudflare solves the “agents need wallets and identity” problem. Reactive solves the “agents need real autonomous on-chain reactions” problem. Together they feel like actual infrastructure for the agentic internet, not just another payment button. $REACT