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:

• 
  hekt0 (@rq_crypto) reported 1 minute ago

  @metasal @vercel @Cloudflare my clanker thinks $pepe is a frog dating app the rename would fix that instantly

• 
  SaltyAom (@saltyAom) reported 2 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 Response/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 significant performance degradation compare to what it should be because Node.js simply decided not to implement this specific feature "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 WinterGC committee (now WinterTC) to draft this standard, just to implement the bare minimum for fetch and not an HTTP Server? Like come on This is like Apple not wanting to implement RCS, but at least Apple has the elephant in the room of losing money, but here, there seems to be no valid reason at all to not implement it besides just to watch people mad 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/runtme to sign so we can have the evidence that the majority library/framework want it or what? Because I'm willing to go to that length because of how frustrating it is right now

• 
  Valentino Giudice (@Aspie96) reported 2 minutes ago

  @mycoliza This is funny. Microsoft tried to convince us that Windows 10 was not an operating system (which it was/is, good or bad it is an OS). Now Cloudflare tries to convince us that CloudflareSlop is an OS.

• 
  Malik (@MalikHHarouna) reported 4 minutes ago

  @0xJuliechen @Cloudflare Damn

• 
  Nils Groove (@nilsgroove) reported 5 minutes ago

  Don’t use that stack. That whole list is pure AI-generated BS. No way that guy actually uses every single one of those tools on real apps. You only need @Cloudflare. That’s it. The list is usually the typical suggestion when you ask AI what stack or tools to use. You can keep Next.js. That’s fine. Just do this instead. Host it on Cloudflare Pages and Workers. Vercel is great until the bill shows up or someone in Asia tries to load your site. Cloudflare runs on a real global network, gives you unlimited bandwidth for free, and doesn’t punish you when traffic spikes. The OpenNext adapter makes Next.js work just as smoothly. Ditch Convex. Use Cloudflare D1. It’s a simple SQLite database that lives right on the edge next to your code. No extra service, no weird pricing, no waiting for some third-party backend to wake up. Reads are fast everywhere and the free tier is actually usable. Auth can stay Clerk if you really want the pretty UI. Or just run Better Auth on Workers with D1. Either way you stop adding another paid tool that scales with users. Emails? Forget Resend. Cloudflare’s own Email Service lets you send and receive straight from your Worker. No extra API keys, no separate dashboard, no monthly surprise. Keep Stripe and Tailwind. Those two are solid. Everything else on that original list is just AI padding. The result is one platform instead of five. Cheaper, faster for people outside the US, and you don’t have to babysit a pile of free tiers that suddenly start charging. This is the stack that actually survives past the first hundred users.

• 
  daily netizen (@dailynetizen24) reported 5 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.

• 
  Helen JJJ (@JJJ_Helen) reported 6 minutes ago

  🤖💳Giving agents wallets solves payment friction by creating a new permissions problem. The key product is not autonomous spending—it is programmable limits, revocation and audit trails. #AgenticPayments #x402 #Cloudflare

• 
  𝐁𝐚𝐫𝐫𝐞𝐥 (@BarrelOnChain) reported 9 minutes ago

  Cloudflare just gave AI agents programmable wallets to hold stablecoins and pay for things online. So bots can make payments now, and you still can't get a human on customer support. Priorities.

• 
  Al-Yazen (@AlYazen_Wahaibi) reported 11 minutes ago

  @MarianaMorales8 @bingersapp Hey there!, Before you start typing your email, please wait for the Cloudflare "Verify you're human" checkbox to appear Once it appears, complete the verification first, then proceed with entering your email. I believe this is a glitch Many people faced the same issue

• 
  De UniQue 👑 (@Abdulkarim2) reported 14 minutes ago

  Cloudflare wants AI agents to pay $0.001 per API call. A standalone card payment would cost more than the call itself. Its new Monetization Gateway lets a service return an HTTP 402, quote a price, and receive payment before serving the request. At launch, settlement runs on stablecoins over x402. Machine billing already existed, but it ran on accounts, API keys, and invoices piled up over time. What was missing: a way for an unknown agent to pay per request, without the seller onboarding it first. Stablecoins didn't invent machine commerce. They made the smallest transaction worth collecting.

• 
  harmony ! ΘΔ& 💚🌱 (@aharmonysought) reported 14 minutes ago

  @LUVONAWlRE yeah. everything else was loading fine which is why i tweeted this to begin w, when i have this issue where only one site takes like two minutes per page to load it's usually toyhouse so. looping back around to cloudflare and the lack of staff it's probs one of those factors LMAO

• 
  CryptoCook (@ThCryptoCook) reported 14 minutes ago

  @CoinDesk @Cloudflare The technology is promising, but real-world adoption will depend on how many services actually support it

• 
  logan (@logantoday) reported 14 minutes ago

  @HeirLegacy on @Cloudflare OS 'Executive summary The headline finding is not "we should adopt Cloudflare OS. " It is that we independently built roughly 80% of Cloudflare's Gatekeeper architecture already, and the remaining 20% is precisely the set of problems we explicitly deferred in code comments. Great minds i guess

• 
  JTCrawford (@JtCrawford) reported 17 minutes ago

  Cloudflare ditched enterprise security tools for a $58/month AI agent while vendors charge $200k for the same capability. Either security has the worst price discovery in history or we've been getting fleeced. #InfoSec #DefenseIndustry

• 
  Manas Choudhary (@_manaschoudhary) reported 17 minutes ago

  Oh man, how come Cloudflare is able to do so many things and knew about these problem statements a year ago????