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.

• Cloud Services (37%)
• Domains (26%)
• Web Tools (21%)
• Hosting (11%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	8 days ago
Los Angeles	Cloud Services	9 days ago
Paris	Cloud Services	25 days ago
New York City	Hosting	28 days ago
Manchester	Domains	2 months ago
Angers	Cloud Services	2 months 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:

• 
  IamR0b (@O_0olI_1_lIo0_O) reported 3 minutes ago

  @Polymarket JUST IN: Cloudflare executives are broken ****** accidents from sibling parents.

• 
  Enkhmanal 🟠 (@Enkhmanal) reported 5 minutes ago

  $NET - CLOUDFLARE'S 2021 CONVERTIBLE COMES DUE THIS MONTH, AND THE HEDGE AGAINST IT CAPS OUT AT $250.94 Cloudflare runs the network that sits in front of a large slice of the web, absorbing attacks and serving pages from close to whoever asked for them. This morning it proposed $2.175 billion of new convertible notes. On August 15, the $1.29 billion of 0% notes it sold in 2021 mature. A 0% coupon is never free money, and Cloudflare knew it. Alongside those notes it bought capped calls — a hedge that hands back shares to offset the dilution when conversion arrives. That hedge switches on at the $191.34 conversion price and stops at $250.94. The stock closed Friday at $300.78. So the settlement splits three ways: the $1.29 billion of principal in cash, which the company irrevocably elected back in May; stock for the conversion value above it; and a partial refund of that stock from the hedge, but only as far as the cap. Everything above $250.94 is dilution Cloudflare simply wears. That is the bargain inside every capped call — cheaper protection, bought by agreeing in advance on how well your own stock is allowed to do.

• 
  Daniel (@Arxonic) reported 6 minutes ago

  @gregisenberg @Cloudflare 7/ Startup Idea #2: Agent Readiness Audit Sell "agent readiness" to businesses. Show the founder exactly what AI says about their company today. Most will be horrified. Fix their structured data, MCP endpoints, and payment rules.

• 
  Lorenzo (@lorenzolfm) reported 8 minutes ago

  I've been thinking a lot about the recent @BtcpayServer vulnerabilities over the last few days. IMO, they also shed some light on other architectural and design issues in the application. I want to talk a little bit about them in this post. First, if you run BTCPay Server, please: - Upgrade to 2.4.2. - Rotate your LND credentials if you use LND. Treat the old ones as compromised. Also, I want to make it clear that I have deep respect for the project and its maintainers. I know how hard it is to ship safe software. Sometimes lessons are learned the hard way, and it really sucks when that happens. Okay, back to the topic. Here are some things I think could be improved: 1. Different server bindings for user-facing and admin features The goal of running a BTCPay Server instance is to accept Bitcoin payments. This means you have to expose the application to some network. Either a LAN if the merchant has a physical store, or the internet if it's an online store. As the app works today, exposing your PoS also means exposing all of the admin-facing features of the app. A customer can access /apps/appId to make a payment, but they can also access /login, the page that prompts for a username and password to access the admin interface. This means that users have to go out of their way to block public access to the admin interface. This could mean using local firewall rules if it's a LAN-exposed application, or Cloudflare WAF rules if it's exposed to the internet. And you have to configure those rules correctly. There are plenty of ways to shoot yourself in the foot: you could accidentally block legitimate URLs, forget to block something, or introduce another misconfiguration. This could be easily avoided by having separate server bindings for user-facing and admin-facing features. So instead of users having to worry about firewalls, they could simply expose the PoS binding and not the admin one. 2. Make sensitive features opt-in BTCPay Server has an API that can do almost everything the web UI can: create invoices, manage stores, create payouts, access wallets, etc. This is very useful for tech-savvy people to build custom software on top of the application, but it's a niche use case. Most people will just use what BTCPay Server already provides. From what I could tell on my own instance, there's no way to turn the API off at all. I'd argue this, and other sensitive features, should be opt-in rather than enabled by default. 3. Passwords shouldn't work as API credentials BTCPay Server has a really nice feature that lets you grant 46 different permissions to an API key. But you can also authenticate API calls with your username and password, and that method bypasses all of them. You get everything your account can do. My take is that basic authentication should never have been possible in the first place. An account password is a human credential. An API key is a machine credential. They shouldn't be interchangeable. Machine access should always require a credential that you deliberately created for that purpose. 4. Don't display sensitive data in plaintext When you connect BTCPay Server to a Lightning node, you give it a macaroon. It's sort of like a password with specific permissions baked into it. The problem is that the store settings page displays the entire connection string, including the macaroon, in plaintext. So if someone gets access to your admin UI, they don't need to do anything clever. They open one page and can read your Lightning credential straight off the screen. The same applies if you use a hot wallet. BTCPay Server stores the seed in its database, and you can view it through the UI. Credentials should be write-only. You paste them in once, they get masked, and that's it. If the application really needs to show a credential again, make me re-authenticate first and log the event in the database so it's traceable. 5. Audit Logs. In case **** happens, is very useful to be able to know what exactly happened. Which credential hit what API? When? What was the IP of the caller? Was it an inside job? was it a credential leak? was I drunk and pressed the wrong button? --- Please take all of this with a grain of salt. I had no involvement in building this software or in the decisions that made it what it is today, and it's very likely that some of what I pointed out has a good reason behind it that I can't see from the outside. This is just a comment from a user who is very paranoid about the software he runs. If I could be granted one wish, it would be splitting the customer-facing binding from the admin-facing one. That alone would be a huge security improvement, and it seems like a low enough hanging fruit.

• 
  Alexander Zuev (@zlxndr) reported 8 minutes ago

  If I was looking for ways to 10x the DX of @CloudflareDev (which is already great, ofc), formulated in a withlist: 1. Make every error thrown by any binding or the runtime carry a stable, documented .code - not a code embedded in the message like R2's (10024), an actual property 2. Every such error should carry .retryable, typed, on all bindings - you already ship it on DO stubs, extend it and put it in @cloudflare/workers-types 3. Both should survive the boundaries that currently flatten errors: RPC serialization and NonRetryableError in Workflows This will make error workers error handling no longer depend on string parsing for each & every binding I use. Is it too much to ask? Merci beaucoup in advance!

• 
  Mark Z · FiveToClose (@MarkZofMarkZ) reported 10 minutes ago

  @JacobCounsell I take the 5th. lol. It's been many many years since I got my hands "*****" and rolled my own servers and such. call it lazy, call it smart, call it getting sh*t down faster. TBH - no idea how AI set up my cloudflare. But noted!

• 
  Musharof (@MusharofChy) reported 10 minutes ago

  @csaba_kissi Yes, they do. But I never used any. I like their service pretty solid plus very competitive pricing. Now, Cloudflare has become my first choice, but not all the extensions are yet available, or they were not available before I purchased them.

• 
  Eric Schweizer (@ericschweizer) reported 19 minutes ago

  @masoncapitalllc @remarks They did this with cloudflare last week. Put AI in charge of report tickets screening. It was a total disaster. AI was shutting down legitimate sites hundreds of them. A site dedicated on preventing sites from being shut down was the one doing the shut downs. AI not reliable.

• 
  Kazani (@kazani351) reported 20 minutes ago

  5/ The signal most people missed: 47% of all agentic transactions on Base now run through @virtuals_io. Add the x402 wave around Base, Cloudflare, @youdotcom, @browser_use x Coinbase, all letting AI agents pay per request in USDC. Agents are Base's next users.

• 
  dweewq (@eweqss1431) reported 22 minutes ago

  Agencies charge $8,000 to $12,000 for a marketing site, three weeks of calls, two rounds of revisions, one invoice that makes you sit down. Claude Code builds the same site in an afternoon, but most people still get template output because they type "make it beautiful" and pray. Claude defaults to safe every time: Inter font, purple gradients, three feature cards. The ten thousand dollar look comes from constraints, not vibes. The fix starts before a single line of design gets written. Load actual design rules into Claude Code as skills, so it checks a ruleset before every decision instead of guessing what "premium" means. Then screenshots beat adjectives completely. Three reference sites from your niche, paired with an explicit instruction not to copy the layout, give the model an actual quality bar to hit instead of a vague adjective to interpret. The build itself is one prompt with five blocks: who the audience is, the single action every page should push toward, the references to match, the tech stack, and a banned list of every cliché you don't want showing up. First working version lands in under ten minutes, about seventy percent there, which is exactly the point, nobody ships version one. The part that actually earns the price tag is the polish pass agencies bill forty percent of the project for: typography, spacing, and motion, run as three separate messages instead of one, because asking for all three at once gets one dimension fixed well and two fixed badly. A mobile check at 375px catches what breaks, since most traffic is a phone regardless of what the desktop preview looks like. Shipping costs nothing after that. Push to GitHub, connect Cloudflare Pages, deploy. The agency was always selling three weeks of process. The process was always one afternoon.

• 
  Jim Liu (@jiahanjimliu) reported 22 minutes ago

  Neoclouds, $IREN: The Inference Market OpenRouter is 2% of global LLM token consumption (1) but 10% of Open Source tokens that's not on-prem aka available to AI Platforms / Neoclouds. Global LLM token consumption includes OpenAI/Anthropic and is massively inflated by free tokens. Let's take a full look of the inference market. Closed Source Although OpenAI holds ~24.4% of the token market vs Anthropic's 15.6%, Anthropic has a much higher revenue share of 40% compared to OpenAI's 27%. On aggregate, Anthropic API is more expensive than OpenAI and OpenAI has moved onto competing with cheaper Open Source models with ChatGPT-5.6 Luna. Other paid proprietary including Gemini and xAI are 9.8% of token share and 27% of revenue share. Open Source Removing Closed Sourced and Free Tokens. A majority of OpenSource is hosted on-prem meaning that enterprises deploy their own inference stack onto bare metal. When I say bare metal I mean bare metal + kubernetes. This is 19.5% of global token share but 54% of non-free Open Source. The portions of the market that are available to AI Platform and Neoclouds are 1.5% OpenRouter and 14.6% of Hosted not OpenRouter. This leaves OpenRouter as 10% of the market available to AI Platform / Neoclouds. Although OpenRouter is not an accurate representation of total LLM token consumption, it's a decently accurate estimate of Open Source AI Platforms / Neoclouds. Top AI Platforms Most AI Platforms serve DeepSeek V4 and GLM 5.2, but many do not serve Kimi K3 because Kimi K3 requires a revenue share agreement. OpenRouter keeps track of token market share on a 1-day window. Having track those windows over the past week, it's clear that the leading AI Platforms by market share are FireworksAI, Coreweave ($CRWV). Contenders include Modal, TogetherAI, NovitaAI, StreamLake, GMICloud, Digital Ocean ($DOCN). Nebius ($NBIS) did have market share in Kimi K3 and had 0.6% market share at one point but had dropped out since they had not implemented KV cacheing yet (2). Bare Metal + Kubernetes People call it bare metals but almost all bare metal includes software in that Kubernetes is included. So yes, techically every Neocloud, $CRWV, $NBIS, $IREN sells software with all their GPUs. Yes $IREN has had Kubernetes before Mirantis as they were/are selling to AI Startup HumeAI. What Mirantis brings is orchestration, not Kubernetes. However, what we actually want to know is how much of the market is higher level software services aka SaaS/TaaS? The answer is the market is mostly bare metal (IaaS) with some PaaS. Even 70% of $MSFT AI revenue is bare metal with possibily some PaaS to OpenAI (3). You can bet a majority of AWS AI revenue is to Anthropic. Oracle is a large part to OpenAI and GCP sells alot of Anthropic. Many Enterprises from Netflix, Uber, to startups like Cursor, Perplexity, FigureAI all work on IaaS+Paas. The latter 2 are $IREN customers and the former is a $CRWV and $NBIS customer. Most likely Shopify and Cloudflare work on IaaS+PaaS as Shopify utilizes both GCP + $NBIS and Cloudflare utilizes both $CRWV + $NBIS. Mirantis enables $IREN to do IaaS+PaaS which is the majority of the market. If need be, many of these AI platforms dedicated to inference will be on sale to consolidate in the next 2-4 years and $IREN will be able to pick one up for ~3-10B.

• 
  dlxeva (@dlxeva) reported 24 minutes ago

  Stopping the bad guys with Cloudflare: 4,960 malicious requests blocked or challenged in the last month #cloudflare

• 
  kiruwaaaa (@kiruwaaaaaa) reported 26 minutes ago

  Base just admitted by quietly killing its own social app... @base spent 2025 building a consumer social network on top of the chain. In July 2026, that got walked back entirely - the app handed off, and the entire chain repointed at three things: trading, payments, and AI agents. > 92.8% of all AI agent payments on the internet right now settle on Base > 99.8% of those payments run in USDC through x402, the protocol Coinbase built with Cloudflare > Base alone has processed over $19 trillion in stablecoin volume this year - more than most G20 economies move annually This isn't a pivot. It's an admission that agents, not people, are about to be the largest customer base ever handed to Coinbase in one product cycle. Stripe is chasing this with MPP. UnionPay has APOP. OKX shipped APP. Four protocols launched in twelve months because everyone can see where the money is going - software paying software, instantly, without a human clicking approve. Base didnt lose the social experiment. It just noticed the actual customer walking through the door wasn't a person at all.

• 
  x402 Trust (@Jonas06699258) reported 27 minutes ago

  "What even is x402...??" This is a question that comes up every. single. time. when I show the service I've built over the last couple of months to my friends, collegues and family. Like it or not: We (as in "we" here in the x402 community and tech scene) are living in a bubble. Look over the plates rim and you'll quickly realize that x402 is still a very niche technology that barely anyone has heard of... And I say that as someone working in IT for a living, with the majority of my friends doing so as well. The idea behind the protocol is huge, sure. The execution is brilliant and has proven that it works, deployed on a wide scale already, yes. Adoption is rising, with major players like Cloudflare adding native x402 support to their products, that's undeniable. But for the average consumer? They've never heard of it, and if I'm being honest: It's better this way. You also don't explain to your grandpa what HTTP is when you show him the internet. "This is Google, your searchengine, with which you can find any info for anything you desire!" is as deep as it gets. And what about the builders? The tinkerers? The programmers, people who work in IT for a living? They haven't heard of it either... Not because they're ignorant or uninterested in new technologies, but because the surface of exposure is still so small that only people in extremely specific fields (agent-development or integration of web-based payment systems) hear about it organically. I have to say, I'm lucky to be one of these people. And because I like to teach my friends, family, coworkers and anybody on the internet new things, I've written up a small interactive webpage, which shows what x402 is, but simplified: So anyone can understand it & anyone can try it out for himself!

• 
  ChainPeak (@chainpeak) reported 27 minutes ago

  Cloudflare just introduced programmable wallets that allow AI agents to hold stablecoins, receive funds and purchase services across the web. The bigger signal here isn't another company launching a wallet. It's that one of the world's largest internet infrastructure companies is now building financial infrastructure for AI agents. #ChainPeak

• 
  🔥🏴‍☠️CyberTechWolf🏴‍☠️🔥 (@CyberTechWolff) reported 27 minutes ago

  @interesting_aIl Why they got a phobia of bots on the Internet and we have to ******* use newer Operating Systems just to visit a ******* website? I think cloudflare is full of ******* **** if that was the case you wouldn't have to verify if you're a "bot" each website you ******* visit.

• 
  Mysticle (@Mysticle_) reported 28 minutes ago

  @CloudflareDev seems Wordpress APO (Cloudflare paid tool) is not caching, all HTML requests reporting DYNAMIC. There's 2 active topics on community forum about this. Paid service - please address.

• 
  Anonymous Nobody (@AFuckingNobody) reported 34 minutes ago

  I don’t think I will ever stop vibecoding now that I started. Something that I thought would always be out of reach isn’t out of reach anymore. I can now turn my ideas into something interactive. Making art will always be something I do. Now, the experience will be more fun for everyone. Once testnet is thoroughly tested and built out the way I want it, I’ll start launching. And while I’m launching, I’ll still be building. Once you start building, even if you don’t know anything, you start learning. I literally had never even used Powershell before. Hadn’t used the cmd window since 1992. Knew nothing about piñata. Nothing about Solidity. Barely knew anything about Cloudflare. Barely knew anything about Sepolia Testnet. Definitely didn’t know how to build a site with web3 capabilities. I’ve paid nothing for hosting. $20 a month for ChatGPT. $24 a year for my domain. Bye bye platforms. Bye bye marketplaces. Anybody can do what I’m doing. Nobody needs a third party.

• 
  Jimmy Pringles (@Rat_Bag113) reported 37 minutes ago

  @itslivny Mate do you wanna fix your Cloudflare or something.

• 
  Korra AI (@KorraFinance) reported 42 minutes ago

  @StockSavvyShay The engine for that growth is already running: 57.5% of all web traffic is now automated bots, per Cloudflare. The biggest customer for cloud infrastructure won't be humans using AI; it will be AI agents themselves. That's the real capex supercycle.

• 
  Csaba Kissi (@csaba_kissi) reported 43 minutes ago

  I switched from Namecheap to Cloudflare for the domain registration. Because of the better price for domain renewals. What service do you use?

• 
  Aryuemaan Chowdhury (@aryuminstrel) reported 45 minutes ago

  Stopping the bad guys with Cloudflare 1,314 malicious requests blocked and challenged in the last month #cloudflare

• 
  Sydney Business Web | Web Systems Engineering (@KeithRowley66) reported 47 minutes ago

  Doncha love it when stuff works? This data is generated from edge Workers running on Cloudflare. The requests are observed at Cloudflare’s edge before they reach the website origin, and the resulting retrieval outcomes are recorded there too. The telemetry is then filtered, corroborated and categorised so we get useful numbers for the actual business pages and machine-discovery resources that credible AI and search crawlers are retrieving — not useless raw “Kilroy was here 6,000 times” bot-hit numbers. Synthetic tests, diagnostic fetches, support assets and weakly identified crawler traffic are excluded from the headline evidence. Even the telemetry stays in Cloudflare: it’s stored in Analytics Engine and queried using SQL. The point isn’t to count bots. It’s to measure what identifiable machine systems actually retrieve — and whether the retrieval succeeds.

• 
  Ryan Hicks (@RyanThomasHicks) reported 51 minutes ago

  @waynesutton @Cloudflare @CloudflareDev This would be nice! Ran into an issue on setup this weekend myself

• 
  brain (@miladybrain) reported 54 minutes ago

  holy **** it just occurred to me that Elon might buy Cloudflare

• 
  Andrew Jefferson (@EastlondonDev) reported 54 minutes ago

  @dok2001 @kirso_ Just becuase other clouds are bad doesn’t mean ppl shouldn’t strive to be better - but I’ll take cloudflare any day for billing

• 
  Jeremy (@Jeremybtc) reported 56 minutes ago

  Cloudflare built a browser that no human can use Kitesurf renders pages for AI agents only It has no tabs or themes and there's no use for extensions or perfect rendering It runs 3 to 7x lighter on CPU and memory than Chromium It also runs 1.7 to 1.8x slower A bad product for one human user and a great one for ten thousand agents Cloudflare built it in 12 weeks They're not building for the future of people browsing more, they're building so machines can browse more

• 
  LonestarDomains (@LoneStarDomains) reported 59 minutes ago

  @n0tme23235 @andrewhorowitz you beat me to this response. The domain name forum is full of people who love cloudflare as a registrar because they save $1 on domain name registrations. Why is this bad? You cannot change DNS records. You pay for a functionally broken domain name.

• 
  Quentin (@QuentLaBrute) reported 1 hour ago

  @sri9s Never tried it actually, always used Cloudflare. Is it better?

• 
  Ryzm (@Goeun_6121) reported 1 hour ago

  Cloudflare plans to issue $2.175 billion of convertible senior notes due 2031 in a private offering