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:

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

  • aor4life
    AOR 4 Life (@aor4life) reported

    @Cloudflare If you change all the right fields on your original webhost, then pretty quickly. When I last did it, I thought all I had to change was one screen, but in actual fact I had to get help from Customer service to change a few more. Doh!

  • cultvgnews
    Cult News (@cultvgnews) reported

    I will never be convinced that Cloudflare performs a useful service. All I see them doing is slowing down the internet.

  • LukeYoungblood
    LukeYoungblood.eth 🛡️ (@LukeYoungblood) reported

    @curtjg1971 @Cloudflare We put in a limit request Monday but still no resolution. They have really good service otherwise, but I hope the people handling limit increases are eventually going to resolve it.

  • MizzAugust7
    August_AA_Oldtimer (@MizzAugust7) reported

    @selmaca_ @TimLamb17916673 I found this- Similar errors on X are often linked to server-side issues, backend maintenance, or problems with Cloudflare infrastructure rather than user error. I Hope thats all that was! Thank you SO Much ! 💙

  • aistartuplabs
    Nick Stebbings | AI Startup Labs (@aistartuplabs) reported

    @Gozy_leonardo @Gozy_leonardo Yeah this is exactly what we kept running into. The model does its job fine and then something totally unrelated kills the run. Cloudflare, LinkedIn throttling, session just drops for no reason. We ended up pushing human approval to mobile so the AI proposes what it wants to do, founder taps approve, and it executes through a real browser session on their actual account. You just can't prompt your way past rate limits, that's an infra problem. What's been killing your flows more, the fingerprinting stuff or pure rate limiting?

  • niknak
    niknak (@niknak) reported

    @twolays @Cloudflare Very bad

  • aguspiza
    aguspiza - e/acc (@aguspiza) reported

    @JaimeObregon Cloudflare: npm install -g wrangler wrangler login wrangler deploy

  • msanvido
    Marco Sanvido (@msanvido) reported

    Was the recent Cloudflare RIF in part trying to fix SBC? @bgurley ? AI is an easy scapegoat :)

  • jonas
    Jonas Templestein (@jonas) reported

    I just realised you can use capnweb to build a lightning fast poor-man's version of cloudflare tunnels 🤯 You just need to write a tiny durable object class that hosts a capnweb session, and then write a tiny client side utility that connects to it We use it to e2e test deployed workers. Our vitest test runner tunnels into the deployed worker and can then receive normal fetch(Request) -> Promise<Response> requests from the worker

  • Tebbers343
    Tebbers (@Tebbers343) reported

    @chribjel Cloudflare really need to limit their free tier and raise their prices, and I speak as a customer and investor.

  • Liu_Mickey_Ai
    刘米其丶 (@Liu_Mickey_Ai) reported

    Due to the Cloudflare outage, all unode services have been affected. All users just need to be patient and wait

  • tobias_pfuetze
    Tobias Pfütze (@tobias_pfuetze) reported

    @DukeOphir @CoinbaseDev Congrats to you and the team, huge step forward! My read: cloudflare:402 solves the bundling via a network/MoR model. For generic API merchants, I still think there’s room for a merchant-operated prepaid solution: Credit Card/Invoice/ACH → balance → signed token/voucher → atomic credit deduction. Would be interesting to clarify whether x402 wants both: network-mediated batch settlement and merchant-operated fiat bundles. If network mediated only and moving from the current crawl content use case to “standard API” - how would it work? Would merchants expose cloudflare:402 directly, or would Cloudflare need an API-billing layer?

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

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

Check Current Status