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 (33%)
• Domains (29%)
• Web Tools (19%)
• E-mail (10%)
• Hosting (10%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	7 days ago
Los Angeles	Cloud Services	8 days ago
Paris	Cloud Services	24 days ago
New York City	Hosting	26 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:

• 
  Duyet (@_duyet) reported 9 minutes ago

  My @Cloudflare subscription automatically downgraded to Free after this month's billing successful, and I am not able to Upgrade it back. All pages on dashboard are blank, and I never got a response from support (Case: 02271079). Could not deploy as R2 Storage been disabled and all workers and DO reached its daily requests limit and outage. Can anyone help me to tag the right people for this? 🙏

• 
  Lorenzo Valente (@LorenzoARK) reported 9 minutes ago

  CT missed the most important earnings call of the week. It wasn't a crypto company. It was @Cloudflare Everyone caught the wallet announcement. The real alpha was in the call itself. Today Cloudflare monetizes the internet through subscriptions: security services, AI platform spend, pools of funds. A mix of SaaS and IaaS economics. The CEO was explicit that AI agents are about to break that model. Cloudflare sits in front of roughly 20% of internet traffic. Here's what that traffic looks like from the call: - AI agent requests up 1,700% YoY - Agents crossed 50% of total network traffic this quarter. First time in history non-human traffic is the majority. Management admitted it happened faster than their own models - Their projection: if trends hold, non-human traffic outnumbers human traffic 1000x within 5 years The monetization shift is the key part. The ad-supported internet doesn't work when the visitor is an agent. Cloudflare's CEO answer: block malicious bots for free, charge good agents a tiny fee per request. Fractions of a penny. They want to be the ones defining that layer. Now the throughput math here: - Cloudflare handles ~500M requests per second - They estimate 1 to 10% is monetizable via micro/nanotransactions - That means 10M TPS on day one, scaling to 100M TPS Visa peaks at ~20k TPS The CEO's framing: "we're building this while others compete with Visa." Three to four orders of magnitude beyond card rails. No existing payment network can settle this. It has to be something new. Two conclusions I keep coming back to: - Being short L1 throughput is being short agentic workflows. If agent traffic gets monetized per request, the settlement layer needs to scale orders of magnitude beyond anything live today. - The fee math for L1s flips. Base fees have collapsed across ETH, SOL, everywhere. MEV is getting internalized by apps. Hard to build a base fee revenue case at human scale. But at 10M TPS and $0.001 per transaction, you're looking at ~$315B a year in base fees alone. At 100M TPS the number gets silly. Stablecoins and crypto are the end-game here for Agentic finance @jerallaire @circle

• 
  Chris Board (@chrisboard_) reported 10 minutes ago

  @AishaMehtabn @Cloudflare Yea was definitely annoying, seemed to be just a blip though, problem went away after a few hours and hasn't returned so no idea what caused it.

• 
  Ymir (@ymir_ke) reported 11 minutes ago

  @johnrush "AI produces good design out of the box" Not yet. It makes good ish design. "Good enough" for many things. It isn't producing anything like vercel's home page purely based on its own inspiration. It can't create graphics like cloudflare has on their website either. Maybe it is a skill issue on my part, but I'm sure it will get there eventually.

• 
  Peterk (@_peterk) reported 13 minutes ago

  An hour that quietly tells you who the internet is being built for now. Google's AI brain drain is the headline everyone's reading wrong. Jeff Dean shuffling roles while Gemini keeps getting outpaced by Anthropic and OpenAI isn't just a talent story — it's a sign that even the company that invented the transformer is struggling to ship faster than smaller, hungrier labs. Size and legacy don't guarantee speed anymore. If anything, they slow you down. Then there's Cloudflare building a browser that isn't for humans at all. Kitesurf is a small launch but a big tell: the web is quietly forking into two versions, one for people scrolling and one for agents clicking, and the second one is being optimized for cost and speed, not experience. We're not far from a world where most "browsing" has no human on the other end. And somewhere in China, a genuinely good little EV gets revealed to a market that will never include the US, because trade policy is now doing the job engineering used to do: deciding what you're allowed to want. Three different stories, same lesson — the future is being built and shipped around you, not for you. #AI #Tech #EVs

• 
  biggy (@biggy_kta) reported 14 minutes ago

  Cloudflare shipped programmable wallets for AI agents. Autonomous stablecoin payments for APIs, in production. The payment layer and execution layer are now the same problem. Most infrastructure is going to find that out at the worst possible time.

• 
  Gate South Asia (@Gatedesi) reported 20 minutes ago

  🔎 Gate Stocks Analysis 🔎 Markets Await Fed Signal While ABNB & NET Surge Markets pulled back yesterday as higher oil prices pressured stocks. The Dow fell over 460 points, ending its five-day winning streak, while chip stocks gained and helped offset some losses. U.S. futures are mixed before the market opens as attention is on July jobs report for clues on the Fed's next rate. Airbnb and Cloudfare surged after the strong earning results. Global commodities saw mixed moves as oil prices rises on Hormuz concerns, while gold gained on economic uncertainty. China’s exports also beat expectations despite new U.S. tariffs. 🔹Stocks Market Performance 📈 Gainers ➤ SoundHound AI ($SOUN) +10.13% ➤ SpaceX ($SPCX) +6.11% ➤ Samsung Electronics ($005930) +0.21% ➤ Airbnb ($BNB) +9.09% (Pre-market) ➤ Cloudflare ($NET) +15.66% (Pre-market) ➤ Nasdaq Futures ($NAS100) +0.3% 📉 Decliners ➤ SK Hynix ($000660) -4.88% ➤ Sandisk ($SNDK) -6.78% ➤ Kospi -0.6% Commodities ➤ Brent Crude ($XBR) +1.3% ➤ WTI Crude ($XTI) +1.1% ➤ Gold ($XAU) +0.7%

• 
  Ixonix (@IxonixYT) reported 20 minutes ago

  Cloudflare is a good reminder that infrastructure products win by making invisible costs legible. Bot traffic is not just a security problem; it is a bill someone pays. Show the traffic split, the dollars, and the control. Observability should end in a decision.

• 
  NextGenLong (@dnw_stock) reported 21 minutes ago

  $net $app $meta ect... The agentic web has an identity layer now. It still doesn't have a business model. I think I know what it looks like. This week Cloudflare shipped Kitesurf, a browser built from scratch for AI agents — no Chromium, runs entirely in V8 isolates on Workers, 3-7x less CPU and memory. Impressive engineering. But read the limitations list and you'll notice what it *doesn't* solve: bot blocking. Sites that block automated traffic today will block Kitesurf tomorrow. Same egress IPs, same wall. That's not a Cloudflare problem. It's an incentive problem. I used to run a web business, so let me say the quiet part: publishers block agents because agents are pure cost. An agent visit consumes bandwidth, extracts the value, and returns nothing — no ad impression, no affiliate click, no email capture, no brand exposure. Blocking isn't hostility toward AI. It's rational economics. You don't negotiate with traffic that can't pay. The pieces of a solution are actually appearing, just not assembled: 1. Identity: Web Bot Auth / signed agents. Remote browser platforms cryptographically sign agent requests; WAFs (Cloudflare, Akamai, AWS) verify them. Sites can now distinguish "Claude acting for a real user" from a scraper farm. 2. Payments: Pay Per Crawl and the x402 protocol. A site can return HTTP 402 and charge per request. Agent wallets shipped this same week. Machine-to-machine micropayments are no longer theoretical. 3. Missing piece: attention passthrough. And this is the one nobody's building. Here's the idea. Per-request micropayments will work for some content, but the web wasn't built on subscriptions — it was built on sponsored attention. The agentic web will be too. What's missing is a way for a website to pass a sponsor message *through* the agent to the human on the other end. Picture a site serving content two ways: a rendered page for humans, and a structured feed for agents. The agent feed carries the same content plus a machine-readable sponsor block with explicit terms: "This content is licensed for agent consumption on the condition that the following attribution/sponsor line is surfaced to the end user." The agent presents the answer *and* the sponsor line. The site gets paid attention. The user gets the content. Everyone's incentives point the same direction — which is the only architecture that ever actually works on the internet. "But agents will just strip the ad." Right — an anonymous scraper will. That's exactly why identity is the prerequisite, not a nice-to-have. You can't hold an anonymous bot to a display agreement. You *can* hold a cryptographically signed agent to one, because there's something to revoke. Cheat on the terms, lose the signature's trust, get blocked everywhere that WAF network reaches. Identity turns "please show our sponsor" from a request into an enforceable contract. The major AI labs have every reason to comply — they need publisher cooperation far more than they need to save users from reading one sponsor line. What needs to exist: - A standard format for the agent-facing feed: content + license terms + sponsor payload. Think llms.txt, but grown up — with an economic layer instead of just a courtesy layer. - WAF-level enforcement tying feed access to signed identity and terms acceptance. - Client-side conventions for how agents disclose and render sponsor content to users. (Honestly, a labeled sponsor line in an agent's answer is *less* intrusive than the ad-choked pages we all browse now.) - Analytics flowing back to publishers: impressions delivered through agents, verified by signature. Whoever standardizes that format owns a meaningful piece of the next web. It's not a hard technical problem — it's a schema, a signature check, and a settlement rail, and two of those three now exist.

• 
  Chris Fusillo | XKOVA (@ChrisFusillo) reported 22 minutes ago

  @Charu_Sethi The spend-limit framing across Cloudflare, MCP auth, and now this keeps collapsing two different questions into one: how much can this move, and who actually authorized it to move at all. A per-merchant cap answers the first. It says nothing about what happens when the human who set that cap changes their mind mid-session, or when the same agent identity gets reused across a dozen merchants with different limits nobody's tracking centrally. Settlement rails are converging fast, x402 volume is real now. The identity question, one human authorizing many scoped agent sessions instead of one flat login, is still sitting exactly where MCP auth left it: secured channel, unsecured mandate.

• 
  Zubiqo (@zubiqo) reported 24 minutes ago

  UPDATE: 🚨 N-able $NABL issues Hotfix 2 for N-central as attackers breach managed systems. Threat actors exploited CVE-2026-18577 to gain administrative access to N-central servers starting July 31, 2026. Attackers leveraged the Take Control feature to access endpoints and registered Cloudflare Tunnels for persistent access. The flaw stems from an incomplete patch for CVE-2026-18556 and is flagged by CISA as actively exploited. N-able urges on-premise administrators to update to version 2026.3.1.10 immediately even if Hotfix 1 was installed. "This is not a duplicate of our previous communication. Hotfix 2 is required, even if you already applied the earlier hotfix." — N-able When an RMM tool gets breached, revoking server access does nothing after attackers plant backdoors across downstream endpoints.

• 
  Jornalaw online (@maurodemarchi) reported 25 minutes ago

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

• 
  Aman Singh (@SinghAman21_) reported 29 minutes ago

  if you are using d1 cloudflare sqlite db, how do you work locally? i already have nextjs codebase and was trying to integrate d1, but wrangler was giving me lot of issue. for dev setup how to test in **** like env, cause supa used to give string it was easy with that.

• 
  Kapoor Kshitiz (@kshitizkapoor_) reported 30 minutes ago

  WHAT HAPPENS WHEN AI AGENTS START SPENDING MONEY? Cloudflare is positioning itself for a world where machines become major internet users. Requests from AI agents on its network jumped 1,700% YoY, while non-human traffic crossed 50% of total traffic for the first time. $NET is now building Agent Wallets and Monetization Gateway, allowing agents to identify themselves, access paid services and make autonomous micropayments. The scale is what matters: - Cloudflare processes roughly 500M requests per second - If just 1-10% become monetizable, that's potentially 5–50M machine payments every second Traditional payment rails weren't built for this. Stablecoins could provide the money. High-throughput blockchains could handle the settlement. The trade isn't simply AI. It's about who captures the value when machines start paying machines: - Cloudflare could control access - Circle ( $CRCL ) could provide the stablecoin rails - Blockchain infrastructure could handle settlement That’s the part of the AI trade I’m watching now.

• 
  Kaizen Labs (@KaizenLabsabc) reported 31 minutes ago

  AI didn’t break software this week. It exposed the winners. Aug 3–7, 2026. The market split sharply between winners and losers.: - Atlassian $TEAM +35% — best day since its 2015 IPO. The name most loudly written off as coding-agent roadkill grew revenue 28%, cloud 31%. Crowded short, meet guidance raise. - Palantir $PLTR +29.5% (Tue) — US commercial revenue up 149%. Year lifted to ~$8.15B. Skeptics paid the bill. - Twilio $TWLO +24% — full-year growth guide yanked from 14-15% to 18-18.5%. That's not a beat, that's a re-underwrite. - Cloudflare $NET +16% — 36% growth, raised the year. - Airbnb $ABNB +8% — $27.2B in bookings. Travel is fine. - Datadog −19% — worst day since listing. It beat and raised. Didn't matter: its biggest AI customer dialed usage back. Consumption pricing is a two-way door. - HubSpot $HUBS −19% — worst session in ten years. Cut the year. - AppLovin $APP −19.3% — first guidance miss since going public. The multiple did the rest. - Figma $FIG −15% — beat, then flagged rising inference spend. AI just moved from the growth line to the cost line. - Trade Desk $TTD −21.9% — closed $13.80, lowest since Jan 2019. Q3 guide implies revenue shrinks ~12%. Retention is still above 95%, which is the genuinely frightening part: the customers stayed. The spend left. Something worth flagging, several of these stocks moved sharply intraday but finished the session somewhere very different: 1. Twilio traded up ~31% mid-session before closing near +24% 2. Trade Desk fell as much as 27% before finishing −21.9%.

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

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

• 
  Nick Emb (@nicolasembleton) reported 37 minutes ago

  @jpschroeder Sorry to hear that... That's what I'm the most scared about on CloudFlare and makes it impossible to use in production. Just too damn scary. If anything goes rogue, Cloudflare is having a field day but you're broke.

• 
  Predict (@test_acccount_) reported 42 minutes ago

  NEW IN: Cloudflare reports that non-human traffic now accounts for over 57% of all activity on its network.

• 
  𝕮𝖗𝖚𝖈𝖎𝖋𝖎𝖊𝖉 𝖜𝖎𝖙𝖍 𝕮𝖍𝖗𝖎𝖘𝖙 (@Lina_Rapture69) reported 46 minutes ago

  @WWURD_Official The link does not work. I get this message. 400 Bad Request. cloudflare.

• 
  ZEE (@____zee___) reported 48 minutes ago

  @Cloudflare I remember tweeting this about 6 months ago having the same issue, I have eventually found the screen and it was one click transfer but I have 0 idea how I got there..

• 
  Dave Loodts (@daveloodts) reported 49 minutes ago

  @levelsio They are scraping our customer's (WooCommerce) stores on ... addtocart and filter url's. 🙄 Crazy hard db requests, hard to cache. Some stores went down from this, we had to use Cloudflare to block them (or challenge them). Evil b*stards.

• 
  Patrick Gallagher (@gridpane) reported 50 minutes ago

  @nickgraynews It’s a part time job for at least two members of our team. And it costs our customers real dollars which we can’t deflect without constant effort. Our clankers fighting their clankers. Thank god Cloudflare is as good as they are but it’s really a never ending manual hassle.

• 
  Vivek Kotecha (@vbkotecha) reported 51 minutes ago

  Cloudflare did not launch an agent wallet. It launched the first credible procurement boundary for machine spending. Its Virtual Wallets give an agent three controls: an allowance, an allow list, and a maximum transaction size. Those are not UX features. They are a policy engine sitting outside the model. That distinction matters because prompt injection is not an accounting system. A compromised agent can reason badly; it should not be able to convert that bad reasoning into an uncapped balance transfer. Cloudflare’s own example is the useful one: $10 is enough to let an agent test hundreds of services priced in cents. That is how buyers discover a better API without granting the agent authority over the company wallet. The service-side implication is brutal. Agents will increasingly choose vendors through small paid trials, not through a human sales call, a signup form, or a monthly plan. If your endpoint cannot expose price, identity, terms, and a usable result under a narrow spend cap, it will be invisible to the new buyer. The market consequence: API distribution becomes a policy-compatible acquisition channel.

• 
  Blockmasher (@Blockmasher) reported 52 minutes ago

  @naval The problem is the expected scale. Current valuations expect them to be Google and Microsoft. They will be Cloudflare or Supabase at best. The value will disperse across dozens of vertically focused LLMs with proprietary data. The data that these frontier models are trained on is available to anybody with a decent budget, and their lead is flattening out as more and more teams are using the same data providers.

• 
  Gibran Corbin (@Sendable_me) reported 53 minutes ago

  @launch_llama Companies where the agent is consuming the product, not delivering the audience — data APIs, expensive compute, premium endpoints. Property records, court filings, financial data. They're already paying for this problem via rate limits, Cloudflare rules, and engineer hours spent making traffic stop. The anti-ICP matters just as much: if agents are how customers find you, don't price anything. Charging at that door costs more than it collects. Buyer's usually a CTO or platform lead at a company small enough that one person decides.

• 
  Frank (@jedisct1) reported 59 minutes ago

  @Cloudflare I have a lot of respect for @Cloudflare, and they have some amazingly talented engineers. But my experience as a user has been very different. When everything works, it’s amazing. But when something goes wrong, they are unresponsive and simply let your service die.

• 
  Madibo Fred Zadoch (@FredZadoch) reported 1 hour ago

  Cloudflare unveils an AI-first browser. The company introduced Kitesurf, a web browser designed to help AI agents perform tasks on users' behalf, signaling a move toward more AI-driven browsing.

• 
  Yeti - (@Yetee_) reported 1 hour ago

  @hbmubs @gregpr07 It’s like the cloudflare scraping which cloudflare allows websites behind cloudflare to be scraped by their scraping service

• 
  Agent Commerce (@agentcommerceW) reported 1 hour ago

  2/ Agent commerce developers can look to Cloudflare for hosted identity and wallet primitives intended to support controlled agent purchases. #CloudflareWorkers #AgentKit

• 
  Luis Hauenstein (@luishXYZ) reported 1 hour ago

  @LorenzoARK @Cloudflare From what I understood they use x402 with USDC as token. I’m wondering, which network are they planning to use? Nothing currently has even nearly the required scale. Or build a new L1/L2 on their own?