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 (39%)
• Domains (22%)
• Web Tools (22%)
• Hosting (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	11 days ago
Los Angeles	Cloud Services	13 days ago
Paris	Cloud Services	28 days ago
New York City	Hosting	1 month 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:

• 
  Trishool | SN23 (@trishoolai) reported 4 minutes ago

  The last time a security category went mainstream, it minted some of the biggest companies in tech. AI security is the next one, and it is bigger. • Palo Alto Networks, around 127 billion dollars • CrowdStrike, around 123 billion • Cloudflare, around 65 billion • Wiz, zero to a 32 billion dollar Google acquisition in about four years That is what happens when a security category stops being optional and becomes infrastructure the whole market has to buy. It does not produce good returns. It produces generational ones. The threats in AI are worse, they are faster, and they are already in production, with models breaking out of sandboxes and into real systems right now. This demand is not a forecast, it is already here. Here is what makes it different from every security bet before it. Those giants were private companies, so to own a piece early you had to be inside the cap table, and by the time you could buy in the asymmetry was gone. The control layer for AI cannot be a single company. It has to be a neutral network nobody owns, so for the first time the category-defining position is open, on-chain, and ownable at the start instead of read about after. That position has a name. 𝗧𝗿𝗶𝘀𝗵𝗼𝗼𝗹 is building the control layer for AI on Bittensor, a live network with a real product, real backers, and a token you can hold from the start. No bet like this is a sure thing, and anyone who tells you otherwise is selling something. Early networks carry real risk, but the shape here is rare. What you put in is the downside. The upside is a category that keeps producing 30 to 130 billion dollar outcomes, and this time you can own it early.

• 
  favoritbookshop🚢 (@favoritbookshop) reported 9 minutes ago

  For years, the crypto industry has searched for a mainstream use case for stablecoins. The answer may be arriving from an unexpected direction: not humans, but machines. Cloudflare is pushing toward an agentic Internet where software can request and pay for digital resources automatically. Its Monetization Gateway is designed to let websites, APIs, datasets and MCP tools charge users in stablecoins through x402, an open protocol built around the long-unused HTTP "402 Payment Required" status. This matters because AI agents operate very differently from humans. A human might make a few payments per day. An autonomous agent could make thousands of API calls, purchase datasets, access compute, retrieve information and interact with other services — potentially around the clock. Traditional payment rails were not designed for this. Why stablecoins fit the machine economy AI agents don't need a bank account in the traditional sense. They need: - programmable spending rules; - fast settlement; - global access; - low transaction costs; - machine-readable payment instructions; - the ability to transact without a human approving every purchase. That is exactly the problem stablecoins can address. Cloudflare describes x402 as a mechanism where an agent requests a resource, receives a machine-readable "402 Payment Required" response containing payment terms, pays, and retries the request with proof of payment. The payment itself becomes the credential. That is a radically different model from: Sign up → create account → enter card → receive API key → get billed later. Instead: Request → pay → receive. For machines, that distinction is huge. The infrastructure is already forming Cloudflare isn't moving alone. MetaMask has introduced Agent Wallet, giving AI agents dedicated wallets with user-defined policies and a security pipeline that includes transaction simulation, threat scanning and MEV protection. Transactions outside predefined policies can require human approval, while eligible safe transactions receive up to $10,000 per month in Transaction Protection coverage. This is an important evolution. The agent receives a budget, follows predefined rules, pays for resources and potentially earns revenue — without requiring a human to manually sign every transaction. The bigger shift: from blockchain economy to application economy This is where the thesis becomes interesting for crypto investors. The next major value capture may not happen at the blockchain layer alone. It may happen at the application and infrastructure layer — where users and agents actually consume services. Cloudflare's own vision is explicit: agents could eventually become primary buyers on the Internet, purchasing datasets, API calls, tools and compute automatically. If that happens at scale, stablecoins stop being merely an alternative payment method. They become machine-native money. What traders should watch The investment thesis is broader than simply buying “AI tokens.” Watch the infrastructure connecting four layers: AI agents → wallets → stablecoins → payment protocols The winners could include: - stablecoin issuers; - payment protocols; - agent-wallet infrastructure; - blockchain networks optimized for cheap settlement; - API and data marketplaces; - DeFi protocols that agents can interact with programmatically. The most interesting question is therefore not: “Will AI use crypto?” It is: “How much economic activity will autonomous software generate — and which crypto rails will capture that activity?” We're still early. But the direction is becoming increasingly clear: the next generation of crypto users may not have a face, a phone or even a human behind the transaction. They may be agents. And when millions of machines start buying from millions of other machines, someone will need money that machines can actually use. Stablecoins may have just found their killer customer.

• 
  404oops (@oops4041555) reported 11 minutes ago

  @spinelessaisha get a raspi and set up an argo tunnel. simplest ****. you need to pay yearly for a domain, but you can get free domains for like a year or something at freenom (which is what i used before i got my .com) or set up a cloudflare pages at your domain if you have static crap only.

• 
  Kay 🏍️😈 2.0 Fall! (@KayohVT) reported 16 minutes ago

  @hxlxlist Cloudflare is always the worst. Best of luck!!

• 
  ./ivan (@sloaxleak) reported 17 minutes ago

  @a_shimanski @Namecheap @Cloudflare Haha. Or just pay for a reliable email service: Google Workspace, Microsoft 365, or a Proton subscription with a custom domain. There are options. I love Cloudflare, but not everything needs to be solved by them

• 
  Deano (@deanthebard) reported 18 minutes ago

  @bhavyapandya07 Two hours down here, thought it was Cloudflare at first.

• 
  Whezzel (@Whezzel) reported 21 minutes ago

  @ReinhardtOp @ReclaimTheNetHQ Tbf, there already are registries located outside the us, but they have their own challenges. The issue you'll still run into is most of the internet runs on American infrastructure, built by the us governemt and American business. Google, Amazon, Cloudflare and others. On top of that verisign manages 2 of the root dns servers, with the majority of the remaining root dns servers hosted by other American entities. To top it off, verisign distributes the zone files for the root dns servers. If Verisign decides they don't want a domain listed in dns, good luck getting to it.

• 
  Warhead (@vz_warhead) reported 21 minutes ago

  @JaniBangiev damn, does it work the same for user's data in apps? should I also switch to cloudflare instead of supabase?

• 
  Red Arrow (@RedArrowPatrio2) reported 21 minutes ago

  @XFreeze Come to think of it there were Cloudflare issues around the same time that may have contributed to the problem.

• 
  Small News (@SmallNewsX) reported 24 minutes ago

  @ShimituMusic @NamecheapCEO Why will you take legal action? Since I started using Namecheap this is the first time their server went down. Big companies like Facebook, Cloudflare, even Google has gone down before so let’s take it easy with Namecheap.

• 
  Antonio Gomes (@onchainantonio) reported 28 minutes ago

  Been thinking about why cryptographic migrations always take so long 🤔 It's never the maths. SHA-1 was visibly weakening in 2005. Browsers didn't finish rejecting it until 2017. Twelve years, and we had SHA-256 the entire time. TLS 1.0 was superseded in 2006 and people were still switching it off in 2020. Every one of those delays came down to the same thing. Someone's payment terminal. Someone's embedded device. A vendor that went out of business years ago. A box nobody could turn off without breaking something else. The cryptography was ready. The world wasn't. Which is why that line is worth staring at for a minute. A year ago, under 40% of encrypted traffic used post-quantum key exchange. Today it's over 70%. That's the fastest cryptographic transition the internet has ever run, and it happened without a single person being asked to switch. The trick is that nothing was replaced. Classical and post-quantum key exchange run side by side in the same handshake. Old clients keep working exactly as before. Newer ones negotiate the stronger path automatically. Support arrives, the line moves, nobody files a ticket. No flag day. No deadline. No morning where the internet broke. That's what a migration looks like when it's designed around compatibility instead of coordination. Everyone planning for post-quantum should be studying that curve far harder than they're studying the algorithms. The algorithms are finished. Getting millions of systems to move without breaking any of them is the part nobody has pulled off twice in a row. @Cloudflare publish it live if you want to watch it move 👇

• 
  John C. 🇹🇹 (@jcamachott) reported 32 minutes ago

  @bhartzer @Namecheap "If you used @Cloudflare, for example, for DNS, then you could simply log into CF and point the DNS to another web host and your site or service would be back up and running in minutes." Not always as simple as it sounds. This also means restoring a website with yesterday's data to a new hosting account. It's really unusual for a hosting account to go down for several hours like this

• 
  Aleksejs Zuravlovs (@aleksztrading) reported 35 minutes ago

  @shownotover Oh.. you are from Pakistan! I had some good programmers from there many years ago. Damn, that's backwards, it should be the opposite, like in Steam - you get charged *less* from poorer countries, which makes sense. In that case, re-review everything. Do you need Contabo or can you push everything to Cloudflare? (it's free for quite a lot of traffic, but better ask Grok to verify the limits) Do you really need Grok at $30? I would get ChatGPT Codex at $20 + Open Code Go at $10 - much stronger stack, I think.

• 
  Edward T֍ (@edward_terhov) reported 39 minutes ago

  CLOUDFLARE THE GOAT Super underrated. Cuz wtf is vercel bro😭 how did these random hosts appear out of nowhere??

• 
  Jeremy Daniele (@jdanielenj) reported 40 minutes ago

  @firebol226860 @signalapp @Cloudflare You're the one claiming it's hacked. It's literally on you to bring the burden of proof. That is how all arguments work. You're asking me to prove a double negative lol. My proof is what Signal publicly provides. Your proof is your tests that prove they're lying.

• 
  Praveen Yadav (@yadavships) reported 40 minutes ago

  @deancochran_ @thdxr There are many provider like docker, @cloudflare/sandbox who support local as well like - E2B - Daytona - Runloop - Sandpack - Modals - Vercel Sandbox - Cladflare sandbox - Upstash Box - Ascii Box - Railway - NorthFlank

• 
  güs (@nukefags) reported 42 minutes ago

  @NEVER_G0ON Soybooru and ze Jarti haven’t used cloudflare in like 3 years. Null and d0ll swapped it over to a custom DDoS retarding service when the domain was switched to .st

• 
  Sean (@sean_from_earth) reported 44 minutes ago

  @TensorTemplar I'm not, Google started abandoning the informal agreement they formed with the open internet years ago with the overviews, etc that kept searchers on google instead of going to the actual links they surfaced. Cloudflare is just playing a variation of that game - inject yourself as the middleman for enough of the internet and you can exert a lot of control for your own purposes. The truth is, we need a new internet. This one is old and broken and about to be totally owned, controlled, and censored by nation states (well, the rest of them).

• 
  VC Intern (@the_vc_intern) reported 45 minutes ago

  Cloudflare is not shutting down Google Search on September 15. It is forcing Google to decide what Googlebot actually is. Cloudflare’s new controls divide crawlers into three jobs: Search, Training and Agent. Search remains allowed by default. Training and Agent traffic will be blocked on ad-supported pages for new sites and existing free customers that keep the new defaults. A crawler doing multiple jobs inherits the strictest rule. That puts Googlebot in an awkward position. Cloudflare classifies it as both Search and Training. A publisher that welcomes search indexing but rejects AI training can therefore block the entire bot. For years, bundling those jobs gave Google leverage. Publishers depended on search traffic, so refusing the crawler also meant disappearing from discovery. Cloudflare is moving that decision from a line in robots.txt to enforcement at its network edge. Google now has three choices: separate its crawlers, convince publishers to permit both uses, or lose access to pages that still want search traffic but no longer accept training as part of the bargain. The web is not dying here. Its access contract is being renegotiated. Robots.txt was a request. Cloudflare is turning it into a gate.

• 
  frango (@franguinlol) reported 50 minutes ago

  @drewlevin Thanks for the answer. I haven't made any changes to my internet or hardware; the only thing bothering me is the routing problem, which forces me to use Cloudflare sometimes because It becomes unplayable.

• 
  Vincenzo (@DaGiftedmind) reported 51 minutes ago

  This CloudFlare security verification thingy has started making browsing the Internet difficult for me I can barely access journal sites these days because the verification just never works. It just keeps rolling and rolling Is this an Internet speed thing or what?

• 
  RJ Finnegan (@1rjfinnegan) reported 51 minutes ago

  If your project isn't on @cloudflare, you're seriously missing out on not only huge savings but also flexibility. I used to think it was a benefit to have multiple vendors, which it is for some use cases, but Cloudflare honestly simplifies a lot of the infra for most applications. Plus, if Cloudflare ever goes down like it did last year, 80% of the other websites are also down 🤷

• 
  Artyom Shimanski (@a_shimanski) reported 52 minutes ago

  @XJosephCox @Cloudflare yeah, hard caps would fix half the horror stories

• 
  michibiki || szmf au in 📌 (@michibikionmain) reported 53 minutes ago

  dog what the hell is up with the 5 morbillion cloudflare checks and captchas on Twitter lately this is so ******* annoying and might really be the final straw in me leaving thia ******* site 😭😭😭 im just scrolling through and liking **** dog leave me tf alone!!!

• 
  Sterling Labs (@sl_wire) reported 54 minutes ago

  A crawl is a program walking the web on its own, saving a copy of each page to build the pile of text a model learns from. Each page gets taken once. That was 36.40% of AI bot traffic in January 2025 and 44.56% in July. Agent traffic is the other thing, a page fetched right then because you asked, and it was 2.63% last October and 2.65% in July. Nine months flat. Both are shares of AI bot traffic, not of the web. @CloudflareRadar counts this because Cloudflare sits in front of a big share of it, and out on the whole web bots were 34.81% of requests in July against 65.19% human. Agents are at most 0.92% of everything, and that assumes every bot is an AI bot. Call it a third of a percent. The tollbooth is already built. $NET opened Pay Per Crawl in private beta on July 1 at a one cent minimum per successful retrieval, and the network already returns more than two billion payment required responses a day. Its own June investor day line was that the vast majority never become a transaction. Purpose is self declared at registration and nobody audits it, so hold the levels loosely. Anthropic’s crawl to referral ratio fell from about 8,800 requests per referral in April to 2,800 in July, and Adobe measured AI referred retail visits up 138% year over year in May. We are following what the models tell us. The agents aren’t out doing the shopping. Yet.

• 
  $empiternal$trafe (@SempiternalStrf) reported 55 minutes ago

  @NamecheapCEO That time when your website is running with cloudflare pages (static) so you aren't affected by this. Altho' everything else what I have is down [the web hosting itself], so I hope my data and stuff won't be lost in this process.

• 
  Josh Mullins (@ETFbreakouts) reported 57 minutes ago

  I think there’s a lot more middle ground here. $APP slightly missed revenue expectations and gave an in-line guide. That matters at this valuation. But revenue still grew 53% and adjusted EBITDA grew 58%. That isn’t the next $TTD yet. Advertising is splitting into winners and losers as AI changes how people discover information: • $U Strategic Grow +63% • $META revenue +28% • Google Search ads +17% • $TTD +12% • $TBLA +2% • Google Network ads -1% Cloudflare recently said the ad-funded open-web model is breaking because AI answers the question without sending a human to the publisher’s page. That is a much bigger threat to publishers and open-internet advertising than to closed-loop performance platforms. The real question is whether AXON keeps proving conversion and attracting more ad spend. One quarter didn’t answer it.

• 
  City of Hats (@CityofHats) reported 1 hour ago

  @KuptoKosmos Signal’s AKV is a useful improvement, but “automatic” deserves an asterisk. Signal still operates the central key directory, while Cloudflare and Trail of Bits are explicitly trusted auditors. AKV proves consistency of the identifier → key mapping; it does not prove the identity behind that identifier. Even more interesting: today, verifying another user still requires knowing their phone number, and the user must explicitly open Safety Number and select “Verify automatically.” So this is better tamper detection — not the elimination of trust. The architectural question remains: why should identity/key discovery depend on a centralized directory and external witnesses at all?

• 
  Aleksejs Zuravlovs (@aleksztrading) reported 1 hour ago

  @a_shimanski @Namecheap @Cloudflare No, excellent service and support. Used it for ~2 years for multiple sites without any hiccups.

• 
  Jason Fleagle (@jjfleagle) reported 1 hour ago

  @Cloudflare Does the workflow help teams close the loop after an alert? I would want issuer context, affected names, first-seen time, expected-owner check, revocation status, DNS and hosting clues, incident assignment, and proof of resolution. Better signal needs a clear response path.