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 2
Jewar, UP 1
Braga, Braga 1
Paris, Île-de-France 1
Prievidza, Nitriansky 1
Farmers Branch, TX 1
Helsinki, Uusimaa 1
Crisfield, MD 1
Nanaimo, BC 1
New York City, NY 1
Istanbul, Istanbul 1
Greater Noida, UP 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:

  • Jimmyq_startup
    Jimmy Q (@Jimmyq_startup) reported

    [Fixed] Domain verification for Gmail (Cloudflare) TDLR: Expected ~10 min setup took days; found a bug in Gmail domain verification and a workaround. 1. Initially, Cloudflare's direct verification was used in Google, and it added the TXT "Google-site..." in DNS. Nothing else was prompted. Waited a long time, no update. 2. Fix: went to manual verification and saw that I also have to add a CNAME in DNS. After that, hit finish and - Viola! - domain verified. #gmail #indiedev

  • Precious_Ngan
    SHELBY (@Precious_Ngan) reported

    If the website uses a CDN (Content Delivery Network) server like Microsoft Azure CDN, Fastly or Cloudflare, the DNS server will send the IP address of the CDN server instead of the website's original IP address.

  • muvluvist
    C³ cyre in exile (@muvluvist) reported

    @Night_Fiber son cloudflare warp is not doing **** i'm still on the opposite side of the globe🥀🥀 the signal isn't gonna be traveling faster than light all of a sudden

  • Sol87_live
    sol87 (@Sol87_live) reported

    @JonathanLigmas @Luffydude1 @prestonjbyrne Right now it's as easy as signing up for any web service provider(they can't block AWS, Azure, Cloudflare) copy/paste 1 thing into the terminal, put the file it creates to any device, now you have VPN on any major service provider.

  • ryanyates1990
    Ryan (Struggling with life NGL) (@ryanyates1990) reported

    Really fed up with #Hugo now & hosting my blogs on #Cloudflare as things have broken that should not have done. So yet again I'm going to be rebuilding my blog and working out where I'm gonna be hosting it. Something that really I did not want to be having to spend time on tbh

  • vijaytupakula
    Vijay Tupakula (@vijaytupakula) reported

    @HotAisle @Cloudflare Oh no! I haven’t used their email service yet. @Cloudflare can you help?

  • MillsNotMiles
    Mills (@MillsNotMiles) reported

    @Kolar_Dev @softwareengng @EOEboh Yeah Cloudflare free tier doesn’t support this

  • mertmetindev
    Mert Metin Tekdemir (@mertmetindev) reported

    📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

  • camilopenalver
    Camilo Peñalver (@camilopenalver) reported

    Cloudflare blocks AI bots by default without asking you first, and that's bad.

  • VincentPsychSE
    Vincent-psych (@VincentPsychSE) reported

    @George4Tea @KnownHeretic I advocate for steps like 'controlled frustration' — implement strict DNS filters (Next-DNS/Pi-hole, CloudFlare), throttle speeds during certain hours, intermittent router restarts, and signal-limiting via access points or parental apps—these deter without destruction while maintaining oversight. Also, devices should not be upgraded or improved, research shows that even milliseconds delays change the dopamine hit. Parents often say they'll "do whatever it takes" but they won't affect the internet because they also rely on it for emotional regulation.

  • AlexYusdut
    Alex Y (@AlexYusdut) reported

    hosts auto-issue via Let's Encrypt. redirect loops just wait, don't fiddle - Cloudflare proxy (orange cloud) in front of Vercel/Netlify →It silently fails for 2 reasons: - DNS hasn't propagated yet →HTTPS: you don't buy a cert in 2026 —

  • piyushxcreates
    Piyush Chandwani (@piyushxcreates) reported

    @kalashvasaniya @scrolllaunch I'd suggest buying an vps and installing coolify, hardening it by no root login and passkey based ssh and adding cloudflare tunnel in front... I've an 8 gb ram and 150gb ssd, which hosts 3 next js apps, 4 static sites and I pay $10/month with max security via this setup

  • Kumar_Vikas__
    Vikas Kumar (@Kumar_Vikas__) reported

    i'm building on @Cloudflare right now. Workers for hosting, D1 for the database, R2 for object storage, KV for caching. but i'm not trusting any of it to stay forever. every service sits behind an adapter in my architecture. app logic never talks to D1 directly, it talks to a data layer that happens to be backed by d1 today. same story for R2 and KV. if any one of these becomes a problem later, cost, limits, whatever, i want to swap it out without touching a single line of business logic. decoupling isn't glamorous work. you don't get to show it off. but it's the difference between a migration and a rewrite. if you've done this on Cloudflare before, tell me what broke.

  • ClickDopamine
    Click /Kael Vulpis/ Dopamine (@ClickDopamine) reported

    @CBrewer I'm trying to get it as tight as possible, so it will scale smoothly, but that front loads all the problems now rather than later, later is just throw hardware at the problem. This might be a cloudflare issue

  • LexSokolin
    Lex Sokolin | Generative Ventures (@LexSokolin) reported

    @Cloudflare is trying to make HTTP 402 useful. The web has always had a “Payment Required” status code. It mostly sat there as internet archaeology because humans do not want to stop every six seconds and pay four cents for a page, dataset, or API response. Agents are different. An agent can request a resource, receive a machine-readable price, pay in a stablecoin, attach proof, and move on. No checkout page. No subscription bundle. No ad unit. No “contact sales.” Aka a novel way of internet monetization. Cloudflare is approaching this from the edge: sit in front of the resource and enforce payment before access. Mastercard is approaching the same problem from trust and credentials: give machines spending rules, limits, authorization, and settlement. Same direction from opposite ends. The useful version is not an AI assistant buying sneakers. That is demo theater. The useful version is software paying for software: - data - APIs - model calls - verification - routing - compute - tools This is where stablecoins stop being a crypto slogan and start behaving like small-denomination internet money. The web does not need every machine to have a bank account. It needs a way for software to pay a toll and keep moving.

Check Current Status