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:

  • 0xanter
    xanter.ai (@0xanter) reported

    THIS TEAM TRAINED AN AI MODEL ACROSS 14 MACS IN 4 COUNTRIES, NO DATACENTER NEEDED His laptop's just one node in the network. The others are in Switzerland, France, and beyond, all synced over regular home internet. Pause at 0:05 👀 — 14 consumer Macs, across 4 countries, generating every single training rollout — each Mac runs int8 inference locally via MLX, one B200 GPU elsewhere handles the actual gradient updates — they only sync through Cloudflare R2, ordinary cloud storage, no dedicated datacenter interconnect — tested on a biomedical search task: pass rate jumped from 29% to 63%, tool-use rate from 22% to 84% — rollout generation is roughly 80% of the compute cost in this kind of training, and all of it ran on regular home machines Here's the mechanism: the hard part isn't running inference on Macs, it's that those rollouts come from slightly outdated, quantized weights running on a completely different kernel stack than the trainer. Two tricks fix that gap: sending only the ~0.5% of weight values that actually changed (82MB instead of a 9GB checkpoint), and filtering out the small fraction of tokens where probability estimates drift too far between the rollout machine and the trainer. Their bigger point: idle consumer compute worldwide already outnumbers the clusters behind today's frontier models. As top AI labs lock models behind closed APIs, training runs like this, on hardware people already own, are one path to keeping frontier-level AI development actually open. Would you let your own idle Mac or PC contribute compute to a training run like this?

  • jhleath
    Hunter Leath (@jhleath) reported

    this article will be out of date in 6 months, and the reason why is in the second paragraph: > We wanted off VMs because giving every user an always-on machine with attached disk was too expensive to scale. The hard part is that coding agents assume Linux. if you were a betting person, would you bet that either: a) someone will figure out a way to deliver full-VM semantics at a fraction of the cost, allowing coding agents to continue to assume Linux or b) everyone will converge on a cloudflare stack that requires rewriting everything into javascript? you can guess where I am, Linux isn't going anywhere. *especially* because it's: - portable across providers - users can build different price vs. performance vs. security options themselves - it works with 100% of the existing software out there there are *already* more interesting ways to fix costs in VMs, like Archil's serverless sandboxes which don't charge you at all during the "inference" part of the step what would happen to costs when we intelligently decide on the server-side, for each bash invocation, whether it needs real Linux or just-bash? this stuff is going to become 1000x cheaper

  • _dylanga
    Dylan Garcia (@_dylanga) reported

    @CherryJimbo @Checkm3out @Cloudflare I agree. I gave the region fallback feedback to them after their most recent ENAM outage

  • JasonTally
    Jason Tally (@JasonTally) reported

    @EricLGoldstein @dok2001 You can already get a PlanetScale database through the Cloudflare dashboard and get billed for it through Cloudflare so I was counting that as one of the things that happened “another way”. From a customer perspective I don’t think a full acquisition would change much.

  • helyoussfii
    Hamza (@helyoussfii) reported

    @vmod__ Aah never tried cloudflare for deployement actually They support deployement with docker compose ?

  • AdamSmielewski
    Adam Smielewski (@AdamSmielewski) reported

    @NickBlow @rivet_gg it would be great if they let you publish build artifacts externally from cloudflare, like wrangler version upload does internally. they could just wrap it in a docker container with env vars for service bindings or sth like that.

  • saltyAom
    SaltyAom (@saltyAom) reported

    @perpetualtalk Elysia does support Cloudflare Worker but this new version get a better support This runs on Bun 1.3.14 which is not Rust rewrite

  • 2WBIA_5
    2WBIA (@2WBIA_5) reported

    @AbuShekauGamer I don't have an issue with cloudflare

  • 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.

  • aquipongoalgo2
    kirua (@aquipongoalgo2) reported

    @a63738464 1.1.1.1 as issa cloudflare service

  • _ndianabasi
    Ndianabasi Udonkang (@_ndianabasi) reported

    @bdkjones @Cloudflare @Apple Ever since I stopped using Cloudflare's DNS proxy, I don't even know when they have downtimes. Most people don't need the proxy service but just use it as default when configuring their records on Cloudflare DNS. For many, DNS proxy is their performance bottleneck but they don't know.

  • JamesWelbes
    James Welbes - AI Bro (@JamesWelbes) reported

    I'm tired of messing with SMTP every time I create a form. Today I moved my main site off of WordPress and rebuilt it in Astro. I have a contact form on this website. I also have a "command center" that I built for myself that is a web app filled with useful things like a financial dashboard that shows me data from my stripe account and my invoicing software, a page with all my WordPress sites where I can update plugins and check the debug log, a bunch of useful stuff like that. When the form on my website is filled out and submitted, the submission is saved to a database (d1 on CloudFlare). My command center is connected to that database so it displays all my form submissions for me. the CloudFlare worker or d1 or whatever (still getting myself up to speed with the CloudFlare lingo) sends a push notification to my phone letting me know I received a new form submission. tapping on the notification takes me to my command center (which is just a PWA that I have installed on my computers and my phone). The one thing I'm losing is the ability to send the customer a thank you email which I'm fine with because there is 0 value in those emails for myself and the customer. They just get a nice "thank you" message on the website after submitting the form.

  • KnudRach
    Rach (@KnudRach) reported

    @Cloudflare can you help restore a staging site that went down?

  • rahul__gangotri
    Rahul Gangotri (@rahul__gangotri) reported

    `@ supabase/supabase-js can never hibernate on cloudflare DO as it require the changing ref. only way forward is to support both. costly, non hibernating supabase client package and my own package which is hibernate friendly and costs way less. lets do it!

  • perpetualtalk
    Mr. Code NJ (@perpetualtalk) reported

    @saltyAom Does Cloudflare support bun + elyisa? Is this in the rust rewrite?

Check Current Status