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:

• 
  rita kozlov 🐀 (@ritakozlov) reported 4 minutes ago

  at a lot of companies, product's role is to come up with ideas, carefully groom the roadmap and narrowly define requirements for engineering to (blindly) follow this maybe makes for an "easier" product role but limits creativity (and accounrability) one thing that's unique about cloudflare is that ideas can really come from so many more places product's role is to help map those ideas to customer problems and make sure we actually solve them and help get those ideas in customers' hands (aka actually ship it and make it good!) it makes for a much more interesting role and breeds so much innovation and leads to better experiences because engineering is not exempt from taking ownership in the deliverable. "i shippped what's in the PRD" is not good enough. you own the customer problems & solutions together

• 
  63green (@63green) reported 6 minutes ago

  So @Cloudflare works overtime to destroy thei reputation by sending emails despite every notification turned off, and I’m willing to grant their request to never, ever trust this criminal company, and never use them. Any company willing to **** you by email will **** your data.

• 
  Japan Anime News (JAN) (@JapanAnimeNews_) reported 9 minutes ago

  A change to our Cloudflare settings appears to have caused access issues for some users. We apologize for the inconvenience this may be causing. Please bear with us for a few days while we work to resolve the issue. 🙏

• 
  Fardeem (@FardeemM) reported 11 minutes ago

  If you're on your way to building a billion dollar company that involves a web app, here are some of my notes on architecting the frontend. if you don't do this, it's probably fine but one day you'll hire someone to fix it but truly that person could be doing some other higher value thing if you make some key optimizations on day 1 you don't even have to learn anything you're gonna tell your agents to do it anyways! okay here it goes: - Make your server code generate a openapi spec which then generates all the relevant client side code. Never do this by hand. Typing backend types instead of generating them should be banned - You need to make a decision on how the client talks to the backend. rest/graphql works in which case please just use tanstack query. other libraries will look similar but tanstack query truly is goated. - if you want linear style sync setups or offline mode, think about this HARD and architect it from day 1. Bolting this on later is so tedious. - People like using plain react router but things have gotten a lot better since then. Try their new framework mode or just even use tanstack router. Use route data loaders. - If you store a lot of state in query params, make that a first class citizen and make sure its type safe. use nuqs or tanstack query. - Most apps just need a single state management situation for server state and thats it. If you have other bespoke needs, i have quite like zustand and xstate/store. - If you have a super interactive app where things come in and out of view, theres a lot of frontend state to maintain, music is playing and what not, lock in and learn xstate. Trust me if you wanna keep ur sanity, you need to model ur frontend as a state machine otherwise you're gonna be deep in useEffect hell - React compiler is here my friends, the days of useMemo and useCallback are gone. Update your priors accordingly - Tailwind is easy and fun but makes it really hard to maintain a large app with consistent styling. You need a "agent-first design system/component library" but maybe this is a rant for another day - Don't be afraid to hack your routing library to fit your needs more closely. A lot of apps have "drawers" to show additional info. You should 100% be able to say "here's a route, make it a drawer" and everything should be handled from there. - Managing loading and error states using isPending and isError is madness. Lean into Suspense and ErrorBoundary. - Figuring out a blessed path for websockets and SSE on day 1 i think will pay dividends in the long term if you're building anything AI related. - If you're building a SPA, don't use next.js. it literally makes no sense. Why would you do this. - Definitely deploy on Cloudflare or vercel. There are other services but trust, there have weird missing features. - Assuming you build something people want, the next job is to build the factory so it can efficiently build the thing. Act accordingly.

• 
  Elie Steinbock ~ getinboxzero.com (@elie2222) reported 11 minutes ago

  Got a Vercel bill down from $4,200/mo to $120/mo. Some notes: - This is a free B2C product that went somewhat viral. - To get cost down I first optimised Vercel itself. Better caching. Move images to Hetzner / Cloudflare / AWS. - I also switched off server rendering. This product didn't need it. Moved everything to SWR. These changes were needed for better caching. - The big drop at the end is because I moved a lot to a Hono server on Hetzner. - I reused an existing Hetzner server so there were no extra costs there. But even if using a new one, the extra cost would have been only another ~$30/mo. - For B2B products it's usually not worth worrying about. This product had 15k+ signups in the last month. If you have thousands of paying customers, you're making 7 figures per year and a few k to Vercel isn't critical. This product was free, so it was painful to be burning dollars on it. - No need to waste money you don't need to, but the peace of mind with Vercel handling any scale, and you having zero DevOps is a major plus. - You can always make the adjustments I did. It's easy with AI. You're not locked in forever. - The switch I made to Hono was a simple one. It doesn't have load balancing. The server should hold up, but for a B2B SaaS I'd invest more time in a stable setup (which would also cost more time and money). - Vercel makes less sense for a B2C app that goes somewhat viral. It's still my go to every time, but need to be ready to move if you do see some real growth. - The product still uses Vercel. But many of GET requests now go to Hono. PS, this isn't for @inboxzero_ai which is prosumer/B2B focused and isn't free (other than 7 day free trial).

• 
  Ciccio Diddo 🐧🇪🇺🚽 (@CiccioDiddo) reported 14 minutes ago

  @EddCoates another interesting cloudflare function is AI labirynt ... it create a ton of fake content filled with nofollow links generated by some **** IA... so the scraper spends a ton of resources to traverse all links then, if not enough start to ban by AS number instead of single IP

• 
  IJav (@javmung) reported 16 minutes ago

  @MSU_NW_FANG @MaplestoryU @nexpacetime Also need to test WARP From CLoudflare.. that helps a lot. But most likely is his/her ISP. mine was disconencting a lot, they did reset my NAT, and assigned me a public IP address, and problems are gone.. so routing probably the problem.

• 
  JD (@TooTrill4Thiss) reported 20 minutes ago

  @BoringBiz_ Every business doesn't need a custom agent. It needs an enterprise plan and a few capable devs who can map it, and deploy agents. building automation that don't rely on agent compute. like hello??? app scripts, compute engine, cloudflare workers. ******** are people doing?

• 
  𝗶𝗮𝗺𝟰𝘅 (🌷,🦈) (@iam4x) reported 23 minutes ago

  @DegenCT @TheCryptoNexus - Proxy the ui api of hyperliquid through cloudflare to fetch sub-accounts - Then implementing the spot trading with support of sub-accounts

• 
  bigdatachads (@bigdatachads) reported 25 minutes ago

  I've been building AI phone agents on @Cloudflare for a while now. v1. a Python container, fighting for every millisecond. v2. no container, the whole call on the edge. that was the real work. now that I have the stack down, I spent last weekend messing around. this is v3, a cartoon you talk to that remembers you and gets heckled by a second AI. all on Cloudflare primitives. three teardowns, first one tomorrow. follow along. @CloudflareDev

• 
  Brendan Irvine-Broque (@irvinebroque) reported 27 minutes ago

  dex is holding his Cloudflare product feedback hostage until I share this video watch so that I can learn what bugs we should fix

• 
  Dety (@Dety0) reported 28 minutes ago

  ServiceDesk tier list S: Cloudflare is down A: Password Reset, PC Crashing B: Data Backups C: Phishing Mails D: New User Onboarding, Meeting Room Setup F: Outlook Classic, PRINTERS

• 
  Sina Meraji (@sinasanm) reported 29 minutes ago

  totally forgot i can replace the scrappy cf onboarding in kimiflare with the new "login with cloudflare" oauth thingy

• 
  ƒrαeყ (@fraey0) reported 32 minutes ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?

• 
  Adam Rush 🛫 (@Adam9Rush) reported 35 minutes ago

  @JamesSherlouk Hosted on R2 @Cloudflare, zipballs each dependency and mints it so it can never change. More control, mainly, we can just manage it pretty cheaply, but ultimately do some other stuff with it. I would quite like to build a little internal dashboard that shows our dependency graph, etc.