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
New York City, NY 2
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
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:

  • EMercerCap
    evan mercer (@EMercerCap) reported

    I’ll say this once: These 8 stocks could create a $3 million opportunity before 2027. $TSLA (Tesla) — Don’t buy $AAPL (Apple) — Don’t buy $CRM (Salesforce) — Buy at $158–$166 $CRWD (CrowdStrike) — Buy at $190–$200 $NOW (ServiceNow) — Buy at $100–$105 $NET (Cloudflare) — Buy at $265–$275 $FTNT (Fortinet) — Buy at $156–$163 $ZS (Zscaler) — Buy at $140–$148 Strong companies can still be bad buys at the wrong valuation. Which pullback would you buy?

  • rknkhanna
    Rahul K (@rknkhanna) reported

    you mean 3 people are trying to cancel cloudflare?

  • Sophia_Crypto
    Sophia dev 🤓 (@Sophia_Crypto) reported

    @Lovable We have a bug. We use Cloudflare turnstile for our app sign in but on your windows desktop app it won’t pass / validate despite all your URLs whitelisted in cloudflare.

  • Marshal_Seda
    Seda Marshal (@Marshal_Seda) reported

    @DanielNjorogee @truehostcloud I faced this challenge with about 15 domains I wanted to change their nameservers to point to cloudflare. @truehostcloud why did I have to call support to help me do this?

  • CounterStratGG
    CounterStrat.com (@CounterStratGG) reported

    Heads up: some users on the U.S. West Coast may be having trouble reaching CounterStrat right now. Our servers are operational, but an upstream networking issue between Cloudflare and our server provider appears to be causing connection problems. We’re keeping an eye on it and will post an update once things are back to normal.

  • lianshangpixiu
    Pixiu.eth🐬TermMax (@lianshangpixiu) reported

    @the_jujukey @RobinhoodApp @Noxa_Fi cloudflare issue is real, gotta wait it out

  • Alpernoth
    Alpernoth (@Alpernoth) reported

    ok seriously, what's going on with the cloudflare page popping up on X lately and my account continually getting locked? wtf is going on with either this website or Cloudflare? I'm not DOING anything other than enjoying artwork for the most part on this site!

  • RNR_0
    Romano (@RNR_0) reported

    @0x7im @Hetzner_Online @OVHcloud What I did, Install nixd and Terraform LSP. Ensure it's wired or Claude code can use it (idk if build in) Try to setup a repo and make it manage by using Terraform/Opentofu and NixOS with deploy-rs Also opentofu to manage your cloudflare settings (if any) When it's all declarative it's easier for an LLM to reason about it. My GCP bill used to be $6k, slashed to $3k after i mentioned a testnet of a testnet is retarded. Cut it down from $550 bill on GCP with GPT 5.5 and the few days of Fable (before initial ban)

  • Mavericks100xs
    Maverick (@Mavericks100xs) reported

    It’s over for cash-cat:native Chinese blockchain sleuths have uncovered the following: ‘NOXA Dev ***** History" After the incident erupted (especially post-downtime + new launch halt), the Chinese community quickly unearthed Amun Phantom's past record, with the core accusation being **"veteran rug pull playbook."** Main sources are posts from active Chinese KOLs/communities (e.g., @DiYi_Community, etc.), claiming "people who know him are well aware." - Key exposé points: Not his first big project: Two years ago (around 2024), he built a product even hotter than NOXA this time, then rugged at peak hype, allegedly draining that chain's liquidity pool dry (claims of "chain pool leader 3w ETH," possibly 30,000 ETH level, with community debate on exact figures). - Patterned operations: Every time a new chain heats up, he spins up a similar launch platform/product, quickly harvests traffic and fees, then "exits" or rugs. In 2025, multiple "exited products" of his popped up on new chains. - This time a "soft rug" not hard rug: Originally geared to straight-up bolt, but with too many bagholders this round—scale too massive (fees too high, user base huge)—direct rug would've blown up, so he opted for "soft rug" strategy: Website "issues" (Cloudflare IP block), halt new launches, shift to decentralized frontend, hand fees fully to creators, then slowly fade out. - Personality/Style Critique: Community calls it "deep-seated foreign scumbag traits, no vision for real growth," akin to some early infamous but controversial project vibes. These exposés are currently mostly community word-of-mouth + historical pattern inference, with no full public on-chain evidence chain or article yet (some say a detailed timeline post is coming). But since Amun Phantom is anonymous/semi-anonymous, historical project links rely mainly on community memory and behavioral pattern matching.

  • RamseyPulse
    julian ramsey (@RamseyPulse) reported

    I’ve cut my watchlist down to 7 names. Nothing else comes close. $ANET (Arista Networks) — Buy at $174–$180 $CDNS (Cadence Design) — Buy at $358–$370 $NET (Cloudflare) — Buy at $250–$258 $AKAM (Akamai) — Buy at $117–$121 $INTC (Intel) — Buy at $102–$106 $SNPS (Synopsys) — Buy at $420–$432 $QCOM (Qualcomm) — Buy at $176–$182 If I had to keep only one, I’d choose $ANET. What’s your pick?

  • naps62
    naps62.eth (@naps62) reported

    @oleg_fem Seems I had an issue with the "http -> redirect, and safari was smart enough to still redirect. a toggle missing on cloudflare should be fixed now!

  • staysaasy
    staysaasy (@staysaasy) reported

    I'd recently been meaning to build something end-to-end to feel where AI acceleration helps. So I built something that I personally wanted for a while, which is a chrome extension to block existing sites until you solve a math, brainteaser, or quick coding problem. The overall thinking is that site blockers are too annoying and get uninstalled. More importantly, I've been getting increasingly freaked out that AI + social media means that we're getting pincered between attention-crushing feeds on one side and mental laziness from AI on the other. So if the brakes on the dopamine actually force my brain to work, I'm kinda solving both problems. Since we also like to talk about AI development, I'll add a few things I learned from this exercise: Coding a very compact site and JS package is *extremely* fast, but getting it to something workable takes much, much longer. Claude Code basically one-shotted an initial working version of the project. It's cliche at this point but I thought that I was 90% done in the first 30 minutes, and I was probably actually only 5% finished with something I was happy with. But I really see why (somewhat foolish, often non-technical) people are constantly crowing about how magical it is that they one-shotted some app, because even I was pretty confident that I was nearly done after that first half hour. Overall, the code still got written probably 10x faster than if I'd coded it all by hand. And keep in mind that this is an extremely compact project. But even with that said, the coding agents did a pretty poor job of structuring the code and I had to fix a bunch of it by hand and/or with very targeted prompts. GPT via Cursor was better than Claude at this, fwiw. AI is extremely good at coming up with tiny incremental features ("it'd be great to have a setting for timeouts, I'll add that") and makes totally dumb macro product decisions, you can really feel how alien and inhuman the intelligence is at times. Especially for a project like this that has to do with human psychology. It also picks weird color schemes; I ended up picking all of this outrun-inspired color palette myself. AI is incredibly valuable at compensating for your weaknesses. I put the landing page for this extension behind Cloudflare and had some DNS/hosting issues, an area where I'm not an expert. Claude solved them all in about 10 minutes. 3 years ago, I would have been googling like an idiot for hours. AI is not much help at all for much of the work related to making a project presentable. Site copy, making a teaser video, taking nice screenshots... if you use AI your copy immediately looks like horrific AI slop, and actually generating even moderately nice assets still requires care. Dealing with the Chrome store's annoyances still requires human willpower. Overall, I really see why we're *not* seeing an explosion of new products despite the impressive power of AI to write code. There's just so much else to do to get even a tiny project presentable that I'm not surprised to see that despite the very real productivity boost, so few people actually follow through that any increase is basically a rounding error. Thanks for reading all of this. I'll put a link to the project in a comment as well.

  • __chibugo
    Chibugo | AI automation (@__chibugo) reported

    there's a trend on instagram right now: everyone's building their own version of Tony Stark's Jarvis; a voice agent that runs like an actual OS. what nobody shows is everything people overlook when building one. so here's that part, since I built it myself. 🎯 the plan on paper vs. the plan that shipped the amount of planning you need to do is insaneee. first version had each agent loading one tool, fetching, verifying, then unloading before the next; all built around not blowing past a token budget. that's the part people underestimate: you don't know your constraints until it's running. once it was live, token budget stopped mattering. speed and cost-per-call did. so the whole approach changed: instead of mcp's, every agent just calls its tool's API directly, does the work in plain code, and only asks the AI to write the sentence at the end. 🎯 scope one AI that "does everything" sounds impressive but could be a nightmare to debug. so i split it into 5 sub-agents, each only knowing its own lane. a router decides which lane(s) a question touches. these sub-agents then report to the main agent orchestrator. similar to a team lead and team members 🎯 prompt chaining integrated ElevenLabs for voice, and a single voice reply isn't one AI call; it's a handoff, several times over: hear the words → figure out what's being asked → pull the data → write the sentence → speak it. every handoff adds seconds and cost, which can lead to latency. one reply once took 31 seconds. pulled the logs instead of guessing: a wasted double-check on an expired token, a slow handoff to an outside service, plus the normal chain. fix is running sub-agents in parallel and timing each call. 🎯 tokens and prompt caching each agent's instructions get cached, so it's not re-reading the same manual on every call. what never gets cached is live data; for instance, caching a bank balance is just caching a wrong number the moment it changes. that same cost-awareness came back around differently later: the AI account ran out of credit for a few hours, and every request failed with the same error. 🎯 local vs. web everything gets tested on a local copy first; headless browser opening the dashboard, checking for errors, a test message round-tripping through voice before go-live. if you're handing this to someone else, though, you commit, push to GitHub, and host it. for mine, i used Cloud Run for the brain, Cloudflare Pages for the screen. 🎯 vault write-back most builds only go one direction: ask, answer, forget. this one writes back because every full briefing gets saved as a dated file into a notes vault so the agents can keep training themselves with the data. if you ask a follow-up an hour later and it still knows, because that memory is shared across every way you talk to it. used Obsidian, synced through Drive. 🎯 security once, a message could've gone somewhere it shouldn't have. that only needs to happen once to be a problem. so now there are three checks before anything goes out: - it can never post to certain places, - it has to prove who it's speaking as before it speaks for someone, - and tests confirm both of those actually work. separate from that, I went through every access key this thing has and asked, "does it really need this much access?" a few did not. 🎯 the checks after every update, it runs a test and asks does a voice message go through? does it understand a normal sentence? does the screen load with no errors? also implemented something we call "error logging" in automation, but i call this "diagnostics" or "agent health status," which checks in every 15 minutes on its own, making sure the data is still updating. if it's not, it sends a warning without anyone needing to notice first.

  • trevhud
    Trevor Hudson (@trevhud) reported

    With cloudflare tenant separation (one D1 per customer for example) you could just start giving read access to your customers which would go a long way for trust and integrations.

  • yashmp2004
    yash.jsx (@yashmp2004) reported

    @Im_IrushiK Cloudflare runs a vast global edge network with security, zero-trust, serverless compute, and AI not just basic CDN.

Check Current Status