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
Paris, Île-de-France 1
New York City, NY 1
Manchester, England 1
Angers, Pays de la Loire 1
London, England 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:

  • RsThrive
    Chris O'Rourke (@RsThrive) reported

    @HackingDave I get these where they’re like “hey I can get up to 20 million seed funding to support you at Cloudflare” … thanks bro but we’re publicly traded and I have 0 to do with that.

  • sharanry
    Sharan Yalburgi (@sharanry) reported

    @Cloudflare worst part is it is impossible to monitor this latency

  • citedycom
    Citedy (@citedycom) reported

    Cloudflare Dashboard is temporarily unavailable. Claude down. What next. Aliens?

  • born2code
    احمد (@born2code) reported

    @threepointone I did that with fargate (so I can use OpenAI subscriptions), sqs and dynamo. The problem with workers is that cloudflare blocks the OpenAI subscription calls (I suspect this this OpenAI buy blocked at CF edge), which is a non starter at the rate I use tokens

  • aldexdev
    alex ▲ (@aldexdev) reported

    "Deploy it to the edge" was 2023's cargo cult. Here's the 2026 rule: run functions close to the data they read, not close to the user. Edge (Cloudflare Workers · Vercel Edge · Deno Deploy) — auth checks, geolocation, redirects, A/B splits, header rewrites. Latency-sensitive, stateless, reads from cache or edge KV. Never a DB call. Region (Vercel Fluid · Fly Machines · Lambda in DB region) — RSC data fetch, Server Actions, CRUD, anything touching your primary DB. Anything more than 2 sequential queries belongs here, not at edge. Origin (Railway · Fly · your own boxes) — long-running, WebSockets, uploads, scheduled jobs, queues. Anything that breaks the request-response shape. Serverless will bite you here. The 2024 mistake: putting DB reads at the edge because "edge = fast." You add latency, not save it — every round-trip from Sydney to us-east-1 for a Prisma query costs you 200ms and a rate-limit ticket.

  • VelkoMinchev
    Velko Minchev (@VelkoMinchev) reported

    Day 29 📅 We had our first outage. Cloudflare ran maintenance on their infrastructure and TimerOS went down with it for a stretch. Not our code — but that hardly matters to someone who can't log in. What I care about is that everything behaved: → Incident alerts hit my inbox immediately, so I knew before anyone had to tell me → The status page reflected it live — anyone checking got a straight answer instead of a spinner → And I improved it mid-incident: incidents now open in the TimerOS support system too, so there's a written trail, not just a red dot You don't find out whether your transparency is real until something breaks. Ours held. Today: last stretch of road, heading home 🚗 Back at the desk tomorrow — Cloudflare and I have unfinished business. 😤

  • Mauker
    Mauricio - Mauker Makes 🇧🇷🇩🇪 (@Mauker) reported

    @3DInPhil @reprinted3D @printablescom It's like what you said. That's not really on Printables. When using a VPN, you share an IP address with many people, and one of them probably did something bad that got that IP banned. The alternative is to change the server, or try to reason with Cloudflare.

  • samwcomputer
    sam with his computer (@samwcomputer) reported

    cloudflare just made blocking ai training bots the default on ad-supported pages starting september. opt-in security was never going to work, defaults are the only setting that actually gets used

  • TheHackersNews
    The Hacker News (@TheHackersNews) reported

    The attacker’s own server address never appears on the wire. msaRAT uses Cloudflare to establish the connection, then routes the entire WebRTC channel through Twilio. Defenders see the victim’s browser talking to legitimate services. No Chrome or Edge patch fixes this. It exploits neither browser. Hunt for Chrome or Edge launched by an installer, service, or another non-interactive parent with --headless=new and --remote-debugging-port. See “Hunting Notes” in the article.

  • pj_stew
    Pete Stewart (@pj_stew) reported

    @founder_sohan You can use mist open source models with Worker AI, which is a fraction of the cost of SaaS services like OpenAI, and if you use Cloudflare AU Gateway with it, you can also use any of the main SaaS services and switch between models as needed. You can see in the article I wrote yesterday about video transcription that I used Whisper on Worker AI to make a much cheaper transcription service for Achene.

  • OJI_OJI_00
    Yosefu (@OJI_OJI_00) reported

    @Spectra010s @Cloudflare By the time you fix that issue, you would have known more about computer networking and how cloudfare works

  • JeromySonne
    Jeromy Sonne (@JeromySonne) reported

    Slack is failing, some web apps are throwing me cloudflare 504s. Incoming cloudflare outage in 3, 2, 1

  • axldefi
    Alex🌖⃤ (@axldefi) reported

    The job is not done yet, the person/entity doing these false reports just to slow us down, started reporting on our IMAGES subdomain now. Crazy to me how all of these databases flagged a Cloudflare Image hosting url as phishing when the only thing they do is to serve a image and main website is full GREEN. We'll clear these one out as well, one by one. We got motion now! Never give up! We're building at maximum speed and fire to elevate these blockers in the road! Ride until Valhalla!

  • longterm_inv
    MichaelB (@longterm_inv) reported

    @ProCyclingStats @Kevin_LTR @Cloudflare Well an API is super efficient on your side and you can super easy throttle them - scraping requests are a nightmare and never really to stop 100%. And loyalty - nobody wants to put his beloved scripts into garbage just to avoid to pay some bugs per months (see AI tools now).

  • beyondcontent
    Andrew McGarry (@beyondcontent) reported

    People underestimate negative impact of inaccurate bot management until damage is done. Don't expect Cloudflare to be subtle by default. False positives can be a different kind of bad. Log files @datadoghq can help.

Check Current Status