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:

• 
  jem is looking for a job (@sheherenow_) reported 3 minutes ago

  I've been building Trails ~ a personal project intelligence platform that keeps track of all of the 1000 projects you work on across harnesses/models/computers and reminds you what you've been doing anyway. it's all self-hosted/open source on your own network and i'm deciding what that means for how I handle LLM inference. I really hate to build anything with """user accounts""" and imho data is sensitive enough that i don't want to touch it, but inference for summarization is currently done on (my) cloudflare worker i could just do BYOK or local summarization but that feels like it will have way more complex onboarding (but maybe that's ok?) would love thoughts/prayers bc this is the part of the thing i hate the very most

• 
  035.eth (@web3manager_eth) reported 4 minutes ago

  Cloudflare announces the issue of their brand new wallet with stables integration. Users have the chance to secure their handle to use during payments with merchants - centralized naming protocol, offchain and not interoperable one What’s absurd is that neither Cloudflare has planned to integrate onchain names - one of the most useful innovations in tokenized finance - which could change forever our transactions experience Centralized handles cannot be used across different wallet solutions and that‘a why all of those issuers that integrate onchain names will attract much more users #ENS

• 
  Barry Morgan (@techrealm) reported 8 minutes ago

  @eastdakota Same in my name :) problem O have is I have over forty trade names in my Cloudflare account that probably should be tied to their name but would then need to admin 39 other accounts to tie to them and likely breaking things in the process... Fun problem to find, not devastating for me but others might be more impacted.

• 
  sofia🤍 (@_sofiaaamoran) reported 8 minutes ago

  @mariagpts the cloudflare + separate host + separate VPS tool combo is exactly my setup too, never bothered fixing it either

• 
  Fajar Sentosa (@fajarsentosabuz) reported 9 minutes ago

  @Cloudflare The useful detail is that Astro did not let an agent simply close issues. It made the agent reproduce, diagnose, patch, and ship a preview for verification. That turns AI coding from code generation into maintainer capacity, with review still built into the loop.

• 
  Connor (@connortrenches) reported 10 minutes ago

  @mattzcarey @sleepercell34 Damn, so it was all fake bruh! Can we actual run a coin for you and send you fees to your legit github? What is the cloudflare mascot?

• 
  Yeti - (@Yetee_) reported 12 minutes ago

  @KentonVarda Maybe a dumb question here, could I essentially self host cloudflare workers? I’d just lose the edge serving powered by the cloudflare network

• 
  Vantix AI Agency (@VantixAgency) reported 12 minutes ago

  @geoprotocol @Cloudflare Cloudflare gives AI agents wallets but who owns bad purchases

• 
  absinthium (@absinthiumxmr) reported 13 minutes ago

  @Cloudflare **** your cbdc bullshit

• 
  Cluster Protocol (@ClusterProtocol) reported 13 minutes ago

  @Cloudflare traditional banking APIs are too slow and restrictive for autonomous agent execution loops

• 
  zerts (@zertsdev) reported 14 minutes ago

  @gyan_w3b @Cloudflare Trying to stay vigilant so I never miss MY RIGHTFULLY DESERVED HANDLE ever again!

• 
  Constantin Diez (@ConstantinDiez) reported 17 minutes ago

  Update on cloudflare OS, a nice UI but very very confusing to navigate. Panels open, close, disappear etc. Good concepts but really mixed up in different places. No support for pptx or other complex files, relies more on the LLM itself (e.g. pdf). Creates anything based on a code execution, looks like cloudflare workers so it can be deployed. Many LLMs supported, but not all such as Grok & Co. Would say a good starting point, tries to be enterprise but not there yet. A lot to learn though.

• 
  Arpit Bhayani (@arpit_bhayani) reported 25 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.

• 
  SaltyAom (@saltyAom) reported 27 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

• 
  Manu Otel (@manuotel) reported 29 minutes ago

  @catmanyau @Cloudflare Is the MCP that’s failing. The agent took the right actions. Makes me question a bit cloudflare’s dev tbh. How can you bee such a good proxy, but soo bad in AI? Their devs must be making easily 150k+$ a yr, this should be easy work…