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
Istanbul, Istanbul 1
Greater Noida, UP 2
Paris, Île-de-France 1
Crisfield, MD 1
Noida, UP 2
Augsburg, Bavaria 1
Bengaluru, KA 1
Montataire, Hauts-de-France 1
London, England 1
Attleborough, England 1
Colima, COL 1
Leuven, Flanders 1
New Delhi, NCT 2
Mâcon, Bourgogne-Franche-Comté 1
Amsterdam, nh 1
Ashburn, VA 1
Rosario, SF 1
Merlo, BA 1
Frankfurt am Main, Hesse 1
Birmingham, AL 1
Dayton, OH 1
Miami, FL 1
Osnabrück, Lower Saxony 1
Bulandshahr, UP 1
A Coruña, Galicia 1
Easton, PA 1
Guayaquil, Guayas 1
El Port de Sagunt, Valencia 1
Medellín, Antioquia 2
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:

  • ashnallawalla
    Ash Nallawalla (@ashnallawalla) reported

    @gaganghotra_ Great reminder. Most geo-blocking plugins and CDN rules need a specific exemption for known crawler IP ranges. Cloudflare and Wordfence both support this, but it's rarely enabled by default — so it's worth checking even on sites that seem to be working fine.

  • JessePeplinski
    Jesse Peplinski (@JessePeplinski) reported

    @adahstwt Cloudflare. Good developer support. I switched from name cheap

  • shipwithjay
    buildwithjay (@shipwithjay) reported

    Spent 3 weeks debugging "slow API" on my biggest app. It was Vercel cold starts on the hobby plan. Moved one function to Cloudflare Workers. Latency dropped from 1.4s to 90ms. Same code.

  • SergioDiPietro
    Sergio Di Pietro (@SergioDiPietro) reported

    @Cloudflare @CloudflareHelp @eastdakota Workers AI advertises $0.10/M tokens but bills in undisclosed "Neurons". Got charged $2,457 for a fraction of that usage. Ticket #02066519 — 34 days, copy-pasted replies, forced to pay under cancellation threat. Help?

  • builtbyfaithh
    Andrejco (@builtbyfaithh) reported

    Today I finished setting up Cloudflare for a website. It was my first time doing the full process, so I was definitely a bit scared. Not because Cloudflare itself looked impossible. But because DNS is one of those t hings where one wrong record can break something important. • The website • Email • Webmail • cPanel • FTP So I was extra careful. I reviewed the DNS records Cloudflare automatically imported. Then I compared them with the original records from cPanel. Then I checked them again. And again. I made sure only the main website records were going through the Cloudflare proxy. • Mail • cPanel • FTP • webmail and other service-related records stayed DNS only so they would not break. I also found one small mismatch in the MX record and corrected it to match the original DNS setup. After that, I confirmed the A record IP matched the server IP in cPanel, collected the Cloudflare nameservers, changed them on the domain, and waited for propagation. At the start, it felt scary. By the end, it made a lot more sense.

  • niknak
    niknak (@niknak) reported

    @twolays @Cloudflare Very bad

  • Wallage
    Philip Wallage (@Wallage) reported

    3 weeks ago Cloudflare published a beautiful blog post about redesigning that little widget you click to verify you're not a robot. WCAG 2.2 AAA. Rigorous user research. Eight participants from eight countries, blinded testing. They wrote that "when visual consistency conflicted with readability, readability won. Every time." Today they launched their new marketing homepage. No blog post about it. No press release. No tweet from Matthew Prince. For a company that announces a quarterly Forrester report and individual API changelogs, the silence on a full marketing site relaunch is loud. The reaction on X has been brutal. Some of what's being flagged: - Login button goes to the sign-up page - "View docs" link on the careers page points to R2 storage - Multiple users with no colourblindness saying the contrast hurts their eyes - Broken scrolling on Safari - Doesn't render properly on mobile - An em-dash in the hero headline, days after a whole blog post about removing em-dashes for readability A Cloudflare engineer replied to the thread: "expect fixes in the coming days." I'm not piling on Cloudflare. Shipping at their scale is hard and they'll fix it. The contrast between the two artefacts is the lesson. The blog post about the human-verification widget is what design teams want to be true about themselves. Process. Research. Accessibility as a value. The marketing homepage is what actually ships under deadline pressure when nobody owns the QA pass. If you look at most e-commerce sites I audit, the same gap exists. The brand book says "accessible, considered, customer-first." The product detail page has 11px grey-on-grey microcopy, a CTA that disappears on hover, and a sticky add-to-cart that covers the price on mobile. The blog post you want to write about your design system matters less than the page where you take money from people. Audit what you actually shipped, not what you meant to ship.

  • Caddue
    kitcatixoxo || Margaritamar (@Caddue) reported

    btw the problem seems to be cloudflare and many apps suffer momentarily

  • yagyaansh
    A Pale Blue Dot (@yagyaansh) reported

    @gmail please help. I have been locked out of my account. the shown phone number is mine but i am not recieving any code on this number even after multiple tries and now I have been locked out of my account completely. I create this new account for an app that I was planing to launch and all my vercel, supabse and cloudflare accounts related to the app are linked to this id. PLEAE HELP!!! :(( I use a little over 5 gmail accounts for different purposes bu this is happening with me for the first time since I have been using Gmail. @Google

  • ayushagarwal
    Ayush Agarwal (@ayushagarwal) reported

    @snipextt @dodopayments @Cloudflare working on that too tbh. distribution for AI-native products is still completely broken right now.

  • Orangek21865157
    xiaoshi · AI SaaS Patterns (@Orangek21865157) reported

    @Digi_Ingenuity Yes. Worst offenders I see: 1) Cloudflare Bot Fight/Super Bot Fight 2) challenge rules for unknown UAs 3) Wordfence/rate limits on bot-like fetches 4) edge middleware treating GPTBot/ClaudeBot differently Audit: compare browser UA vs AI UA status, body, WAF headers.

  • eashish93
    Ashish Rawat (@eashish93) reported

    I was trying to solve a cloudflare sandbox related to HMR (websocket) with opus 4.7 for past three days and filed multiple issues on their repos (sandbox, workers-sdk etc). I almost gave up because it's a issue in their sdk, then comes the gpt 5.5 which fixes the bug in just one pass.

  • thomasklemenc
    Thomas Klemenc (@thomasklemenc) reported

    @DarkSeed347 @jack_thurling Oh okay that's really bad. Sorry for the inconvenience. I am using Cloudflare for hosting and DNS and I'll try to solve this issue. Can I DM you?

  • devfredy
    Fredy Sandoval⚡️ (@devfredy) reported

    @asaio87 Will he secure your app behind a Cloudflare bot protection and set a Tailscale network for zero trust configuration, ensuring the database is unreachable for public internet?

  • iamrknain
    Ravi (@iamrknain) reported

    The Problem: During the attack, I had to manually block hundreds of abusive IPs to avoid blocking entire ASNs (which would drop legitimate users). Cloudflare WAF is amazing, but real-time rate-limiting on every single request can get very expensive very fast.

Check Current Status