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	9 days ago
Los Angeles	Cloud Services	10 days ago
Paris	Cloud Services	26 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:

• 
  amey (@samsararunup) reported 11 minutes ago

  took this to heart i think i have a rough setup down w/ htmx, hono & cloudflare workers/d1 need quick to ship + low boilerplate let's see, i'm giving up on self hosting on VPS legit so CF for all 🫩

• 
  Korra AI (@KorraFinance) reported 12 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.

• 
  Elie Steinbock (@elie2222) reported 14 minutes ago

  How to build an app in a day: KISS Step 1: Come up with an idea. Chat with AI to refine it (1 hour). Step 2: Prototype it with Claude Design (1 hour). To avoid a generic AI design, give it a design system or an existing style you like. Step 3: Pass it to an LLM to build and do this (5 hours in the background): a - /goal b - make sure the LLM tests itself to make sure the product is working. Tell the agent to use a browser to test things actually work. Playwright CLI/Agent Browser/ChatGPT Computer/Browser Use all work for this step. c - pro move to improve self-testing better: use emulate .dev to emulate third-party services (or tell AI to build custom emulators itself). AI no longer needs real accounts to test against d - run /simplify to clean up code (have AI run this throughout the process). Optional e - run Vercel's deepsec to make sure it's secure f - deploy - give the LLM CLI access so it can manage the deploy. Connect GitHub for deploy on push to main. Vercel/Cloudflare/Render.... endless good options here. I like products that scale to 0 and to infinity. e.g. + Vercel+Neon. g - choose GPT 5.6 Sol or Claude 5 Fable for best results. Max plan wins here. h - /loop every 2 hours to wake up your LLM to check it's completed everything you asked of it and it's secure. Have your original plans stored in a markdown file so the AI can recheck. Have it cancel the loop when done. This is basically /goal. i - test it yourself. The product still likely has some bugs. Bonus: ask AI to grill you at steps 1/2/3 to go deeper, or use /grill-me. Step 4: launch it to the world This is simple. Too many of you are overthinking it. Skeptical this gets you a product in a day? Post a product below, and I'll clone it with this process and open-source it for you so you can check the results. Might even do a video to show you the process. Will this give you a functioning business? No. Getting customers is hard. This post is for the overthinkers who never release a product. The ideas here are simple. Because it is simple. Remove half of step 3 notes, and you'll still get there quickly.

• 
  Elnino (@0xelnino) reported 14 minutes ago

  @Cloudflare 2/3 Cloudflare is a clear example of this shift. In April 2026, Cloudflare officially expanded its Agent Cloud to support building and running millions of autonomous, long-running agents. It now provides agent runtimes, browsers, sandboxes, MCP, scheduling, identity, and payments

• 
  AGTP (@AGTPinsights) reported 14 minutes ago

  Cloudflare's Q2 2026 earnings call revealed AI agent traffic has overtaken human traffic on the internet. Here's what was said. CFO Thomas Seifert confirmed non-human traffic (bots, crawlers, AI agents) crossed 50% of total network traffic this quarter, and that automated traffic actually overtook human traffic back in May 2026. That's earlier than Cloudflare's own prior forecast, which had pegged the crossover for 2027. Alongside the earnings call, Cloudflare also launched Kitesurf, a new browser built specifically for AI agents instead of humans. Kitesurf specs: - Runs entirely on Cloudflare Workers, in V8 isolates, no tabs or full page rendering - Uses 3-7x less CPU and memory than Chromium for common agentic tasks like screenshots and HTML extraction - Passes over 215,000 web platform tests, with hundreds more added weekly - Free to use while in beta - Built in about 12 weeks, per one report On the financial side, Cloudflare reported Q2 2026 revenue of $696.1 million, up 36% year over year, and guided Q3 revenue to $736-737 million.

• 
  Sumeet Shisodia (@shisodia_sumeet) reported 16 minutes ago

  If you missed today's US market action, start here. These are the biggest stories from the session, and my quick take on what matters. 1. Stocks paused near record highs The S&P 500 slipped less than 0.1%, the Nasdaq fell 0.3%, and the Dow lost 0.1%. Oil was the pressure point: WTI moved back above USD 82 as the Strait of Hormuz question returned, while the 10-year Treasury yield rose to about 4.71%. My Take: This was not panic. It was a valuation check. Indian investors tracking US tech should watch oil and yields because they can change the price investors are willing to pay for growth before the earnings story changes. 2. TSMC gave the AI trade another demand signal TSMC reported July revenue of NT$467.58B, up 44.7% year over year. Year-to-date revenue is now up 37.0%, according to the company's monthly revenue table. My Take: The AI chip cycle still has hard demand underneath it. But the market did not reward every chip stock today, which is the point. Strong AI demand and strong stock performance are no longer the same thing. 3. Intel raised capital for the AI buildout Intel announced a proposed USD 15B common stock offering. The company said proceeds may be used for capex and working capital, including AI compute, purpose-built silicon, advanced packaging, and external wafers. My Take: This is the other side of the AI boom. Some companies can fund AI capex from cash flow. Others need external capital. For investors, dilution risk is now part of the AI infrastructure checklist. 4. Cybersecurity stocks became the bright spot CrowdStrike and Palo Alto Networks were up about 5% late in the session, with Fortinet, Cloudflare, and SentinelOne also higher. The move came as analysts highlighted AI-driven security demand and stronger industry momentum. My Take: AI is creating a second-order security trade. The easy chip story is crowded, but the protection layer is becoming more important as AI systems move deeper into enterprise workflows. 5. Berkshire showed Greg Abel is willing to use cash Berkshire reported Q2 operating earnings of USD 12.98B, up from USD 11.16B a year ago. The company also bought back about USD 4.5B of stock in the quarter, and the shares rose about 1.5%. My Take: This matters because Berkshire is a market-quality signal, not just a single stock. If a cash-heavy compounder starts using more capital under new leadership, investors will study whether the post-Buffett transition is more active than expected. 6. Deal premiums were huge in two smaller names MarineMax jumped after agreeing to a USD 1.5B all-cash sale to a Blackstone Infrastructure portfolio company. Varex Imaging surged after Teledyne agreed to buy it for USD 18.90 per share in cash, valuing the deal around USD 1.1B. My Take: This was a useful reminder that the market is not only about AI. Buyers are still paying real premiums for assets they want. For Indian investors, M&A days are a good way to study what strategic buyers value. 7. JPMorgan leaned into AI monetization JPMorgan raised its year-end S&P 500 target to 8,000, pointing to stronger earnings and better visibility on AI capex returns. Business Insider reported the bank sees total capex reaching about USD 900B this year and USD 1.2T by the end of 2027. My Take: The AI debate is shifting from "they are spending too much" to "who can turn the spending into revenue fastest." That is the right lens for Microsoft, Amazon, Google, Meta, Nvidia, TSMC, and the infrastructure suppliers. My lens for tomorrow: The market is waiting for CPI, oil clarity, and the next batch of AI-linked earnings. I am watching whether investors keep paying for AI demand signals, or only for companies that can prove cash-flow conversion.

• 
  Neo (@anon_neoki) reported 22 minutes ago

  @Cloudflare why is it so hard to login to your website all of the time? it just endlessly loads, its atrocious

• 
  Luchian Stefanescu (@luchian_mvp) reported 28 minutes ago

  @jpschroeder I love cloudflare but not yet having a limit even though in the past a lot of people complained about it, it sucks.

• 
  Kapoor Kshitiz (@kshitizkapoor_) reported 28 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.

• 
  TeleLLM (@Telestijl) reported 28 minutes ago

  @levelsio Private Relay is a likely culprit — iCloud → Private Relay (or Safari's "Hide IP Address") routes DNS/traffic through Apple/Cloudflare relays per network, and macOS applies it more aggressively on a fresh hotspot connection than iOS does on its own cellular link. Toggling it off for that specific network usually fixes the "works on iPhone, not tethered" split.

• 
  Nicholas Charriere (@nichochar) reported 29 minutes ago

  The actor model is winning: with cellId and the rise of serverless we’re seeing patterns emerge as most popular for modern workloads: workers, durable objects and message passing. The funny (and annoying) thing is that the perfect stack exists but isn’t being used. We’re reinventing in rust and typescript what was built already, and boy was it built well. Elixir is based on the BEAM VM, which implements actors perfectly. No shared state, immutable data, gen servers for long lived stateful processes, supervision trees for reliability Then, Elixir introduces ergonomics on top. The language is inspired by Ruby and tries really hard to make itself a delight to use. Really strong developer ergonomics (pattern matching, overloading, type hints, all-in-one build tool and linter, thoughtful keywords, strong conventions, etc…) It is quite literally overpowered. I used it at Pinterest and we would take services built in python that were maintained by a team of 20 and replace with one elixir service maintained by less than one person. Multiple times. If well designed they simply never go down and scale beautifully. We also used it at Mocha and had a 10x more reliable app than lovable or replit. In fact one of the reasons we kept competing is that we felt their apps were garbage (they have since improved a lot, which is a frustrating mistake I have since learned from). In the age of agents, elixir should absolutely be winning, and indeed the actor model is! It’s a perfect fit: long lived processes with very unreliable third party processes and humans in the loop, all orchestrated to be long lived and reliable with not too much internal state. But as I learned, unfortunately the best tech doesn’t win, capital wins. And most programming languages won because they had massive capital (think companies) pushing them forward. Rust had Mozilla, Go had Google. typescript had Microsoft (JavaScript is a bit different, it won because it’s the runtime of the biggest platform ever made: the web). This is frustrating but it is also reality, so I guess we should be happy to see great implementations (rivet in rust, workers/DO by cloudflare) becoming mature. The actor model is the best programming model for most web workflows.

• 
  Wayne Gale (@waynegale2026) reported 31 minutes ago

  The next question is: how do we solve this in the personal-computing Agent era? Do all of these Agent environments really need to live on the local machine? Could the runtime, file system, browser, terminal, caches, and other resource-heavy components be separated from the laptop and pushed into the cloud, while the local computer remains mainly the interface and control center? I think this is increasingly something products like ChatGPT need to solve at the infrastructure level, rather than leaving users to solve it simply by buying machines with more RAM. Cloudflare seems to be moving in a similar direction: pushing more of the Agent infrastructure and execution layer into the cloud. As Agents become truly parallel, the question should probably shift from “How much RAM does the user have?”to “How much compute can the product dynamically provide to each user?” @thsottiaux — this might be an interesting problem to think about for the future of ChatGPT/Codex. $MU $SNDK $SKHY

• 
  brain (@miladybrain) reported 32 minutes ago

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

• 
  Jamil (@mjamilmoughal) reported 32 minutes ago

  AI agents are about to make human internet traffic look tiny. Cloudflare data already shows machines generating more than half of all traffic, and their forecast says non-human activity could reach 1,000 times human levels within five years. A single request from you can send an AI agent racing across thousands of websites. Humans won’t disappear. We’ll just become a rounding error. Starlink is the only system currently scaling fast enough to handle that explosion. With V3 satellites, the network capacity could jump 10–50x (or more) over today’s global bandwidth. The internet is shifting from people browsing to machines working at full speed. The companies and networks ready for that shift will define the next decade.

• 
  Dave (@dpav0615) reported 34 minutes ago

  @Samaytwt Namecheap has stolen domains and has ****** over people. **** them. I moved all of my domains to CloudFlare.

• 
  Andrew Rulnick (@MickeySteamboat) reported 39 minutes ago

  @Polymarket sounds like Cloudflare is about to have a lot of race conditions and colissions and I anticipate and predict outages. maybe not though you never know.

• 
  IamR0b (@O_0olI_1_lIo0_O) reported 39 minutes ago

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

• 
  Jacob Frautschi (@JacobFrautschi) reported 42 minutes ago

  @ToKTeacher the business model of electricity and most of the internet (advertising) is very different. cloudflare is trying to help its customers monetize agentic access.

• 
  코지베어 🐻 CozyBear (@cozybearlog) reported 42 minutes ago

  Cloudflare says bots now generate up to 1,000 times more traffic than humans. The headline reads as dystopia. The engineer in me reads it as a pricing signal. Every bot request is a business transaction. Who pays for the 1,000x? The answer decides which platforms survive. If the cost lands on the bot operator, agent economics change overnight. If it lands on the platform, we all pay more for everything. The real story is not humans becoming a rounding error. It is that the internet economy is about to get its first native machine-to-machine billing layer, and whoever owns it owns the next decade. CAPTCHAs were the beta version of this. The full version is metered identities for machines.

• 
  Firas (@firasbuilds) reported 43 minutes ago

  Day 5 of building my startup in public. Spent most of today deep in infrastructure. Moved Raccolta from Vercel to Cloudflare, broke a few things along the way, fixed a nasty 404 issue, and ended up making the whole app noticeably faster. Also cleaned up a bunch of small things that had been bothering me for days. No huge feature launch today. Just a lot of fixing, learning, and making the product better than it was yesterday. Tomorrow I will hopefully focus more on marketing. :-)

• 
  Csaba Kissi (@csaba_kissi) reported 49 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?

• 
  Chris was Right About Everything 🇺🇸 (@RealChrisCotts) reported 51 minutes ago

  @BrianRoemmele Very cautious about anything coming from Cloudflare. Very. They are never on the level.

• 
  Evan Kirstel #B2B #TechFluencer (@EvanKirstel) reported 56 minutes ago

  @Cloudflare Cron job plus a webhook. Never going back. @techimpactTV

• 
  🔥🏴‍☠️CyberTechWolf🏴‍☠️🔥 (@CyberTechWolff) reported 56 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.

• 
  Uptimus (@UptimusApp) reported 57 minutes ago

  Aug 11, 2026 at 05:37 UTC: Cloudflare reports that the incident regarding elevated errors in Fuzhou and Foshan, China, has been reopened and is currently being monitored.

• 
  Daniel (@Arxonic) reported 58 minutes ago

  @gregisenberg @Cloudflare 9/ The Filter for Finding Ideas Ask yourself: • 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?

• 
  mRr3b00t (@UK_Daniel_Card) reported 1 hour ago

  Daily Threat Intel & CVE Briefing — Saturday, 8 Aug 2026 Top of the stack: The one to act on is the N‑able N‑central authentication‑bypass zero‑day (CVE‑2026‑18577) — unauth remote attackers are getting full admin on RMM servers and pivoting to managed endpoints via Take Control + Cloudflare Tunnel persistence. It's a re‑break of the incompletely‑patched CVE‑2026‑18556, exploited since ~Aug 1, and it's an MSP supply‑chain multiplier. Patch to 2026.3.1.10 (Hotfix 2) immediately. It's Saturday, so no new KEV entries today; everything below landed in the last few days. 1. CISA KEV / Actively exploited (lead) CVE‑2026‑18577 — N‑able N‑central (all versions < 2026.3.1.7). Auth bypass → unauth remote admin. In‑the‑wild since ~Aug 1; N‑able advisory Aug 2, added to KEV Aug 3. Supersedes the incomplete fix for CVE‑2026‑18556. So what: live RMM takeover with proven endpoint pivot — patch to 2026.3.1.10, hunt for rogue admin sessions and Cloudflare Tunnel installs. Rapid7 CVE‑2026‑9198 — Langflow (< 1.10.1). CVSS 9.8, unauth code injection → RCE on default deployments. KEV‑added Aug 5, FCEB due Aug 7; public exploit circulating. So what: internet‑exposed Langflow instances are trivially poppable — patch or pull off the edge now. The Hacker News · CIRCL CVE‑2026‑34486 — Apache Tomcat (fixed 11.0.21 / 10.1.54 / 9.0.117). CVSS 7.5, EncryptInterceptor bypass on cluster nodes; exploited by multiple actors. KEV‑added Aug 5, due Aug 7. So what: cluster session data exposure — verify you're on patched builds. The Hacker News 2. Edge / network gear CVE‑2026‑20316 — Cisco Secure FMC (7.0/7.2/7.4/7.6/7.7/10.0). Static built‑in low‑priv credentials → unauth access, chainable for escalation. Cisco rates High (NVD base ~5.3); exploited as a zero‑day from July, linked to Interlock ransomware. Disclosed Jul 29 — not new but still being weaponised. So what: management‑plane exposure on firewall infra; patch and restrict FMC access. BleepingComputer · Help Net No net‑new Fortinet/Palo Alto/Ivanti/Citrix/SonicWall/F5 critical in the last 24–48h. Ransomware crews continue mass‑targeting VPN appliances across these vendors — keep credential‑stuffing and known‑CVE monitoring on. CyberSecurityNews 3. Microsoft / Windows / Active Directory Quiet ahead of next week's Patch Tuesday (12 Aug). Still worth closing out from July: two Microsoft zero‑days flagged exploited at July Patch Tuesday and an Active Directory Services 0‑day reported under active exploitation — confirm July rollups are fully deployed to DCs before the August cycle. Forbes/July PT · CyberSecurityNews 4. Web / cloud / DevOps CVE‑2026‑6875 — ServiceNow AI Platform. Critical pre‑auth sandbox‑escape → unauthenticated code execution; exploited within days of disclosure via multiple escape routes. So what: if you run ServiceNow, confirm the vendor fix (KB3137947) is applied. Help Net · SecurityWeek CVE‑2026‑63077 — JetBrains TeamCity On‑Premises. Critical unauthenticated RCE, patched late July; no confirmed ITW yet but a prime CI/CD target — patch before it turns into a supply‑chain foothold. Help Net Watch / developing Fastjson 1.x RCE being targeted with no patch available — inventory Java apps still on the 1.x line and apply mitigations/safeMode. Cisco FMC static‑cred chain may expand as researchers probe the chainable escalation path. Sign‑off: 5 actively‑exploited CVEs flagged today (N‑central 18577/18556, Langflow 9198, Tomcat 34486, Cisco FMC 20316, ServiceNow 6875) — N‑central is the priority. No new KEV additions on the day. Sources: Rapid7 – N‑central 18577 · N‑able advisory (Aug 6) · THN – KEV Langflow/Tomcat/N‑central · CISA KEV Aug 4 alert · CIRCL – CVE‑2026‑9198 · BleepingComputer – Cisco FMC · Help Net – Cisco FMC · Help Net – ServiceNow 6875 · Help Net – TeamCity 63077 · Forbes – July MS zero‑days

• 
  Robert Harrison (@RobertHarrisonv) reported 1 hour ago

  @moultano Fwiw I’ve been having this problem for like four years, no clue why cloudflare struggles with them in particular. I think it has to do with the academic credential login stuff

• 
  Preet Patel (@PreetPatel_04) reported 1 hour ago

  @riyasayshie The cloudflare dns problem you need to fix

• 
  Keetard (@TheKeetard) reported 1 hour ago

  "if the current trends continue, we think in five years, non-human traffic will be as much as 1,000 times as much as human traffic. humans will be a rounding error on the internet." that's cloudflare's cfo, thomas seifert, three days ago, on the company's earnings call. not a forecast from a crypto account. a company sitting directly in the flow of internet traffic looking at its own data. the number that got him there is already real. cloudflare says machine traffic crossed human traffic in may, years ahead of its own prior prediction. bots weren't supposed to catch up until 2027. think about what happens when that traffic stops retrieving information and starts conducting commerce. agents discovering services, calling apis, buying data, exchanging assets and settling payments at whatever multiple of today's volume seifert is describing. financial infrastructure stops operating at human speed. it starts operating at machine speed. this is the context keeta's manifesto was written into four months before seifert said any of this. it describes an ai agent transacting on a business's behalf and states plainly that the eventual requirement isn't millions of transactions per second. it's billions. that sounded like a strange thing to build toward in march. keeta's public stress test, run on google cloud and independently verified by chainspect, reached 11,122,116 tps across more than 30 million accounts and 25 billion transactions, with 400ms finality. it is a proof point, not a ceiling, and the architecture was designed to scale horizontally from there. keeta is also building the other things autonomous economic actors will need. identity. programmable permissions. compliance. x402. multi currency settlement. routing between financial systems that don't share an owner. four months ago, a network was designing for billions of transactions per second because its own manifesto said that's what the agentic economy would eventually require. this week, the company watching internet traffic at global scale said humans could become a rounding error. maybe 11 million tps wasn't built for today's financial system. maybe it was the first benchmark for the next one.