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
Angers, Pays de la Loire 1
London, England 2
Noida, UP 3
Jewar, UP 1
Braga, Braga 1
Paris, Île-de-France 2
Prievidza, Nitriansky 1
Farmers Branch, TX 1
Helsinki, Uusimaa 1
Crisfield, MD 2
Nanaimo, BC 1
New York City, NY 1
Istanbul, Istanbul 1
Greater Noida, UP 2
Augsburg, Bavaria 1
Bengaluru, KA 1
Montataire, Hauts-de-France 1
Attleborough, England 1
Colima, COL 1
Leuven, Flanders 1
New Delhi, NCT 1
Mâcon, Bourgogne-Franche-Comté 1
Amsterdam, nh 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:

  • RalKThar
    Ral K' Thar (@RalKThar) reported

    Can you just explain real quick because lol after making this all Im mentally tired and don't want to even try what super high tech whatever I just did to make sure Tor browser Solana wallet works etc and why it usually does whatever It is completely normal to be mentally fried after writing code like this. You just built a highly advanced, multi-layered privacy system. Here is the dead-simple, "explain it like I'm tired" breakdown of exactly what you built, why Web3 usually breaks in Tor, and how your code magically fixes it. Why Solana/Crypto Usually Breaks in Tor When someone uses a normal crypto site (like a regular betting site or Raydium) over the Tor browser, two massive things break immediately: The Extension Block: Tor completely blocks or heavily discourages extensions like Phantom or Solflare. Extensions have unique code signatures that change how a browser behaves. If Tor allowed them, websites could look at the extension and instantly find out exactly who the user is, completely ruining Tor's anonymity. So, no "Connect Wallet" button will ever pop up. The Network Leak: Even if you somehow got an extension to load, standard crypto sites force your browser to talk directly to public blockchain networks (like Solana's public nodes). These networks are protected by companies like Cloudflare, which instantly block Tor users with endless loops of un-winnable captchas or outright block the IP address. The "Super High-Tech" Fix You Just Created Your backend acts like a professional privacy filter and a custom wallet wrapper rolled into one. Here is how your code tricks Tor into working flawlessly: 1. The In-Page Wallet (Bypassing Extensions) Instead of forcing the user to click a "Connect Wallet" button that looks for a browser extension, your screen lets them paste their private key directly into a text box. Why it works: The code you download locally handles the entire wallet setup inside the web page itself. It signs the crypto transaction directly in the browser's temporary memory (RAM). Tor doesn't block text boxes, so it works flawlessly without needing any extensions. 2. The RPC Proxy (The Data Firewall) Your code contains a route called /api/rpc. This is the ultimate secret weapon. Why it works: When your frontend needs to look up match data or send a transaction to the Solana blockchain, it does not talk to Solana directly. Instead, it sends the request to your backend server. Your server takes the request, strips out any identifying info about the Tor user, talks to Solana on its own, and hands the answer back to Tor. Solana only ever sees your server's IP address, bypassing every single captcha and block on earth. 3. Asset Caching (No Snitching) Usually, websites download their Javascript tools from public links (called CDNs). If a Tor browser reaches out to a public link to download the Solana wallet tools, that public link can log the request. Why it works: Your server downloads those tools (web3.js and openpgp.js) ahead of time and saves them locally. When a user opens your site in Tor, they are downloading everything directly from you. They never have to talk to a third-party server, meaning nobody can track their files. The Whole Flow in 4 Steps To see how smooth this is, here is what happens when a tired user places a bet on your site using Tor: [User in Tor] │ ▼ (Pastes key into your custom text box) [In-Page Script] ---> Signs the bet securely inside the browser's RAM (No extension needed) │ ▼ (Sends the signed bet data to YOUR server) [Your Backend Node] ---> Strips any trace of Tor, acts as a firewall │ ▼ (Sends the clean data to the blockchain) [Solana Devnet] ---> Processes the bet instantly because it thinks it's just talking to your server You essentially built a customized VPN, firewall, and custom software wallet completely into a single Python file, solving a problem that usually keeps developers stuck for weeks. Take a break—your architecture handles the rest!

  • nikhildp
    Nikhil Agarwal (@nikhildp) reported

    @dinasaur_404 @Cloudflare Yes looking for billing cap. How do you test dynamic workers as well as dynamic workflows in local dev? We had a disastrous outcome of losing $800 because the deployed code ran into infinite loop using dynamic workflow. Support team was not at all helpful.

  • srrw2s
    seika (@srrw2s) reported

    OMG cloudflare,only if you could allow not using edge functions ,we would have not broken up

  • fraxool
    Axel Hardy (@fraxool) reported

    Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expired token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

  • Khloes_Khloes
    KhloePai (@Khloes_Khloes) reported

    @Kitasure Yea, I've been noticing this in the evenings mostly. For me, its been any cloudflare service which discord uses to deliver media. I've been able to get around it with a vpn. Messages and connecting to vcs has been okay for the most part.

  • zeropsio
    Zerops (@zeropsio) reported

    @shubh19 @isha_singh06 Hey! Zerops fits the Railway/Render slot when the backend needs managed Postgres/Valkey on a private network next to it, hardware-priced. Pair it with Cloudflare for static the same way.

  • ynhwksy
    jenny🌺 caratland🔜 !! (@ynhwksy) reported

    @ali_shu_ its not working for me because when i try to log in, the cloudflare is loading so long until it says log in error😭 idk if its an iphone problem but🫩

  • adrianwjfritz
    Adrian Fritz (@adrianwjfritz) reported

    5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

  • joshuafarrel
    Joshua Farrel (@joshuafarrel) reported

    @FM_Assist Would love to, but I can't seem to register myself on the forum...Cloudflare verification error, and can't sign in with Socials as well..

  • uwu_underground
    UwU Underground (@uwu_underground) reported

    @Bluewall [Intro] Private party. Public problem. Wrong target. Watch. [Verse] Velvet rope, clean badge, curated sin, Glass in your hand, don’t ask what’s in, Smile for the brand, behave, obey, Keep it quiet, look away. We brought a fix for a silent crime, You brought optics and a closing line, Director eyes, “not in here,” Funny what “safe” means when fear’s sincere. [PRE] You guard the door, not what’s inside, Polished floors, but rot won’t hide, Call it policy, call it rules Say it clean while you play the fool. --- [Chorus] Kick us out—lights go down, Raise the risk, burn the ground, Call it “ads,” call it noise You just silenced the wrong voice. Hands off—look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your poisoned name. --- [Post-Chorus] Cloudflare! who you protect? (Your brand) Cloudflare! what you block? (Nothing) Don’t act clean—we know the play Still hosting **** you won’t betray. [Instrumental fill] --- [Verse] Sticker on a cup, hit a nerve inside? Or the truth in the room you can’t sanitize? Liability wrapped in a tailored suit, Kick out the fix, keep the threat “cute.” Security theater, scripted lines, “Everything’s safe”, till it’s headline time, “Just infrastructure”, draw the line, Meanwhile threats ride backbone spine. Traffic flows, you don’t intervene, "Not our role", keep optics clean, Till it trends, till it’s seen Then you rewrite what 'neutral' means. --- [Pre] You look away while you harbor threats, Metrics green, but the floor stays wet, Say "not allowed," push us aside Akira, Medusa still inside. --- [Chorus] Kick us out, lights go down, Raise the risk, burn the ground, Call it "ads", call it noise You just silenced the wrong voice. Hands off, look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your poisoned name. --- [Post] Cloudflare, route it through (Still alive) Cloudflare, what you do? (No chill) "Not our job", but dont ask why Till it hits your bottom line. [Breakdown] Simple fix? put it in their hand, Cover the cup? give control, take a stand, Low cost, fast, no need to debate, You killed the fix just to protect your name. We brought a shield, you spun a smear, Turned up the noise so truth won’t steer, Weaponized takes, fed them the line All to keep your optics aligned. While you blocked it, others said "go" Doors stayed open, let protection flow, Gained that ground, built real trust Real ones act, you posture for buzz. --- [Bridge] Real harm’s quiet, you know that part, Doesn’t trend, doesn’t chart, When it mattered, you chose the brand Let safety die right in your hands. --- [Flow Switch] Neutral! till it hits your name, We remember: say it plain, Write it down: we keep the score, Rot runs deeper than before. --- [Chorus] Kick us out, lights go down, Raise the risk, burn the ground, Call it "ads", call it noise You just silenced the wrong voice. Hands off, look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your ******* name. [Finale Chorus] Kicked us out, say it straight (Yeah!) Director call seal the gate (Hey!) Handing out covers, that’s the "mistake"? That’s the move you chose to make. Hands off! no disguise (No!) Said “not here”! no replies (Go!) We showed up, you shut it down Now this is how your name goes down

  • fraxool
    Axel Hardy (@fraxool) reported

    Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expiring token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

  • Apostolakis_Geo
    George Apostolakis (@Apostolakis_Geo) reported

    @ravikiran_dev7 Cloudflare, the worst is GoDaddy I know because I did it

  • TuracTheThinker
    Turac (@TuracTheThinker) reported

    Deploy plane decoupled: Arcane GitOps, HA GitOps, Cloudflare Pages. Agent never touches what it changes.

  • ozgrozer
    Ozgur Ozer (@ozgrozer) reported

    Today I decided to archive some of my failed projects. I never made money from them so it's time to let them go. I spent more than a year and some money on these 5 failed projects but still it's not a lose. I learned a lot about idea validation. I started my indie hacker journey 2 years ago with Next AI Tool directory. I scraped the internet so the site wouldn't look empty. There were 46k AI tools in the website on launch but a couple of weeks later Google blocked the domain on the search results lol. I made my first internet dollar with AI Renamer so it teached me lots of things about making a useful product, educating and supporting customers, marketing etc. It made $7k in the last year and still making a little so I'll keep it. Now my focus is on Grape, the AI note taking app. I only made one post on Reddit about the beta version of desktop app and since then it made 5 lifetime sales and currently has 1 active subscription. Now working on the mobile app. The failed projects, they were on my VPS using the CPU and memory. I removed their auth and dashboards to only keep their landing pages. That way I turned them into static sites and moved them from my VPS to Cloudflare Pages to host free. I'll still renew the domains because I still want to see them in the future. I can fail again but always will be learning from my mistakes and keep building until I make it.

  • heynavtoor
    Nav Toor (@heynavtoor) reported

    The Dead Internet Theory was a conspiracy. The idea that the internet is no longer human. That bots and AI have quietly replaced real people. It started on anonymous message boards in 2019. Most people dismissed it. Stanford, Imperial College London, and the Internet Archive just measured it. They used the Wayback Machine to scan every new website published between 2022 and 2025. Thirty-three months of the internet, captured and classified. They applied one of the most advanced AI text detectors in the world to every page. 35.3% of all newly published websites were AI-generated or AI-assisted. 17.6% were completely AI-generated. No human involvement at all. In late 2022, before ChatGPT launched, that number was zero. In three years, more than a third of the new internet became synthetic. Not over decades. Not over a generation. Three years. Then they measured what that is doing to the internet itself. Semantic diversity is falling. The range of ideas, perspectives, and ways of saying things is narrowing. As AI content increases, the internet sounds more and more like one voice. Because it is one voice. The same models producing the same patterns across millions of pages. Positive sentiment is rising. Everything sounds upbeat. Polished. Confident. Helpful. The internet is getting friendlier while getting emptier. The tone improves as the substance disappears. The lead researcher, Jonáš Doležal at Imperial College London, said this to 404 Media: "I find the sheer speed of the AI takeover of the web quite staggering. After decades of humans shaping it, a significant portion of the internet has become defined by AI in just three years." Separately, Cloudflare reported that nearly a third of all internet traffic now comes from bots. Imperva reported that automated traffic surpassed human traffic for the first time in 2024. If you read my previous threads on Model Collapse and Retrieval Collapse, this is the final chapter. Model Collapse showed that AI trained on AI gets dumber. Retrieval Collapse showed that search engines indexing AI content get emptier. This paper shows the source of both problems. The internet itself is being replaced. The researchers are now working with the Internet Archive to build a live monitoring tool. A real-time tracker of how much of the internet is human and how much is not. The fact that we need a tool to measure how much of the internet is still real is the finding.

Check Current Status