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:

• 
  Special Situations 🌐 Research Newsletter (Jay) (@SpecialSitsNews) reported 3 minutes ago

  New Activist Name: Shares of $MTN are trading up 13% at $141.65 on Thursday, rebounding sharply from their 52-week low of $118.51 hit earlier this year, as the Semafor scoop circulates across trading desks. The intraday move lifts the company's market cap to roughly $5.05 billion. According to Semafor, Vail's bankers are tasked with assessing vulnerabilities across a broad front: labor unrest, weather-related demand swings, and the specific pressure campaign being waged by Prince, who co-founded Cloudflare (NET). Prince told a local Colorado publication in June 2026 that he is willing to invest $500 million in Park City Mountain Resort and admitted he has already fielded calls from activist investors probing Vail's weaknesses. His preferred blueprint would see Vail pivot to an asset-light model, acting as a partnership facilitator rather than a direct mountain owner, a structure that would almost certainly require carving up the company's core real-estate holdings. The timing is awkward for management. Vail reported fiscal Q3 2026 earnings per share of $8.81, missing the consensus estimate of $9.09 by 3.1%, while revenue of $1.21 billion came in roughly $10 million below forecasts. The company subsequently cut its fiscal 2026 net income guidance to a range of $128 million to $162 million and trimmed Resort Reported EBITDA guidance to $735$755 million, down from the prior range of $745$775 million. Net debt has climbed to $2.65 billion from $2.24 billion a year earlier, pushing net leverage to 3.5x trailing twelve-month EBITDA as of April 30, 2026, while cash on hand stood at $371.4 million. Into that environment, the board moved in May 2025 to recall Rob Katz, the executive who originally built Vail into a multi-mountain empire, ousting his hand-picked successor in the process. Katz has since focused on the operational grievances that drove customer dissatisfaction, particularly lift-line congestion and chronic labor shortages, introducing products like Epic Friend Tickets and discounted super-advanced lift tickets that are showing early traction. The move signals that Vail's board views operational credibility as its first line of defense against any activist pitch centered on mismanagement. Management also has a financial lever to highlight in any proxy fight. The company pays a quarterly cash dividend of $2.22 per share, with the next payment scheduled for July 9, 2026, equating to an annualized yield of roughly 6.6% at current prices. That yield argument, steady cash returns while the turnaround plays out, is a standard defensive talking point, though it carries less weight when leverage is rising and guidance is being cut. Investors will get a clearer read on whether Katz's operational fixes are gaining traction when Vail reports fiscal Q4 2026 results, tentatively scheduled for September 24, 2026. The setup is challenging: consensus EPS for that quarter stands at -$5.05, with eight analyst downward revisions in the past 90 days and no upward revisions, reflecting the structural headwinds Prince and any allied activist would likely exploit.

• 
  Zerops (@zeropsio) reported 6 minutes ago

  @shubh19 @isha_singh06 Hey! Zerops fits the Railway/Render slot when the backend needs managed Postgres/Valkey on a private network next to it, hardware-priced. Pair it with Cloudflare for static the same way.

• 
  Fardeem (@FardeemM) reported 6 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.

• 
  Matt Carey (@mattzcarey) reported 7 minutes ago

  Day 0 support for MCP servers on Cloudflare, with Workers OAuth Provider. Thanks to our customers for working with us to ship this for the wider ecosystem :) Sounds small but this is massive for MCP auth in large companies.

• 
  Diogo D (@DiogoTheReal) reported 9 minutes ago

  @EddCoates @Cloudflare rate limiting might help

• 
  SpikeViper (@spikeviper) reported 10 minutes ago

  I am once again asking @Cloudflare for a response on why their support is radio silent on what is now a shady billing situation

• 
  پارسوا (@imparsua) reported 12 minutes ago

  @DougMadory I think the udp whitelist has been set up on this network and is limited to a number of large global resolvers such as Google, Cloudflare and etc ...

• 
  sco2084 (@vega_yaa) reported 13 minutes ago

  @rohit_jsfreaky What if I subscribe to private DNS servers ..... let's say cloudflare? Will that help? I mean I'll put those DNS swrvers in my laptops TCP/IP config with ISP provider for my home internet.

• 
  Francisco T. Barbosa (@Cisco_research) reported 15 minutes ago

  @YashasGunderia I believe this is more a Cloudflare thing. Lots of issues with log in/log out

• 
  Nick Sunny (@suny_nick) reported 20 minutes ago

  @EddCoates I had similar issues. If you use Cloudflare, you can do what I did

• 
  JD (@TooTrill4Thiss) reported 23 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?

• 
  Lachlan (@lynx769) reported 24 minutes ago

  @EddCoates Are you using Cloudflare in front of it? It should help.

• 
  KarenR (@heykarenrc) reported 26 minutes ago

  When I built d1-studio, I was still early in my transition from UX to development. At first, I just wanted the simplest stack possible. Something lean. Something affordable. Something I could build with fast. Like many new devs, I started with the familiar stack: Next.js. Supabase. Vercel. AI helping me along the way. Supabase was great to get started. I still like it. But as I built more products, I started noticing the small costs and tradeoffs that you only understand after shipping. Storage. Egress. Deployment limits. The usual “newbie learns the hard way” stuff. That pushed me to look for a stack that fit how I wanted to build. Then I found Cloudflare. Workers. Pages. D1. R2. Queues. Generous free tier. Simple deployment. Close to the edge. I slowly moved more of my projects there and never really looked back. But there was one thing that kept slowing me down: Cloudflare D1 local development. D1 is great, but working with the database locally felt too slow. I didn’t want to keep jumping between CLI commands just to inspect tables, edit rows, run SQL, or check data while building. I also didn’t want a tool that required a long setup. My thinking was simple: The database is already in my Cloudflare project. The wrangler.toml is already there. Why can’t a studio just detect it and work? That became the trigger for D1 Studio. A native database studio for Cloudflare D1. No complicated setup. No extra database connection string. No heavy workflow. Just run it inside your project and start working with your D1 database faster. You can inspect tables, edit data, run SQL, and work with local or remote D1 without fighting the CLI every few minutes. It started as a tool I needed for myself. Now it’s getting used by other Cloudflare developers too. This week it hit 311 weekly downloads. Not a huge number in the grand scheme of things, but for me it means a lot. Because this is the first product I built that truly came from my own pain. Not a random idea. Not a trend. Not something I forced. Just a problem I kept hitting until I finally built the tool I wished existed. That’s been the biggest lesson for me as I move from design into development: The best products are often not born from brainstorming. They come from friction. Something feels slower than it should. Something takes too many steps. Something breaks your flow. And eventually you think: “There has to be a better way.” That’s how D1 Studio started. And seeing people use it for their own Cloudflare projects is still one of the best feelings.

• 
  Jasper Disney (@jasper_disney) reported 28 minutes ago

  As an unsuccessful app builder, I only need to pay 5 dollars to Cloudflare each month. Life is not that bad.

• 
  Aly (@alishteinn) reported 29 minutes ago

  Most Next.js websites are entirely too slow. I just boosted the Cursor Baku community site performance from 77 to 98. It is deployed on @Cloudflare, and the fixes were incredibly simple. If you want lightning-fast load times, steal these 4 tips: • Resize images to their actual display size before committing • Set minimumCacheTTL in next.config to cache image at the edge • Always set sizes on Next.js <Image> or retina fetches 4× the bytes • Wrap R2 reads with caches.default to serve media from the edge Fast load times build trust. Stop losing users over a slow website.