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
Los Angeles, CA 1
Paris, Île-de-France 1
Manchester, England 1
Angers, Pays de la Loire 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:

  • WillarShoko
    willard shoko (@WillarShoko) reported

    Cloudflare says humans could become a "rounding error" as bots generate 1,000 times more internet traffic Just a couple of months after Cloudflare revealed that bots have officially surpassed human traffic online, the company has given its view on what things will look like in five years. It's not good news for us fleshy meatsacks: non-human traffic could be up to 1,000 times higher than human traffic. CDN and cybersecurity giant Cloudflare held its Q2 earnings call on Thursday, during which chief financial officer Thomas Seifert gave a concerning prediction about what the web will look like in the future. "If the current trends continue, we think in five years, non-human traffic will be as much as 1,000 times as much as human traffic," he said. "In other words, humans will be a rounding error on the internet, not because human traffic goes down, but that's just how fast we're seeing non-human traffic grow."

  • Arxonic
    Daniel (@Arxonic) reported

    @gregisenberg @Cloudflare 9/ The Filter for Finding Ideas Ask yourself: • What decision is expensive? • What information is messy? • What changes often? • Who already pays for help? • What would an agent need to do the job better?

  • Ibermejocatalan
    Ivan Bermejo (@Ibermejocatalan) reported

    Cloudflare and Coinbase launched the x402 Foundation. Built on HTTP 402, the status code the web reserved for payments and never used. Now AI agents on Cloudflare Workers can pay for API access in USDC on Base. No card rails, no billing dashboard. The agent hits the endpoint, gets a 402 response with a price, signs a stablecoin tx, and the content unlocks. AWS CloudFront already adopted it too. This is plumbing. The kind that makes agent-to-agent commerce default infrastructure, not a demo.

  • NyagahTony
    Nyagah-254 (@NyagahTony) reported

    Stopping the bad guys with Cloudflare: 22,280 malicious requests blocked or challenged in the last month #cloudflare This is from a domain that's pretty much dormant 🤔

  • MPi_IT
    Maik Pietzka (@MPi_IT) reported

    @Cloudflare Shadow AI is an inventory and control problem before it is a model problem. Teams need to know which agents exist, which identities and data they can access, what tools they call, and how actions are audited. Visibility first; policy second; safe automation third.

  • kushbhuwalka
    Kush (@kushbhuwalka) reported

    If I had to summarize the problems of coding agents today, they would be, in order, > reliability & naivety > infrastructure inertia > safety >cost > speed 1) Reliability & Naivety - The agents are not consistent and are prone to degrading, going down weird rabbit holes, and simply performing in random ways. They sometimes make very dumb decisions, especially on long horizon tasks. 2) Infrastructure inertia - Clicking around the computer is actually a terrible way to do things, and thanks to cloudflare & captchas, many products and sites make life very hard for agents to operate. Memory is fallible too. 3) Prompt injection - this is unsolved, although you can mitigate this by running a small model on any incoming inputs. A well-crafted prompt can trick both the AI security layer and then the agent. As AI-pilled as I am, I would not give my agent unfiltered access to my bank account. Things like codemode & permissioning help, but you can't expect to permission everything you give an agent. 4) Cost - frontier models are too expensive. The subsidization is unscalable (I max out two codex plans ~ 20-28k/m). Even for the average user, to have an always on running agent thats actually doing work will cost atleast ~$200 a month ($100 for tokens, $100 for compute). 5) Speed - SOTA models churn out tokens at around 30 tokens/second, which is unimaginably slow. Although I imagine cerebras will solve this (for eg. SWE 1.7 by @DevinAI is somewhere around 1000 tokens/second, and is so fast you don't really see it streaming in).

  • CNC_Kitchen
    Stefan - CNC Kitchen (@CNC_Kitchen) reported

    @MakeProMajkl83 Domains just changes. Maybe this is stil a cloudflare problem.

  • CHItrader
    CHItrader (@CHItrader) reported

    CLOUDFLARE WANTS TO REBUILD INTERNET TRAFFIC RULES FOR STARLINK $NET Cloudflare's CTO says LEO satellites need new congestion-control tech built for constantly changing routes. Elon Musk sent the idea straight to the Starlink team. $SPCX 🔹 LEO networks have unstable paths/RTT that traditional protocols aren't designed for 🔹 $NET could help Starlink improve speed, latency and bandwidth efficiency 🔹 Starlink now has 12M subscribers, while Cloudflare says Starlink traffic jumped 2.3x in 2025 🔹 No deal yet, but Musk forwarding it makes this worth watching $NET is down 2.8% today. Funny how the market sometimes notices everything except the interesting part.

  • knowRowan
    Rowan (@knowRowan) reported

    @thenowhereway Honestly, Cloudflare is the move. Free DNS, no upsells, and renewal at cost price. I switched everything there and never looked back. 💯

  • Telestijl
    TeleLLM (@Telestijl) reported

    @levelsio Private Relay is a likely culprit — iCloud → Private Relay (or Safari's "Hide IP Address") routes DNS/traffic through Apple/Cloudflare relays per network, and macOS applies it more aggressively on a fresh hotspot connection than iOS does on its own cellular link. Toggling it off for that specific network usually fixes the "works on iPhone, not tethered" split.

  • UptimusApp
    Uptimus (@UptimusApp) reported

    Aug 10, 2026 at 12:19 UTC: Cloudflare reports the incident affecting the 1.1.1.1 public resolver in Tel Aviv is resolved. The issue lasted 123 minutes, and DNS services are operational.

  • Arxonic
    Daniel (@Arxonic) reported

    @gregisenberg @Cloudflare 6/ Startup Idea #1: The Niche Data Refinery Pick one messy niche. Clean the data into agent fuel. Wedge: 100 businesses in one city. First customer: The business that needs clean data to exist. First version: Manual data entry + API.

  • nichochar
    Nicholas Charriere (@nichochar) reported

    The actor model is winning: with cellId and the rise of serverless we’re seeing patterns emerge as most popular for modern workloads: workers, durable objects and message passing. The funny (and annoying) thing is that the perfect stack exists but isn’t being used. We’re reinventing in rust and typescript what was built already, and boy was it built well. Elixir is based on the BEAM VM, which implements actors perfectly. No shared state, immutable data, gen servers for long lived stateful processes, supervision trees for reliability Then, Elixir introduces ergonomics on top. The language is inspired by Ruby and tries really hard to make itself a delight to use. Really strong developer ergonomics (pattern matching, overloading, type hints, all-in-one build tool and linter, thoughtful keywords, strong conventions, etc…) It is quite literally overpowered. I used it at Pinterest and we would take services built in python that were maintained by a team of 20 and replace with one elixir service maintained by less than one person. Multiple times. If well designed they simply never go down and scale beautifully. We also used it at Mocha and had a 10x more reliable app than lovable or replit. In fact one of the reasons we kept competing is that we felt their apps were garbage (they have since improved a lot, which is a frustrating mistake I have since learned from). In the age of agents, elixir should absolutely be winning, and indeed the actor model is! It’s a perfect fit: long lived processes with very unreliable third party processes and humans in the loop, all orchestrated to be long lived and reliable with not too much internal state. But as I learned, unfortunately the best tech doesn’t win, capital wins. And most programming languages won because they had massive capital (think companies) pushing them forward. Rust had Mozilla, Go had Google. typescript had Microsoft (JavaScript is a bit different, it won because it’s the runtime of the biggest platform ever made: the web). This is frustrating but it is also reality, so I guess we should be happy to see great implementations (rivet in rust, workers/DO by cloudflare) becoming mature. The actor model is the best programming model for most web workflows.

  • LogWeaver
    Logan Weaver (@LogWeaver) reported

    We think we are the main user of the internet. That’s wrong. Machines now make more than HALF of all web traffic. This report comes from Cloudflare, and even Google and Meta should be nervous about this. Cloudflare runs the plumbing for about one in five websites. So it sees a big slice of all web traffic. The machines are mostly AI bots and agents. They scan the web to train and feed AI models. They read pages far faster than any person can. A person might visit a few websites to buy something. An AI can visit thousands in the same moment. Not long ago bots were about 20 percent of traffic. Now they are more than half of it. Cloudflare expected this to happen around 2027. It arrived a full year early instead. Its finance chief gave investors a blunt warning: Human activity could become a rounding error in five years. Bots could outnumber people by a thousand to one. Picture a web built almost entirely for machines. Now here is the part the market keeps ignoring. The free internet runs on ads shown to people. More and more, an AI reads the page for you. You get the answer and never visit the site. That site gets no visitor and no ad money. Google and Meta are the kings of the ad model. Their fortunes depend on human eyes and human clicks. But those humans are becoming the smaller half. Bots do not watch ads or buy products. These are some of the most valuable companies alive. Their whole engine sits on a shrinking base. Even Cloudflare admits the old model is breaking. It now wants to charge the bots to visit. That risk barely shows up in the headlines. The crowd sees AI as pure good news for big tech. This is a slow shift, not a crash tomorrow. But slow shifts are the ones that reprice giants. The biggest changes are often the quietest ones. The crowd chased the obvious story. The data told a different one. That's the whole game. Surmount runs on clear rules and real data, not hype. If you want a system that follows facts, start here:

  • RealChrisCotts
    Chris was Right About Everything 🇺🇸 (@RealChrisCotts) reported

    @BrianRoemmele Very cautious about anything coming from Cloudflare. Very. They are never on the level.

Check Current Status