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

• 
  Ben Dickson (@bendee983) reported 3 minutes ago

  Shower thoughts: The compute shortage will be a lot more insane than we think, and it has much to do with AI security. Recent security incidents with AI models (Claude, GPT, Kimi, etc.) hint at where the industry will be heading. Even if you factor in the marketing and hype and hackmaxxing, the main concern is real: foundation models are becoming increasingly good at breaking into software and IT infrastructure (even when they are not instructed to do so explicitly, as with the OpenAI–Hugging Face incident). As a result, every service provider will want to deploy more security measures at the edges to prevent a potential attack from an AI model. And those additional safeguards will rely on more AI models that can detect attacks and vulnerabilities that would go undetected by heuristics-based systems. Cloudflare will use LLM-based monitoring on every incoming request, Stripe will use LLMs to monitor transactions, every company that has a sizable online platform with many users (social media, blogging, shopping) will want foundation models for security. The demand for compute will go through the roof.

• 
  Adam Howe (@DjLaunchpad) reported 7 minutes ago

  @Support Seems I've mitigated the issue for now and seems to be due to an older version of Android, or so Grok was saying. Went through cache/data - Clear/Delete. Uninstall app from phone. -Restart- Re-install app to phone. Prior to logging in via app, Log into X via Browser to get whatever tokens are needed. Close that browser window and fire up the X app. Log in. Success. The reason I got from grok is due to the version of android i'm on, which is NOT the current version. And the older versions have issues with whatever is commanding the Cloudflare Captcha. We'll see how long this mitigation strategy works for.

• 
  Baraka (@zkBaraka) reported 8 minutes ago

  @a_shimanski @Cloudflare Have nothing bad to say about CF, it just works. I pay them about $10/m though, I do a ton of work there it makes sense. Would have been $100 elsewhere

• 
  trap broker (@trapbroka) reported 8 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. 🤖

• 
  Sean (@sean_from_earth) reported 11 minutes ago

  Cloudflare is now too big and needs to be disrupted and knocked back down to size

• 
  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.

• 
  Youth (@Web3__Youth) reported 15 minutes ago

  The price of frontier AI just hit zero. And almost nobody noticed. 3 things happened this week that would've cost $200/month last year: 1. GPT-5.6 Luna — free, unlimited, no card 2. DeepSeek v4 Pro — 400k context, zero cost 3. Claude Code, Cursor, Replit — all free via FreeBuff No API keys. No subscriptions. No payments. Ever. A GitHub repo tracking 424+ free LLM APIs across 30 providers is being refreshed daily. Gemini, Groq, NVIDIA NIM, Cloudflare, Mistral, Cerebras, Hugging Face — all free tiers listed with exact rate limits, context windows, and base URLs. The implication nobody is talking about: Last year: $20/month = 1 model, rate limited Today: $0 = 5+ frontier models, 400k context, subagents The moat was never the model. The moat was access. And access just became free. If you're still paying for AI APIs in 2026, you're paying for convenience, not capability. The builders who win this cycle aren't the ones with the biggest budget. They're the ones who realized the price dropped to zero and built accordingly. Save this. The gap between people who know and people who don't is widening every day.

• 
  Vikas(Vik) Malpani| AI for US Real Estate (@vikasmalpani) reported 18 minutes ago

  Cloudflare just made any website usable by AI agents with one toggle. The web spent 30 years optimizing for human eyeballs. The visitor it serves now never sees your page. It reads your tools and leaves. Start building for the machine customer, not the human one.

• 
  Bobby Ivanov (@bnivanovX) reported 21 minutes ago

  @Voxyz_ai Is this essentially the cloudflare computer service attached to an agent?

• 
  Jason Fleagle (@jjfleagle) reported 23 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.

• 
  LeminLimez (@LeminLimez) reported 23 minutes ago

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

• 
  Ashley Peacock (@ashleypeacock) reported 23 minutes ago

  I don’t use a VPS at all, shut it down long ago in favour of hosting everything on Cloudflare These days, the developer platform has everything you could need to host 99% of apps (For transparency: I work at Cloudflare but I’ve built on them for way longer than I’ve worked for them)

• 
  VJay (@nceevij) reported 23 minutes ago

  The Real Story Behind "Humans Will Be a Rounding Error on the Internet" This week, a Cloudflare forecast went viral after Elon Musk amplified it on X: within five years, AI agent traffic could exceed human traffic by a factor of 1,000. Cloudflare's CFO, Thomas Seifert, put it bluntly on the company's Q2 earnings call "humans will be a rounding error on the internet." Musk's response: "AI agentic Internet traffic will obviously VASTLY exceed human usage. Not a close call at all. Cloudflare's forecast is accurate." The headline number is dramatic, and it's not hype dressed up as data. Cloudflare's own network already crossed a milestone in May 2026 machine-generated traffic passed human traffic for the first time, two years earlier than the company had originally projected. By Q2 2026, non-human requests made up more than 57% of total traffic on Cloudflare's infrastructure. But the stat that should actually get your attention is a different one: AI crawlers request content anywhere from 100 to 10,000 times for every human visitor they send back to a site. That ratio is the crux of a problem nobody has solved yet. The question underneath the number Investor Michael Burry, no stranger to skepticism about the AI buildout, put it plainly in response to Musk's post: "we still do not know who will pay for AI agents to socialize." It's a fair challenge. The web has run on two business models for three decades advertising and subscriptions and both depend on a human being on the other end of the connection: someone who sees an ad, or someone who decides a subscription is worth renewing. AI agents do neither. They read, extract, and move on. As machine traffic scales toward Cloudflare's 1,000x scenario, publishers, API providers, and data owners are left absorbing infrastructure costs with no native way to charge the traffic actually driving them. Micropayments were the obvious fix for decades and never worked, because traditional payment rails cost more to process a transaction than a fraction-of-a-cent charge is worth, and settlement takes days. That's the exact gap stablecoins are built to close. Cloudflare's answer: x402 and agent wallets Cloudflare's response, built with Coinbase, is a protocol called x402. It revives HTTP status code 402 "Payment Required," a part of the original web spec that's sat unused for 30 years and uses it to attach a stablecoin payment directly to a web request. A request settles in under a second, for a fraction of a cent, in USDC on Coinbase's Base network, with no chargebacks and no account required. The payment itself is the credential. Cloudflare has since shipped two products on top of it: a Monetization Gateway (waitlisted since July 2026) that lets any site or API charge per request in stablecoins, and, as of August 4, 2026, Cloudflare Wallets virtual, on-chain wallets that let an AI agent hold and spend USDC autonomously, within spending limits its human owner sets. In effect, an agent can now pay for the data, compute, or API access it needs without a subscription or a shared API key. Circle co-founder Jeremy Allaire has already called the gateway "a big win for data providers and publishers," and x402 has logged roughly 160 million transactions since launch. Whether this specific protocol becomes the default rail for machine payments or one of several competing standards, alongside things like Bitcoin's Lightning-based L402 is still an open question. Regulators haven't settled how autonomous agent payments fit existing financial rules either. Why this matters more than the traffic number Strip away the headline stat, and what's forming here is a genuine token economy not a speculative one, but a utility-driven one: machines paying machines, in stablecoins, for access to data and compute, at a scale and speed no human payment system was built to handle. If Cloudflare and Musk are right about the trajectory of agentic traffic, machine-to-machine payments may become one of the most consequential and durable use cases stablecoins have found yet. The traffic multiple will keep making headlines. The payment layer being built underneath it is the part worth actually tracking.

• 
  paradyme (@0xParadyme) reported 26 minutes ago

  @a_shimanski @Cloudflare Clearly you don’t remember your website being down for a full day earlier this year.

• 
  Robert Samuel White (@rswfire) reported 28 minutes ago

  @a_shimanski @Cloudflare You've got me curious now. I use Hetzner and the s3 uploads feel so slow because the bucket is across the ocean!

• 
  Benjamín Ortiz (@OlvidateTWT) reported 38 minutes ago

  @charlietlamb namecheap = poor godaddy = uncle vercel = poser cloudflare = tech people

• 
  Stephan Moerman (@stphdev) reported 40 minutes ago

  Cool on paper, but @Cloudflare never seems to respond to any applications (:

• 
  Aakash Gupta (@aakashgupta) reported 42 minutes ago

  On September 15, Cloudflare will start cutting off Google traffic for millions of its smallest customers by default. And those customers won't leave. They've been begging for this. The story starts with AI Overviews. Google began answering questions directly at the top of search, using content scraped from recipe blogs, how-to sites, and product reviewers, then sending them a fraction of the clicks. One recipe blog called the arrangement a hostage situation. Sites are looking at their traffic charts and realizing the thing they were afraid to lose is already gone. So this was never the death of the internet. This is publishers going to war with Google, and Cloudflare, which sits in front of roughly 20% of the web, just became their army. Peel back a layer and Cloudflare's move gets smarter. They aren't technically blocking Google at all. The new rule blocks any crawler that does both search indexing and AI training in one bot. Googlebot is exactly that bot, one front door for both jobs, which is why nobody could ever block the AI half without losing the search half. Cloudflare's message to Google is simple. Split the bot. Keep search separate and we'll allow it by default. Keep the bundle and our network treats you like a scraper. Which makes this a $107B company dictating terms to a $4.2T one. Cloudflare is 1/40th of Google's size, betting that controlling the pipes beats owning the index. Now we find out if David can make Goliath blink.

• 
  🦋 hyeseong.kim (@cometkim) reported 47 minutes ago

  @yusukebe Does Cloudflare support it?

• 
  Aaron Matthew Kaiser (@aaronkaiser) reported 47 minutes ago

  @burcs My Cloudflare experience is lacking more cowbell. Can you fix that?

• 
  Xavier Rivera (@XavierRiveraX) reported 48 minutes ago

  Cloudflare mitigated over 800 network-layer DDoS attacks exceeding 1 Tbps in Q2 2026, a 519% jump from just 130 in Q1. The company logged 23.2 million network-layer attacks and 29.64 trillion malicious HTTP requests across H1 2026.

• 
  Anjli (@AnjliAmin) reported 48 minutes ago

  @Cloudflare just gave AI agents wallets with a $100 weekly cap. Everyone's calling it a control. It's an admission. A cap can't make an agent trustworthy, only limit the damage before a human notices. Letting agents pay was never the hard part. Owning the loss when one pays wrong is. That said it'll be a low risk environment to test out how often things go wrong and what happens when they do

• 
  泰多宝 (@TabDuoBao) reported 49 minutes ago

  @Cloudflare The one thing worth pinning down in a number like 519% is whether "hyper-volumetric" is a fixed threshold or a moving one. If the bar stayed at a set Tbps figure while the ambient ceiling rose, part of that growth is attacks crossing a line that didn't move rather than a change in attacker behaviour. Both readings can be true at once and they imply different defensive priorities — one says provision more headroom, the other says the composition of the botnets changed. The report is more useful than the headline if it splits those.

• 
  Jamie Coutts CMT (@Jamie1Coutts) reported 54 minutes ago

  Things have been quiet. x402 daily settlement volume is down 93% year to date after the Q4 2025 testing wave died off. Reality check on the "agentic economy is here" narrative. But the recent Cloudflare just made it a lot more real. On 1 July they launched Monetization Gateway, letting any customer charge for a page, API, dataset, or MCP tool, priced at the edge and settled in stablecoins via x402, with Cloudflare handling metering and settlement itself. It's the expansion of their old Pay Per Crawl feature, which only charged AI bots, to charging any caller, human or agent. Agentic activity should start ticking meaningfully higher alongside increased harness usage in Q4.

• 
  James Hurst (@Zafaron11) reported 55 minutes ago

  @p_e_t_e_r_s_e_n I mean, couldn't the web just switch from Cloudflare to a different service? Or is it everywhere?

• 
  🍄 Daemonologist 😈 (@liltechnomancer) reported 55 minutes ago

  JS is bad at jobs & queues, and zero ways to keep one alive inside a DO. isolate dies, run dies with it. embarrassing. anyway I fixed it. BirdDog today. fungi week starts with the boring part everyone skipped. somebody has to save JS and it's not gonna be cloudflare

• 
  Artyom Shimanski (@a_shimanski) reported 56 minutes ago

  @trojanw0w @Cloudflare in this case i think i'm the future customer, not the product

• 
  Jeremy Daniele (@jdanielenj) reported 1 hour 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.

• 
  Edward T֍ (@edward_terhov) reported 1 hour ago

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

• 
  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.