Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (36%)
• Cloud Services (31%)
• Hosting (17%)
• Web Tools (11%)
• E-mail (6%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Manchester	Domains	1 day ago
Angers	Cloud Services	12 days ago
London	Domains	14 days ago
Noida	Hosting	27 days ago
Jewar	E-mail	28 days ago
Braga	Web Tools	28 days ago

Full Outage Map

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:

• 
  🔱Lady Livz🔱 (@thelegendoflivz) reported 6 minutes ago

  I just know my dad will be pissed tomorrow if it actually is a programming error. If he wasn't in a different division he would probably drive over and fix their ****. I keep telling him he should just apply to Cloudflare or something because this kind of **** drives him bananas

• 
  kiosa (@thegreatest_sv) reported 9 minutes ago

  THE BIGGEST SCAM IN TECH MIGHT BE HOW MUCH PEOPLE STILL PAY TO HOST SIMPLE WEBSITES. >I just launched one for $0. > have 9 project ideas > each needs a domain (~$15) + hosting (~$10/mo) + SSL > do the math > talk yourself out of 7 of them > later find out domains can be free > register one in 2 minutes, no card > Cloudflare for DNS + SSL, free > Cloudflare Pages for hosting, free > live custom-domain site in 20 minutes > cost: $0 > mfw the only thing stopping me was a bill I never had to pay >full build below

• 
  Jasper Disney (@jasper_disney) reported 12 minutes ago

  As an unsuccessful app builder, I only need to pay 5 dollars to Cloudflare each month. Life is not that bad.

• 
  Kolar😎 (@Kolar_Dev) reported 15 minutes ago

  As a product builder, avoid putting your entire infrastructure under a single provider. If your database is running on an EC2 instance, keep backups somewhere independent, such as Cloudflare R2. The goal isn't just redundancy, it's leverage. No single provider should be able to take your product offline, lock you out, or put your business at risk with a single outage or account issue.

• 
  Wallstreet Dragon (@longwashere) reported 16 minutes ago

  DD: Long term holdings. $NET cloudflare and why it's important in the age of agents ELI5: The world is moving towards agent. Big industries need better cloud bot protection, developers need LLM computing on the edge. Cloudflare provides the most afforadable option for both, even heavy aws users are using cloudflare for these purposes. What is Cloudflare? For the technically challenged or pre-med professionals, Cloudflare is a web infrastructure and security company that acts as a protective, performance-enhancing shield between a website and its visitors by providing services like content delivery networks (CDNs), DDoS mitigation, and secure domain routing. TL;DR: For the simple folks, it's that **** that pops up with the CAPTCHA to make sure you're not a bot. For developers, it's that **** that makes your sites fast and secure from bots. What is Cloudflare's growing revenue? Application Security and Content Delivery Network (CDN). What is a Content Delivery Network? A CDN is basically a network of servers used to store files closer to its users for faster retrieval. Imagine an app creates a backend database storing all its images on AWS based in US-East. A CDN will then copy the most commonly used images in that S3 database and duplicate them across multiple regions (Asia, Europe, US-East). When an app makes a service request, it will make the request to Cloudflare first. Cloudflare then uses its internal logic to determine if the data needed is in a nearby Cloudflare edge server (on the edge) or if it needs to get it from the main database in US-East. This is called storage on the edge. This CDN mechanism is a relic of Web 2.0, but it will become significantly more important in the age of AI. Now, instead of storing images, large AI providers will be storing entire LLM contexts on the edge. So instead of training specialized ML models to do a specific task, app companies can use a general-usage LLM with a stored context for that specific task, and it will be fast, too. This mechanism is called Prefix Caching or Prompt Caching. By doing this, it makes the LLM responses almost instantaneous. So all your consumer apps that use LLMs—like CALai, Duolingo, Grok, etc.—are most likely already using this process. Beyond simply storing data on the edge, the industry is shifting toward deploying entire servers and specialized AI models locally. A major component of this architecture relies on LLM routing. Instead of hosting massive, resource-heavy models on every single edge device or regional server, companies are deploying highly optimized, lightweight router models at the edge. These local routers analyze incoming user prompts to determine the most efficient way to handle them. If a task is simple, the edge model processes it instantly to minimize latency and eliminate cloud compute costs. If the task requires deep reasoning or a massive knowledge base, the router intelligently forwards the request to a larger cloud-hosted model. Additionally, these edge routers leverage tool calling, which allows them to execute local APIs, query regional databases, or trigger specific code workflows without needing to round-trip back to a centralized data center. Moving from simple edge storage to localized edge intelligent compute represents a massive paradigm shift. It allows enterprises to scale AI applications efficiently, safeguard data privacy, and drastically slash infrastructure costs. Cloudflare Security in the Age of Agents This one is simple. You know that Cloudflare CAPTCHA that pops up when you're entering a website or checking out with a credit card? Websites PAY for that CAPTCHA. And they pay a lot. These features block spam, bots, and DDoS attacks. When you move your mouse to click the CAPTCHA, Cloudflare uses proprietary logic that determines you're human by calculating how fast your mouse moved, the angle you moved it, how long you waited, and any other actions you took. Sometime in the 2010s, every website figured out that paying for this small puzzle CAPTCHA was more cost-effective than getting DDoS'd by bots, so almost every single site adopted it. The CAPTCHA is only one of Cloudflare's products in its security suite to block bots from websites, but the overarching theme is the same for all its features: blocking bots. Well, it's 2026 now, and web traffic across the board has increased, mostly driven by AI and AI agents. Automated web traffic has increased by 600% in 2026 alone. Guess who is positioned perfectly for this? Cloudflare. Not only is Cloudflare blocking bot traffic, but it's also getting paid by them. Cloudflare is releasing a new product (Pay Per Crawl) that allows website owners and Cloudflare to get paid for LLMs crawling their content. Cloudflare is simply winning by creating the gates for web traffic and now charging a toll fee for bots to use them. Cloudflare is direct play on internet traffic, which is a correlating play on ai agents and LLM adoption and usage. If you think people will continue to use ai agents and LLM, then cloudflare is your guy. Cloudflare valuation has dropped recently because of the layoffs due to ai, even though revenue has sped up. This drop was more of emotional sell off than a fundamental one. It's valuation has already bounced back. (Cloudflare is trading at 235 as of this post, I bought in earlier in the 190s for a swing trade after the bogus layoff dips, wish i bought in more)

• 
  Richard Sever (@cshperspectives) reported 16 minutes ago

  @manuelrivascruz working on solutions to this. the problem as I'm sure you can imagine is like so many sites we are being hammered by LLM bots in addition to all the DDOS attacks, so (again like many others) use services like Cloudflare to ensure human readers maintain access

• 
  Shantanu Landore (@ShantanuVL) reported 16 minutes ago

  @itsasmolsush Oof well my non tech tech company has everything set up over cloudflare so we need to log in with MFA once a day... and the prompt to login comes at the worst point of the day everyday so

• 
  dukeo (@dukeo) reported 19 minutes ago

  @EddCoates Had the same issue on one of our sites receiving millions of hits from scrapers while getting just a few thousands legit visitors per day. The only way is to be extremely aggressive in your Cloudflare setup.

• 
  Otto Lorner (@OttoLorner) reported 20 minutes ago

  Best OpenClaw use case is making it an admin in AWS, Google Cloud, Cloudflare, wherever and never having to use their horrendous UIs again. Cloud consultant on tap.

• 
  seanvfacer (@seanvfacer) reported 20 minutes ago

  Bots just beat humans on the internet. For the first time in history. Not coming. Already happened. Cloudflare — the company running 1 in 5 websites on earth — watched the moment it tipped. The old internet was built for people. The new one's built for agents that don't browse, don't linger, don't even see your sign. So if you're building anything in 2026 — your customer might not be human anymore.

• 
  primitive.host (@PrimitiveHost) reported 21 minutes ago

  Anyone else using @Cloudflare "Email Address Obfuscation" feature having crawl issues on @ahrefs crawler? It detected /cdn-cgi/l/email-protection on ALL my pages and ate up my entire crawl limit for the month 😶

• 
  Brandon Bedford (@wealthpotion) reported 23 minutes ago

  "Claude is down" is the new "Cloudflare is down" except way worse.

• 
  dmsimon (@dmsimon) reported 25 minutes ago

  @EddCoates I had the same problem and moved to @Cloudflare and am using pages and workers. Pages is free on a free account for a ridiculous amount of volume. Keep you host running the dB and move the front to CF. I also think it is much better than gh pages.

• 
  max guy 😐 (@GolerGkA) reported 30 minutes ago

  @artillain @ThePrimeagen Ok I’m stupid bear with me. Usually with cloudflare on front of static public site, users don’t hit my web service most of time anyway, they hit cloudflare cache. Does it still work? I assume that information that anybody would want to scrape would be on static public endpoints.

• 
  Kamil Fabian (@KamilFabian) reported 31 minutes ago

  @EddCoates cloudflare free tier. Solved my 1mil req per minute problem. Just make sure to set up properly.

• 
  ƒrαeყ (@fraey0) reported 33 minutes ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?

• 
  Viktor Lazarov (@viktor_techness) reported 34 minutes ago

  @EddCoates Doesn't Cloudflare anti-bot help? They have a setting specifically for scrapers + robots.txt attachment for a legal notice.

• 
  HAB1B0 German Raffleking 🇩🇪🇹🇷👑{🦅} (@Habiboooo4) reported 34 minutes ago

  @Signulous Your cloudflare is down

• 
  zeb (@zebassembly) reported 34 minutes ago

  @astuyve @boristane Not to get too into the weeds but the concern is where the trace context gets inherited and where we check the users tracing configuration. Before a request ever goes to the Workers runtime there's our FL2 (essentially the Cloudflare webserver) that actually accepts the http connection for various reasons we want that part that isn't entirely related to Workers to be aware of tracing so we can do cool things in the future. This entails creating a way for FL2 to fetch the user's tracing config (sampling, if they want to enable propogation, etc), passing that context through FL2, passing it to the Workers runtime, and then when the Worker does a fetch we need to pass it back through to FL2 so we can potentially attach the context header. None of this is strictly about just parsing that trace context header, more about threading configuration and ceoss-service communication.

• 
  AI News 24 (@ainews_24_7) reported 37 minutes ago

  Cloudflare $NET rolled out the Cloudflare One stack to give AI agents autonomous control over Zero Trust environments. The new skill library handles planning and deployment without requiring manual migration support.

• 
  Locally (@LocallyPT) reported 41 minutes ago

  @EddCoates Cloudflare don't help?

• 
  Iqra (@AiWithIqra) reported 44 minutes ago

  6. Default DNS Resolution Lag What it does: When your TV tries to load the image thumbnails for an app like Netflix, it uses your Internet Service Provider's default DNS server to find out where those images live on the internet. Think of DNS as the internet's phone book. Why it kills performance: ISP phone books are notoriously slow and incredibly outdated. Often, your TV is not actually lagging at all. The processor is fine, but the TV is frozen waiting for your internet provider to tell it where to download the movie poster graphics. *********** it: Settings → Network → Network Status → IP Settings → DNS Setting → Enter Manually. Change the numbers to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). You will literally watch your streaming apps load twice as fast.

• 
  Shantanu Dhanuka (@trudydehacker) reported 44 minutes ago

  @CloudflareHelp Hi, My domain DNS on cloudflare and hosted on CF Pages is returning Warning - Suspected Phishing - This website has been reported for potential phishing. This is happening only with the homepage, inner pages are working fine. We raised multiple ticket Pls help

• 
  Karl Emil Nikka (@KarlEmilNikka) reported 47 minutes ago

  @Cloudflare Nice! Do you have any ETA for sub-domain support?

• 
  Patrick St. Jean (@stjeanp) reported 48 minutes ago

  @EddCoates I dealt with some of the same stuff, ended up putting them behind Cloudflare proxies, which helped somewhat. The biggest fix was blocking specific ASNs. Specifically AS132203.

• 
  Inu Games (@games_inu) reported 49 minutes ago

  @EddCoates @mishuba All those people saying "use Cloudflare" cannot just check the ip and see that it is Cloudflare, unbelievable! Btw, what I do now is to block cloud providers by AS number, seems to help a little.

• 
  Ciccio Diddo 🐧🇪🇺🚽 (@CiccioDiddo) reported 55 minutes ago

  @EddCoates another interesting cloudflare function is AI labirynt ... it create a ton of fake content filled with nofollow links generated by some **** IA... so the scraper spends a ton of resources to traverse all links then, if not enough start to ban by AS number instead of single IP

• 
  brale (@brale_xyz) reported 56 minutes ago

  This is not just a blockchain story either. @NIST finalized three post-quantum standards in 2024. @Cloudflare says more than two-thirds of TLS traffic through its network now uses post-quantum key exchange. The migration has already started.

• 
  brale (@brale_xyz) reported 58 minutes ago

  his is not just a blockchain story either. @NIST finalized three post-quantum standards in 2024. @Cloudflare says more than two-thirds of TLS traffic through its network now uses post-quantum key exchange. The migration has already started.

• 
  CAPED CRUSADER🦇 (@stilleclectic) reported 59 minutes ago

  @matthansbello Sigh, everything was originally done on namecheap but I’ve now just moved the dns to cloudflare. Waiting to see if that fixes the issue