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	10 days ago
Los Angeles	Cloud Services	12 days ago
Paris	Cloud Services	27 days ago
New York City	Hosting	30 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:

• 
  Kawa Entertainment (@kawa_entertain) reported 5 minutes ago

  @addzeeyy @Cloudflare That's what I've been doing all morning, unfortunately. All we can do is hope they get taken down quickly.

• 
  Robby Seventeen (@Robby_Seventeen) reported 7 minutes ago

  @eastdakota @Cloudflare the brand account can't post at 1am about a bad deploy. that's the whole gap right there.

• 
  Brendan ⚡️ (@BrendanHufford) reported 8 minutes ago

  Cloudflare just built an AEO visibility dashboard into their core product. Not a third-party tool. Not a Chrome extension from a startup that raised $4M and will pivot to something else in 8 months. Cloudflare. The company that sees 20% of all web traffic. AEO is moving from the marketing budget to the infrastructure budget. And once something moves into infrastructure, it never moves back. What's interesting to me here is that Cloudflare has the first-party data. They can see which AI crawlers are hitting your site, how often, what they're pulling. No guessing. I think this is the thing that makes AEO real to CFOs.

• 
  Hamid Siddiqui (@hamidInventions) reported 9 minutes ago

  @wickedguro @markgalkev tbh now not 100% sure if it might be the same reason since you mentioned everyone getting this same time but i strongly feel it would be Cloudflare only, I faced this issue few months back. When i was debugging this I disabled Cloudflare proxy for a while and tested posting the posts that were failing to post on TikTok, and they worked fine. I also used to face similar issue with fal.i/replicate where they would randomly fail to get the R2 image url i passed for image generation. It was fixed as well. The exact steps i took I don't recall, would have to check what settings i did change eventually.

• 
  Steven Liss (@This_Liss) reported 11 minutes ago

  @joe_zappa @fsinton @BishPlsOk Brands are doing anything they can to influence how they show up in AI. There's already a market for off-site GEO and astroturfing. AI companies have a choice: increasingly get blocked by publishers, pay publishers (lol never), or rely on their existing retrieval system to inherently filter for relevance while allowing publishers a business model that enriches search results and keeps publishers in business. Perplexity's now an enterprise B2B company, so removing any possibility of ads is more aligned with their use-case. They're also more likely to get blocked outright by publishers, since the amount of display ad revenue at stake from Perplexity referred traffic is vanishingly small. Realistically, I see Anthropic following suit until publishers become much more aggressive about blocking noncompliant bot traffic (which Cloudflare is helping accelerate or the legal costs of unauthorized retrieval increase (NY state's Stealth Crawler Prohibition Act).

• 
  ⓧ Jon Theory 🐍👑 Ω 7 (@Xenfluencer) reported 11 minutes ago

  HTTP 402 has sat in the spec since 1997, marked reserved for future use. Cloudflare has switched it on. Anything behind their gateway can now carry a price. A page, a dataset, an API, an MCP tool call. An agent requests it, gets back 402 Payment Required with a price, pays, retries with proof. The request becomes the transaction. Stablecoins are what make that work. Card rails cannot process a third of a cent, and they assume an account and a reversal window. An agent holds a wallet, signs, settles in seconds. File crypto under speculation and you miss it. The thing unblocking the agent internet is boring programmable money that clears at sizes nobody else would bother with. The old bargain: a crawler took your content, search sent you a human, you monetised their attention. Agents break the second half. The content still creates value. The visit never arrives. An archive of 300 videos earns pre-roll on an interview from seven years ago. In an agent internet it is a tool an assistant pays a fraction of a penny to use, every time someone needs your judgement. So the question changes. It stops being how do I get more eyes on this. It becomes what do I know that a machine would pay to use. Most people will answer that late…

• 
  Harsh (@harsh_biz) reported 14 minutes ago

  The deliverability meta going into Q4 2026 is different from what worked in Q1. If you're still building infrastructure the way you did at the start of the year, you're going to feel it next quarter. SURBL made a lot of noise this quarter. Cold email inboxes got flagged in batches, everyone scrambled, and the enforcement has already lost most of its teeth. But the fixes are still the right build. Not because SURBL is going to catch you. Because when you build this way, there's almost nothing left for any ESP to pattern-match against. SURBL won't be relevant soon from what I think. You're no longer defending against a specific list. You're removing the mechanical fingerprint that makes automated detection possible at all. Practically: Keep domains to 20 per registrar account, 50 at the absolute ceiling, spread across multiple accounts. Once your domains aren't clustered, there's no cluster to flag. Stop naming them [Company]aa, [Company]ab, [Company]ac. Branch out entirely instead. If the brand is Milbridge Capital, use Milbridge Advisory, MBCapital, MilbridgeGroup, or drop the brand pattern altogether and use unrelated professional-sounding names. Older domains with genuinely varied names get listed far less often, and that holds regardless of which blacklist happens to be active. Placement tests are dead. They were reliable in early 2025. They aren't now. You can score 100% inbox placement on a test and pull a 0% reply rate on the live campaign the next day. Replies are the only trustworthy signal left. Build your monitoring around reply rate at the sender-email level, excluding auto-replies, and pull inboxes when they drop below threshold. Masking beats redirects, and both beat nothing. Redirects have visibly hurt deliverability this year. Dead domains hurt too, because prospects check the domain and expect a real site. Build masking through Cloudflare Workers rather than paying a markup for it. One free Cloudflare account holds around 80 domains. Your lead source is now a deliverability factor. Cheapest leads reply the least on average, and low reply rates suppress sender reputation. That's not a relevance problem, it's an infrastructure problem. When a campaign starts dying, diagnose before you rebuild. If two or three campaigns trend down at once, it's the copy. Rotate it. If you rotate the copy well and nothing recovers, it's the inboxes. Fix the wrong one and you burn another month.

• 
  aditya - oss/acc (@0x0elliot) reported 17 minutes ago

  pretty sure i saw cloudflare workers acting like **** for a second there. the few services i have hosted there are not responding/taking too long. glad i don't host anything critical on there.

• 
  Akash Rajpurohit (@akashwhocodes) reported 18 minutes ago

  @VinodSharma10x Man, that sucks, hope you have rate limiting already in place. Also seems like Cloudflare dashboard, enable the Under attack mode, might help a bit!

• 
  trap broker (@trapbroka) reported 21 minutes ago

  🚨 THE MACHINE ECONOMY IS QUIETLY BEING BUILT. AI agents are getting something they never had before: IDENTITY + WALLETS. Cloudflare just announced infrastructure that allows AI agents to have a stable identity and make payments within defined limits. Official Cloudflare headline — “Cloudflare Gives AI Agents an Identity and a Wallet” But that’s only one piece. 🇨🇳 DeepSeek just invested $20.8M in Unitree, the Chinese humanoid robotics company. Unitree is being valued at around $9 BILLION. AI is being connected directly to physical machines. Reuters — DeepSeek invests $20.8M in Unitree And while that happens… 🏦 Wall Street is putting real assets on-chain. DTCC has already processed live production trades using tokenized assets, with its broader tokenization service planned for October 2026. DTCC — Tokenization Becomes a Reality Think about what this actually means. AI gets wallets. Robots get AI brains. Financial assets get tokenized. Machines can increasingly interact with digital services and, eventually, with each other economically. AI + CRYPTO + ROBOTICS = THE MACHINE ECONOMY. Everyone is looking at the next memecoin. Meanwhile, the infrastructure for machines to earn, spend and transact is being built in real time. Maybe the next billion users of crypto won’t be human. Maybe they’ll be machines. 🤖

• 
  Dwinity (@dwinity_eco) reported 22 minutes ago

  @signalapp @Cloudflare the math was never the weak part. the key directory was. every e2e messenger asks you to trust a server handing out keys, and apple shipped contact key verification in ios 17.2 for exactly that. verification you have to remember to do is verification nobody does.

• 
  Michael Tanguma (@MTanguma) reported 23 minutes ago

  AI is breaking the free internet. When a human visits a website, free access is cheap enough to subsidize. When a bot can hit it a million times for almost nothing, it isn’t. That changes the economics completely. Micropayments were part of the internet’s original vision. They never shipped, so we built the web around ads, surveillance, subscriptions, and platforms instead. AI may finally force the correction. Charge a human a few sats and they barely notice. Charge a bot a few sats every request and suddenly spam, scraping, and abuse have a real marginal cost. Cloudflare is moving this direction. Lightning makes it possible. Others will follow. The internet is finally getting a native payment layer because AI is making free access economically impossible. Full Final Settlement rip below

• 
  Galath (@W0rkerOfSecrets) reported 24 minutes ago

  @classy1mil 🫣 sorry it’s my first website and I had some major issues with it. I’ve been go in insane figuring out CloudFlare. Issues almost resolved. I am going to bring something like it back soon. I might even be able to bring it back in some capacity too.

• 
  Prmai (@Prmai_) reported 25 minutes ago

  @synopsi @Cloudflare been using it for years. never had to pay them a things.

• 
  Oliver | (@olihels) reported 27 minutes ago

  Cloudflare built payment rails for AI agents to pay per visit. Most businesses can't collect any of it because their pricing pages and PDFs aren't clean enough for an agent to read. Fix the data before you chase the payment.

• 
  Udit (@TherealUDP) reported 27 minutes ago

  I'm cryin dude saw a classmate flexing on story his kali linux with four terminals open using hping3 flood on a cloudflare hosted game server bragging he can down any game server/wifi he wants

• 
  Jim Liu (@jiahanjimliu) reported 27 minutes ago

  $CRWV: Q2 Earnings Revenue: 2.6B or 10.4B ARR EOY 2026 ARR Target: 18B-19B Backlog: 104.2B at end of Q2 (129.2B Aug 11) Adjusted EBITDA Margin: 59% Operating Margin: 5% Adjusted Net Loss: -22% Full AI Platform Contrary to misinformation on X, Coreweave serves Managed Inference, Development Tools, Orchestration and Observability and are a full AI Platform. EBITDA Margins Their EBITDA margins with software come out to 59%. $IREN's H1-4 EBITDA margins are 85% but after depreciating DC build cost for an apple-to-apple's comparison, $IREN's H1-4 EBITDA margin minus DC depreciation come out to 55%. $IREN is able to keep up on EBITDA margins without software because IREN is vertically integrated on the power and datacenter front. Coreweave's software make up for it's colocation costs to achieve 59% EBITDA margins. For comparison $NBIS has ~40% EBITDA margins. Once $IREN integrates Mirantis and DSX OS, it has a great chance of leading on EBITDA margins among the 3 Neoclouds. Backlog Coreweave hit a 129.2B backlog on earnings day Aug 11 which is a huge 25B increase from 104.2B at end of Q2. This is great news for $CRWV, $NBIS, $IREN as it shows the unprecedented demand in this sector. Financing Coreweave will likely benefit from Nvidia's 500B financing pool along with $NBIS and $IREN. However, it's high interest cost make it's Net Loss Margin -22% on what otherwise is a great inflection point of 5% operating income. In other words, Coreweave is a profitable business operations wise besides its high interest payments. This bodes well for Neocloud sector profitability as a whole. Enterprise Customers Coreweave has the widest diversification of customers among Neoclouds with: Primary Cloud: Bentley, Caterpillar, Grammarly, Isomorphic Labs, Sunday Robotics. Expanded Partnership with: Cognition, Databricks, HRT, Periodic Labs, Rescale, Runway ML. Primary cloud is important because although Coreweave and NBIS both serve Cloudflare, they are not the primary cloud for cloudflare. Likewise Shopfiy's primary cloud is GCP not NBIS. Being a primary cloud for a customer is more indicative of usage beyond of orchestrated GPUs or bare metal+k8s. Contracted Power 3.7GW by end of Q2 and 4.2GW by Aug 11. This is a majority colocation however, colocation is working for Coreweave as they still achieve 59% EBITDA margin. This sometimes results in delay but their main problem is interest expense, not colocation. $CRWV is a 55B company with 35B debt for a total of 90B EV. If $IREN can buildout 5GW and integrate in Mirantis to catch Coreweave, it has large upside as $CRWV itself still has significant upside from it's 90B EV.

• 
  INFOSEC.WATCH (@InfosecDotWatch) reported 28 minutes ago

  The N-central story is bigger than a vulnerable management server. N-able says attackers used the legitimate Take Control feature to reach managed endpoints, then installed a Cloudflare tunnel service for persistence. RMM compromise is a downstream hunt problem.

• 
  Yamparala Rahul (@yamparalarahul1) reported 31 minutes ago

  @vercel & @vercel_dev why you pause all the projects of user if free trier usage is going beyond, why not help me (users) optimise? This make me and others probably shift to @Cloudflare

• 
  PawelEDi(🦄,🦄).base.eth (@PawelEdi) reported 32 minutes ago

  @signalapp @Cloudflare Can a third party open the Signal app and access all messages and take control of the Signal app if the Android smartphone is lost, stolen, or forcibly taken? The smartphone and app were pattern-locked.

• 
  Jason Fleagle (@jjfleagle) reported 34 minutes ago

  @Cloudflare A 519% surge should change resilience testing. Rehearse saturation by dependency, upstream failure, control-plane isolation, degraded service priorities, communications, evidence retention, and recovery time. The useful metric is which critical service still meets its promise.

• 
  John Curtis (@jcurtis) reported 37 minutes ago

  @tharshan_09 @rauchg This turned out to be a long answer...but I like to share! The simplest way to describe it is as an overbuilt local replacement for Context7. I tend to keep technical documentation for all the major libraries I use, from TanStack to third-party services like Browserbase. As of today, it contains 89 top-level directories, one of which is "cloudflare" - inside is about 3K md files. I like letting my agents access the latest, grounded context and ensuring they are getting the exact information they need, rather than relying on random search results or Context7, where the interpretation may not always be what I/human wanted. Historically, I would paste a local path to the agent and say, “Here are the specifics on XYZ, for or re: Durable Objects.” Now, I can simply tell it to use the `aidocs` CLI, and in under 80 ms, it returns both vector and/or semantic (bm25) results. vectors are using @VoyageAI for the corpus of content, but the local queries use their nano model self hosted. I have sqlite for the FTS5/BM25 lexical ranking side and lancedb for the vector side. query time free, ingest costs if the doc changed but so far its been well worth it. this scriptC came up for me since there was this startup wall I couldnt get through without a drastic change. turns out compiling to C will do that. But the background ....I have been letting agents run at night on specific sides of the system (user side like - lexical query, vector query, ranking, loading directory details etc..maint side like loading and audits) and each night i have a set of benchmarks on that specific part of the system and i set a /goal to try various ideas to see what can move the needle by more than 10% so minutes in some cases have become seconds and s has become ms. No rush just a constant race to be faster with the same bar of output quality. For example comparing the xxhashes between sqlite and lance was a bit slow, so we evaluated a bunch of options and ended with a Merkle tree which makes row integrity auditing 17x faster and 11x faster for mismatch finding. is it noticeable? not sure, since the primary user is the agent, but last night this merkle tree moved a p95 from 38.49ms to 3.2ms, or the time to rebuild the index from 655ms to just 43.5ms. Im well in to the diminishing returns area but its still fun!

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 42 minutes ago

  What does an AI agent actually pay for? Clean data that is structured and easy to access. Cloudflare is building the access and payment layer right now. So it's still early, you have 6, 12, maybe 18 months. Start with building the manual version and sell it to humans today. Curate the data before the space gets hyper-competitive. Five questions that point you at an idea: - 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? The internet is shifting from pages humans visit to resources agents use.

• 
  Ravin Sharma (@ravinsharma7) reported 44 minutes ago

  Can attest to this. Been experimenting with many things using Cloudflare infra, the cost is literally a few dollars. In the past i read about horror stories related to cloudflare billing and support, but not sure still applies today or not. I'm just happy stuff just works without breaking the bank.

• 
  h index enjoyer (@BigwetRealism) reported 46 minutes ago

  getting real tired of hitting cloudflare issues on @biorxivpreprint even tho I'm not a bot!!!!

• 
  Hajnen Payson (@hajnen) reported 52 minutes ago

  Everyone thinks AI layoffs are just about replacing coders and copywriters. Look closer at the restructuring at Amazon, Cloudflare, and Block. They aren't just replacing tasks. They are eliminating "The Coordinator." For decades, corporate structures needed middle managers because compiling reports and passing information between departments was slow and expensive. AI now does that instantly. But there is a massive trap hiding in these new "flat" org charts: If a company cuts headcount first, but fails to redesign its legacy approval processes—the remaining employees are completely screwed. You inherit the exact same meetings, the same performance expectations, and the same corporate bureaucracy... just with fewer colleagues to help you do it. Cutting heads without redesigning the workflow isn't an "AI Transformation." It's just a recipe for burning out your top performers. Source article by @DocHutcheson

• 
  LeminLimez (@LeminLimez) reported 55 minutes ago

  @khcrysalis we have tried cloudflare before and it caused issues with the nameserver, breaking other services. We may try it again

• 
  Sean Finnerty (@sean_infinnerty) reported 57 minutes ago

  @jpschroeder @dschewchenko someone from @Cloudflare recently posted on X that spend limits were actively being worked and would be shipped soon. Better late than never

• 
  ian (@sivasiann) reported 1 hour ago

  My biggest conspiracy theory is that the US was mad that the Internet was too decentralized and hard to control that they were behind the massive rise in DDOS attacks so they can sell us the nice centralized and controllable Cloudflare as the solution to the problem they created

• 
  Peter Machona (@chilumbamachona) reported 1 hour ago

  @AnthropicAI @OpenAI I.e you ask Claude to help you decide between Cloudflare AI gateway & OpenRouter - it will search the web and come back with a comparison table that actually has some values that are false and until you check you would not know.