1. Home
  2. Companies
  3. Cloudflare
  4. Outage Map
Cloudflare

Cloudflare Outage Map

The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Cloudflare users affected:

Less
More
Check Current Status

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Manchester, England 1
Angers, Pays de la Loire 1
London, England 1
Noida, UP 3
Jewar, UP 1
Braga, Braga 1
Paris, Île-de-France 2
Prievidza, Nitriansky 1
Farmers Branch, TX 1
Helsinki, Uusimaa 1
Crisfield, MD 2
Nanaimo, BC 1
New York City, NY 1
Istanbul, Istanbul 1
Greater Noida, UP 1
Augsburg, Bavaria 1
Bengaluru, KA 1
Montataire, Hauts-de-France 1
Check Current Status

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:

  • calebsylvest
    Caleb Sylvest (@calebsylvest) reported

    @jasondoesstuff Skip the CMS. Recently did the same. Used Claude to build everything Used Astro. Deployed to Cloudflare. Writing with MDX. Pre-rendered everything and served from Cloudflare edge network. Basically a fast as possible.

  • stjeanp
    Patrick St. Jean (@stjeanp) reported

    @EddCoates I dealt with some of the same stuff, ended up putting them behind Cloudflare proxies, which helped somewhat. The biggest fix was blocking specific ASNs. Specifically AS132203.

  • heykarenrc
    KarenR (@heykarenrc) reported

    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.

  • nikhildp
    Nikhil Agarwal (@nikhildp) reported

    @dinasaur_404 @Cloudflare Yes looking for billing cap. How do you test dynamic workers as well as dynamic workflows in local dev? We had a disastrous outcome of losing $800 because the deployed code ran into infinite loop using dynamic workflow. Support team was not at all helpful.

  • zebassembly
    zeb (@zebassembly) reported

    @astuyve @boristane Yeah we aren't happy that the limitation has existed for so long either. We're working hard to try to not paint ourselves into a corner when the o11y platform we've built for Workers expands to being used for other products. There are many shortcuts we could have taken to got this shipped sooner but they may have put us in a state where we later couldn't reconcile it with tracing for another product. We're really going all-out for the o11y platform we're building within Cloudflare and that'll inevitably slow things down by preventing us from taking the easy paths.

  • Alon_iploop
    Alon M. (@Alon_iploop) reported

    @BenjaminFlatz Stealth helps, but most Cloudflare failures are environment issues: IP reputation, geo, sticky sessions, and consistent browser state. IPLoop provides the residential network layer so Playwright/Scrapy stacks don’t fail just because the traffic looks wrong.

  • armeetjatyani
    Armeet (@armeetjatyani) reported

    @tomhaerter Primarily Cloudflare now. GCP support is extremely sluggish

  • fataloops
    oops (@fataloops) reported

    @EddCoates I have a (conspiracy) theory about this- Cloudflare is the one doing the scraping, millions of requests Your only option is to use cloudflare or take down the site

  • ShantanuVL
    Shantanu Landore (@ShantanuVL) reported

    @itsasmolsush Oof well my non tech tech company has everything set up over cloudflare so we need to log in with MFA once a day... and the prompt to login comes at the worst point of the day everyday so

  • chirag
    Chirag (@chirag) reported

    There's a case to run a meta network on Cloudflare rails. These childish things by the regime can be bypassed at scale.

  • AyushmanMallick
    Ayushman Mallick (@AyushmanMallick) reported

    5/ You hand over a paid API key, so it's security-reviewed. The key goes only over HTTPS, only in a header, to one stateless @Cloudflare proxy that never stores it. XSS and SSRF hardened. Templates use a strongly-consistent Durable Object. The proxy is fully open-source.

  • KamilFabian
    Kamil Fabian (@KamilFabian) reported

    @EddCoates cloudflare free tier. Solved my 1mil req per minute problem. Just make sure to set up properly.

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

    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.

  • jsneedles
    Jeff Needles (@jsneedles) reported

    @Hussain_Joe @_ceifa Well, the key is its pretty much managed, just not e2e. Like it's Cloudflare Workers + pipelines + queues -> CH cloud. All managed services! Just the raw volume makes most "pure" managed analytics providers extremely prohibitive -- like prob 10x the cost at least. Of course, there's other options that are really self hosted that are less analytics-focused... or things that rely more on object storage as the source of truth (like R2 SQL, which would actually prob be cheaper) But I've put in maybe 10 hours of necessary maitenance in the last year, occasionally the analyst who uses the system will ping me for questions/advice etc -- but raw infra/system wise, like 0 issues!

  • coffee_oil
    Coffee and Gun Oil (@coffee_oil) reported

    @ShamashAran I was on cloudflare ******* with DNS last night. I hate DNS The **** I run locally works fine, but that's because it's me and a text file.

Check Current Status