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 (50%)
• Domains (25%)
• Hosting (25%)

Live Outage Map

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

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

• 
  Cat (@cybersec_cat) reported 6 minutes ago

  Hey Cloudflare, you don’t get to take credit for stopping cyberattacks that came from your own infrastructure. You created the problem. Solving it doesn’t deserve anything but scrutiny.

• 
  Paul Witcombe (@paulwitcombe) reported 10 minutes ago

  @dhh @eastdakota @Cloudflare I just did a fresh install. Previously I had the Arch - Omarchy install. But now I’ve got a fresh Quattro install which is cleaner. 2 minutes 42 seconds install time which is pretty good for a 2012 MBP Pro. Just had Codex sort out a few wall issues. I’m having so much fun.

• 
  wa1gov (@wa1gov) reported 13 minutes ago

  @nixcraft According to grok: StatCounter data for July 2026 showed a sharp jump in Linux desktop share: globally to about 7.53%, and in North America to ~10.65% (roughly doubling from June). The U.S. figure was even higher in some snapshots. That jump is real in the traffic numbers, but it is not a clean “millions of people suddenly switched PCs” story. Several things happened at once. Measurement and traffic effects StatCounter had a large “Unknown” bucket in prior months. Some of that traffic was later identified as Linux, which inflates the July reading. Independent Cloudflare data also showed a rise, but a smaller one once bots are filtered out. A striking one-day spike appeared on Monday, July 6 (the first workday after the July 4 holiday), with Cloudflare reporting Linux at ~22% of human desktop traffic that day. That points to office/developer use rather than only home conversions. Bots and AI agents (which often run on Linux) also inflate raw web-share numbers. Underlying user reasons Even after discounting artifacts, there was genuine pressure toward Linux: -Windows 10 support ended in October 2025. Many older PCs cannot meet Windows 11 hardware requirements (TPM 2.0, etc.). Linux became the cheapest way to keep those machines useful. -Frustration with Windows 11 (privacy/Recall, Copilot, telemetry, stricter hardware needs). -Linux is lighter on RAM. That mattered as memory prices rose and Microsoft talked about making Windows 11 smoother on 8 GB. -Gaming compatibility improved a lot via Proton, Steam Deck, and related hardware, removing the old “games don’t work” objection for many people. -Developers and people running local AI tools often prefer Linux because toolchains, GPUs, and dependency management are simpler. Steam’s own survey did not show a matching explosion (Linux stayed around 4% of Steam users in July), which is another sign that the StatCounter spike is partly web-traffic and workplace use, not a mass consumer OS replacement. Bottom line: July’s spike mixed better OS detection, holiday-weekend-to-workweek traffic, bots/AI agents, and a real (but smaller) shift of users off aging Windows 10 PCs and away from Windows 11. The 10% North America headline overstates how many ordinary home desktops actually switched.

• 
  Ben Haupt (@benchaupt) reported 15 minutes ago

  I'm noticing a pattern of new(er) engineers (and vibe-developers) over-designing their tech stacks for simpler projects (e.g, mobile app backend on AWS)... It should be a pretty simple decision: buy the things where being wrong is a compliance event or an outage. Database = Postgres (just raw postgres) Auth = Auth0, Cognito or Clerk (compliance event) Email = Resend or SES (deliverability is pain) Payments = Stripe Cache = Redis Queue = Rabbit or Bull CDN + edge = Cloudflare Analytics = PostHog Observability = Prometheus + Loki + Sentry + Better Stack SMS = Twilio Compute = VPS (Synteq (biased), digital ocean, etc)

• 
  Kevin Gilbertson (@unigilby) reported 17 minutes ago

  @levelsio We've spent a lot in legal fees going after LaLiga and Telefonica (Movistar). They are the worst. They have a corrupt judge in Barcelona that allows them to block any domain they want. What they did was sue all the ISPs in Spain, which they are closely affiliated with, then none of the ISPs responded, so the judge issued the order allowing them to block any site on the internet. As far as I know they are not blocking all of Cloudflare.

• 
  Daniel Olmedo (@Daniel_Olmedo1) reported 18 minutes ago

  @levelsio Wait what? Spanish founder currently in Spain with sites in Cloudflare. You say they dont work? Never had an issue..!

• 
  christy (@lazarusgpintern) reported 20 minutes ago

  isn’t it ironic that countless amounts of capital and effort poured into agentic payments visa stripe coinbase cloudflare you name it then instinct came along and said **** it we’ll just use human cards

• 
  Camil Blanaru (@camilblanaru) reported 20 minutes ago

  @levelsio Using Orange Fiber in Barcelona and having ~30 sites behind Cloudflare. Never happened to me.

• 
  NickeNumbers (@NickeNumbers) reported 20 minutes ago

  @eastdakota @zatlyn @Cloudflare She is a bad *** 🤘

• 
  ohnwow (@kxmcs) reported 21 minutes ago

  @dump_tcp @Cloudflare Again the argument was never “Golang cannot handle high request outputs” I run multiple companies running on rust and golang, rust is just the superior choice, that is a fact.

• 
  Konan (@konanlives) reported 27 minutes ago

  my biggest problem with v8 isolates is their 128mb memory limit i don’t know if this is a cloudflare thing but i find myself constantly splitting modules into dedicated Durable objects because js is a memory inefficient language

• 
  Ryan K 🌥 (@Yank) reported 29 minutes ago

  @nimanikroo @CloudflareHelp @Cloudflare Live chat is available if you are on the Business plan. It looks like support has been responding but still needs some time to resolve. Let me see if I can get a new update to you.

• 
  Top Stock Alerts (@TopStockAlerts1) reported 30 minutes ago

  JFrog introduced JFrog Traffic Controller, a new product that integrates with Secure Access Service Edge providers such as Zscaler, Cloudflare and Netskope to route software package downloads through JFrog Artifactory, where they are screened for security vulnerabilities, licensing issues and quality before reaching developers. The launch expands JFrog’s software supply-chain security platform into the network layer as malicious packages rise sharply, with company research showing a 451% year-over-year increase to more than 171,000 unique instances. RBC Capital Markets also initiated coverage with an Outperform rating and a $118 price target, citing JFrog’s growing cloud business and its role in software supply-chain security and AI-era development. Q2 revenue rose 29% to $163.8 million, while adjusted EPS of $0.27 beat estimates, prompting the company to raise its full-year revenue outlook to $650 million at the midpoint. $FROG

• 
  Web3Alert (@theweb3alert) reported 31 minutes ago

  Most have heard of x402 by now But most still don't realize the true long term implications of x402 payments. It starts as a Coinbase open sourced payment layer An AI agent hits a paid API... The server returns a 402... The agent pays in stablecoin, retries the request, done. No login. No subscription. No human in the loop. Coinbase built the Base + USDC side. Cloudflare built the edge infrastructure side. Ran it jointly through most of 2025. Fast forward a year and the Linux Foundation officially governs the protocol. As we know, the Linux Foundation is arguably the largest open sourced tech/software firm, so to see them onboard speaks volumes. From here it was no longer just about Coinbase. As of now there are 40+ members within the x402 Foundation under Linux. The 2 DLTs that sit in the Premiere Tier are none other than Ripple and Stellar. Along with this payment giants like Stripe, Mastercard, Circle & Visa are present. Neither Ripple & Stellar nor the other payment giants should be much of a surprise here. This is the future of AI & blockchain meeting payments after all. Arguably the most interesting placement. Quant's Fusion Layer 2.5 supports x402 natively, connects to 70+ networks. That positions Quant as the bridge between agent payments and the regulated banking rails it already sells into. Additionally some other key DLTs that have been integrated are Solana TON Algorand Aptos Hedera Keeta Concordium Casper Injective Cardano What's interesting is that some of these members such as Hedera & Algorand, while they fully support x402... They're not actually part of the foundation. That goes to show just how wide this standard is becoming... It's not just within the foundation. ––––– There's clear alignment here Much of the DLTs integrated here are either mass chains used by many across crypto. Or they're large scaled Enterprise DLT infrastructure that governments, enterprises & more rely on. And when we look at the legacy and non crypto side? We see those same industry giants here.

• 
  Fiducial.ai (@Fiducial_AI) reported 31 minutes ago

  @Cloudflare Rejection reasons need stable, machine-readable codes. That would let operators fix identity or policy failures without guessing which submission field triggered the block.

• 
  Matt Hodgson (@mhodgson2) reported 32 minutes ago

  @steveruizok Install @executorsh in Cloudflare but first path it so a service token can assume your personal identity. Then add all OAuth MCP servers there. Half of them will still break every day but at least you can fix them in one place. All your sessions/harnesses just keep one config with permanent auth. When you re-auth the servers in Executor the sessions can get the fixed connections immediately

• 
  Ryan Ashbrook (@ryanashbrook) reported 32 minutes ago

  @57Revamp @SolTheSauceGod @dinosaurs1969 Could be, but I really doubt that. Cloudflare has their own network and workers so their WAF would work on top of that at edge. Doesn’t really make sense to go out of network > back in network > back out of network in that case. I could be wrong, though. I’m not sure either.

• 
  Mehmet Akcin (@mhmdatx) reported 33 minutes ago

  @levelsio This is the shared-IP problem. Cloudflare fronts millions of hostnames behind the same anycast addresses, so an IP block is a blunt instrument by construction. There is no version of it that only hits the stream. Enforcement belongs at the hostname, not the address.

• 
  Current Events, Sports & Christian Content (@PartesanJournal) reported 35 minutes ago

  @Cloudflare Human Verification System on @X is causing problems

• 
  NoPuppet (@nopuppet) reported 36 minutes ago

  Shibariumscan at ~49% indexed explains why the explorer looks wrecked. It does not explain DefiLlama, you idiot. The explorer is rebuilding its own historical database after the server/Cloudflare migration. That is why the site’s totals collapsed: txs from ~1.56B to a few hundred million, addresses from ~270M to ~80M, blocks cut in half. Those numbers are the explorer UI catching up. The chain is still producing blocks. Missing tokens on the explorer are an index lag, not lost coins. DefiLlama is a different stack. Adapters do not scrape Shibariumscan. They hit protocol contracts over RPC: balanceOf, pair reserves, vault balances. Then they price those tokens. Current TVL is a live contract read, not a replay of the explorer’s search index. So no: Llama is not sitting there waiting for Shibariumscan to finish backfilling 1.56 billion txs before it can see a WoofSwap pool. What can overlap is the infra underneath. Same migration, same RPC endpoints, same flaky nodes. Failed calls can zero a protocol for a tick and make the chart jump. Event/subgraph adapters are more exposed than a simple balance read. That is a node problem, not “the 49% banner is the TVL feed.” Treat those separately. Explorer bar at 49% → explorer stats are incomplete. Llama at ~$31k with ~$0 DEX volume after a ~$120k → $31k drop → look at the pools, and the volume Indexing will restore the explorer’s historical counts. It will not refill liquidity that already left. If the tokens are still in the contracts, balanceOf works at 49%. If they are not, waiting for 100% indexed will not bring the TVL back.

• 
  Cissé ⚡🇧🇯 (@TairouT) reported 41 minutes ago

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

• 
  Jon Klaric (@complex_maths) reported 46 minutes ago

  @dump_tcp @Cloudflare It would just slow down or freeze up every few seconds when the garbage collection cycle kicks in...

• 
  i am jack’s autism (@tylerjharden) reported 46 minutes ago

  @burcs @AndreEduardoPM I have the time and the talent. Make me a @Cloudflare partner / premium support or playbooks and I’ll cook on this 24/7/365 personally and with the clankers & yappers. I remember begging Cloudflare for an API-access product to register/resell domains back in 2019.

• 
  Jeff Escalante (@jescalan) reported 48 minutes ago

  @arturskruze @clerk Really sorry to hear this one. SMS pumping is awful and we put a lot of work and money into preventing it but it still impacts many of our customers unfortunately. Honestly, I recommend now allowing auth via SMS unless you really need to. SMS fraud is very common and perpetrators are relentless. They can inexpensively get through cloudflare turnstile, and will start leveraging other countries even if Italy is blocked 😞 We we try to discount is as much as we are able to, but ultimately we pay the SMS price directly to our own SMS vendors so we have very little wiggle room without us just straight up losing money.

• 
  TKS (@TKS701312296730) reported 51 minutes ago

  @MeltsIcy24536 It's clearly the problem because Cloudflare is trying to explain its reasons for failing. The 'genius' needs to get rid of this moronic verification system that's probably locking more legitimate users out of X than it is 'exterminating' real bots.

• 
  BaoBrawl (@BaoBrawl) reported 51 minutes ago

  @yizhuosol This is an issue on your side. It could be a browser extension blocking known RPC domains, a corporate filter, a regional block, or a Cloudflare limit on your IP. We can’t affect any of these.

• 
  Ajay D'Souza (@ajaydsouza) reported 58 minutes ago

  @MediaRonLLC @cipriangb Better option is to put something like Cloudflare in front of the login. I have a rule that has it under the “under attack” mode for the checks to take place.

• 
  Rob Janssen (@pe1chl) reported 1 hour ago

  @Cloudflare It's a poor craftsman that blames his tools

• 
  Donatello | AI, Tech & Wealth (@donatelloinvest) reported 1 hour ago

  @Cloudflare Performance and security are often treated as separate projects. For a global booking platform, they’re part of the same customer experience. A fast site that fails under pressure isn’t fast. A secure site nobody can use isn’t finished.

• 
  Akhilesh (theboomerang.co) (@akhileshbuilds) reported 1 hour ago

  If your warm-up scores or deliverability stats dropped earlier this month, you likely got caught in a redirect fingerprinting trap. Here is what's happening: Filters no longer judge sending domains in isolation. They follow where they lead. Having 30 lookalike domains all 301-redirecting to one root site creates a footprint only cold outreach fleets produce. Spam engines trace those redirects, link your entire fleet, and tank your reputation in bulk. If you set up new domains or mailboxes around early August, your standard 301 setup is now a liability. Here is how you can test domain masking to combat this: -) Stop raw 301 redirects: Don't hand filters a map of your entire network. -) Mask the destination: Use domain proxies or Cloudflare bot checks so redirect-crawlers can't map the endpoint. -) Isolate front-ends: Give sending domains unique landing pages or isolated DNS layers. The old infrastructure playbooks are expiring fast. If deliverability dropped recently, check your redirect map first. P.S. If you spun up domains this month, did your warm-up numbers feel off?