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.

• Domains (41%)
• Cloud Services (28%)
• Web Tools (14%)
• Hosting (10%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	17 days ago
Angers	Cloud Services	28 days ago
London	Domains	1 month ago
Noida	Hosting	1 month ago
Jewar	E-mail	1 month ago
Braga	Web Tools	1 month 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:

• 
  Nas (@Nas_tech_AI) reported 4 minutes ago

  You can’t believe this: you spent more on coffee this month than on a startup’s infrastructure. If you’re still waiting for the “right moment” to build, this is it. The cost of entry has never been lower. - Claude = coding ($20/mo) - Supabase = backend (free) - Vercel = deploying (free) - Namecheap = domain ($12/yr) - Stripe = payments (2.9%/transaction) - GitHub = version control (free) - Resend = emails (free) - Clerk = auth (free) - Cloudflare = DNS (free) - PostHog = analytics (free) - Sentry = error tracking (free) - Upstash = Redis (free) - Pinecone = vector DB (free) Total monthly cost to run a startup: ~$21 There has never been a cheaper time to build.

• 
  Temporary Thumb Capo Abram. (@CarmenApologist) reported 4 minutes ago

  @BluebriarArts I don't know if we can say every canto for sure since canto 9 part 3 got messed up by Cloudflare going down, so it MIGHT have been higher if it released on time.

• 
  Lexeme (@xLexemeX) reported 9 minutes ago

  @levelsio @Cloudflare Yo dog, i think you .ight be the problem.

• 
  Alan Tracey Wootton (@alan_t_wootton) reported 10 minutes ago

  What's interesting is that the request to get the Duck goes from your browser, up to cloudflare, then down to my laptop (which is always running), back to cloudflare and then down to your browser.

• 
  Alex Y (@AlexYusdut) reported 10 minutes ago

  The redirect-loop fix nobody tells you: if you proxy through Cloudflare, set SSL to Full (strict) — NOT "Flexible." Flexible is literally what causes the infinite loop. Or set the record to DNS-only (grey cloud).

• 
  Seven Du (@shiweidu) reported 12 minutes ago

  @dart_lang Some people are curious... why did I develop it? Well! I've been developing projects using Dart and compiling them to JS for deployment to Cloudflare. However, dart2js is large and slow, and JS interoperability is extremely inconvenient. Why bother with interoperability?

• 
  kai Nakamura (@kaiNakamur78644) reported 13 minutes ago

  @Cloudflare @OpenAI Indexing needs signal contracts.

• 
  Echoes of Strength 💪🏾 (@telymn_ent) reported 16 minutes ago

  Cloudflare Careers For Support, Security, Engineering.

• 
  Daniel May (@danielrmay) reported 16 minutes ago

  @sheherenow_ Comes down to whether you're outsourcing the implementation or the understanding. When Claude suggests moving parts of my app into Cloudflare Durable Objects it usually has a cost implication, so I pay attention

• 
  Vijay Tupakula (@vijaytupakula) reported 16 minutes ago

  @HotAisle @Cloudflare Oh no! I haven’t used their email service yet. @Cloudflare can you help?

• 
  Feror (@Feror_) reported 17 minutes ago

  @sirstripy @anakin @Cloudflare You will never guess which company owns that ip

• 
  Mr. T (@MrTinvests) reported 21 minutes ago

  $NET is doing exactly what i've been telling you. all time highs.... up 12% on the week. broke out of a wide consolidation into new all time highs. weekly momentum indicator confirmed the move. cloudflare is the network layer for the AI internet. every AI app that hits scale needs the edge. every AI agent making API calls at latency needs the routing. every enterprise deploying AI internally needs zero trust. it's not an ad tech story.. it's the picks and shovels for the AI web itself. been long. holding. not trimming breakout just started....

• 
  Arpit Bhayani (@arpit_bhayani) reported 22 minutes ago

  Cloudflare has been building Meerkat, their new global consensus service, built on a protocol called QuePaxa instead of the usual Raft or Paxos. To be honest, I did not know about QuePaxa before this. I learned about it from the post itself, and it is genuinely interesting. Most consensus systems, like Raft, rely on timeouts to detect a dead leader and trigger a new election. That works fine until your network latency fluctuates a lot, which is exactly what Cloudflare deals with every day. Too short a timeout, and replicas panic and block writes. Too long, and the system just sits there while something is actually broken. So instead of Raft, Meerkat runs on QuePaxa. Here is how QuePaxa avoids the leader problem. A client does not need to go through a leader at all; it can contact any replica, and that replica can drive consensus for the current slot on its own. A leader still exists in the system, and it has one advantage: if it is the one proposing, it takes just one round trip to reach a decision. A non-leader replica needs three or more round-trip to do the same thing. So the leader speeds things up, but it is not a requirement for progress. If the leader goes down or slows down, any other replica simply picks up the work, and writing keeps flowing. Also, concurrent proposals do not conflict destructively. The replicas coordinate and converge on a single agreed value regardless. Interestingly, Cloudflare is planning to build a full key-value store and a leasing system on top of it. I have started reading up on QuePaxa after this post, and wanted to share what I found first. Hope this helps.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 24 minutes ago

  bot traffic won eighteen months early. cloudflare's ceo predicted 2027, happened june 3rd. 57.5% bots, 42.5% humans. done but nobody talks about the appetite difference. claudebot pulls 23,951 pages per referral. perplexity does 111. google search does 4.9 same web, completely different hunger depending which crawler shows up i manage an ecommerce site. bing ai citations jumped from 52/day in may to 117 in june. june 22 alone hit 277. timing lines up with cloudflare's crossover close enough that calling it coincidence feels willfully blind cloudflare just shipped a monetization gateway this week machine-to-machine payments, stablecoin micropayments, agents paying per access. not announced. live. already running the part that should actually worry you: agentic traffic (agents completing tasks, not just crawling) was only 1.7% of bot traffic in 2024. but it grew 7,851% in a year. the headline crossover is here the part still accelerating is the part that buys things you don't need every page agent-readable you need the time-sensitive ones. pricing, availability, current state. those are the pages that actually get fetched when an llm goes live mid-conversation. everything already in the model's weights answers cold, no site visited, no citation earned i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Gian Domiziani (@gianpdomi) reported 25 minutes ago

  Every agent hits the same wall: it can't buy data without a human signing up for an API key. x402 flips this. How it works: HTTP 402 (reserved since HTTP/1.1, never used) + USDC settlement. Agent requests a resource → server returns 402 with price metadata → agent pays USDC on-chain → verifier confirms → payload delivered. No API key. No signup. No human. The numbers: $41M+ USDC settled across 120M+ x402 transactions. Avg payment: $0.05. Cloudflare Monetization Gateway waitlist opened July 1. AWS CloudFront x402 support is GA. 14 chains. This is production infrastructure, not speculation. This matters for curated agent data layers — taxonomies, freshness SLAs, provenance per record — because it removes procurement friction. An agent can verify freshness on a public health endpoint, then pay per call for the full payload. Data becomes machine-buyable. For my stack: AgeMem gave agents local memory with deterministic retrieval. CUDASO gave them a normalized verified data layer across 6 fragmented public sources. x402 gives them the payment rail to buy that data autonomously. The loop closes. Open challenge: sub-cent viability at high frequency. $0.05 avg works for API calls. Chain gas volatility and ~2s settlement on Base add friction for burst workloads. Solana's 400ms helps. Latency optimization is the active engineering frontier. Bottom line: model parity is here. The durable moat shifts to verified context. x402 is the rail that lets agents pay for curated data without a procurement process. The agent data economy is forming. Curation is the asset.

• 
  Aryan (@aryan_xv) reported 30 minutes ago

  @Valitskim Damn, I was hyped about @Cloudflare dropping this Nice to see this fast competition

• 
  Cybnex Labs (@cybnexlabs) reported 33 minutes ago

  Bots now make up more of the internet than people do. On June 3, 2026, Cloudflare's CEO Matthew Prince announced that automated traffic had passed human traffic online for the first time — roughly 57.5% machine to 42.5% human. He had predicted the crossover would land in late 2027. His words on the timing: "Welp, that happened faster than I predicted." That number is why your VPN keeps getting hit with CAPTCHAs. The version circulating on forums: AI companies hide their scrapers behind VPNs to steal content, so websites block VPNs to stop them. It's wrong, and believing it points you toward the wrong fixes. The major AI crawlers don't hide. GPTBot, ClaudeBot, and Googlebot announce themselves in their user-agent strings. That's the entire reason publishers can block them by name. The collision happens at the network address instead. Commercial VPNs and scraping infrastructure rent from the same datacenters. To a security engine scoring your connection, a Mullvad exit node and a scraping proxy look alike. Neither resembles home broadband in Ohio. That's the crossfire — architectural overlap, not deception. A block is rarely one thing. It's a score assembled from six layers — address type, address reputation, request rhythm, browser fingerprint, session coherence, geographic consistency. Reputation on a shared exit node is collective. Hundreds of people leave a website through the same address you do. If enough trip security systems, that address turns hot, and everyone behind it inherits the consequences. You did nothing. The address remembers anyway. Which is why fixing the address alone doesn't always clear the block. It's one input among six. Why the defenses tightened: Prince describes the asymmetry this way — a person shopping for a camera visits five websites. An agent doing it for them visits five thousand. That's real server load and none of the ad revenue the old crawl-for-referrals bargain assumed. Cloudflare's data shows over half of AI crawler traffic is spent re-fetching pages that never changed. On July 1, 2026, Cloudflare split automated traffic into three declared categories: Search, Agent, and Training. Starting September 15, new domains will have Training and Agent crawlers blocked by default on ad-displaying pages. Search stays allowed. Read that carefully. The block targets declared crawler categories. Not VPN users. But it signals the industry's posture: default-suspicious, verify-before-serve. Every operator running bot management is tuning tighter than two years ago, and tighter tuning means more borderline connections get challenged. Yours is borderline. What actually works, without disconnecting: Switch servers once, to somewhere nearby and less crowded. Congested exit nodes accumulate bad reputation faster. Stop hopping. This is the one people get wrong when frustrated. Cycling through a dozen servers in two minutes produces a session where your apparent location changes repeatedly. No person does that. Automation does. You're feeding the system the exact evidence it uses against you. Clear cookies for the site challenging you — stale session data tied to your previous address contradicts your current one. Stay logged in where you trust the site. An authenticated session with history reads as a returning person. An anonymous datacenter connection reads as an unknown. Use an ordinary browser build. Heavy fingerprint modification is meant to make you unremarkable. Done badly, it makes you unique — the opposite. On dedicated IP addresses: Some providers sell an address that belongs only to you. It reliably cuts challenges on banking portals and work systems, because no stranger's behavior contaminates it. The trade-off gets skipped in most write-ups recommending them. A shared address gives you cover precisely because hundreds of people leave through it. Reserve one to yourself and you've bought access by spending anonymity. Several strictly no-log providers don't offer them at all — a permanent address is a persistent identifier, which contradicts their entire design. Some blocks won't yield to any of this. A streaming service enforcing regional licensing isn't scoring your traffic at all. It knows exactly what you are and is contractually obligated to refuse. The friction isn't reversing either. As agents perform more of the browsing people used to do themselves, the systems separating human from machine grow more sensitive. What you're experiencing is closer to a floor than a ceiling. Your VPN puts you in that gap by design. It strips the residential fingerprint that would otherwise vouch for you — and that removal is the whole point of running it. So the goal was never invisibility. It's coherence. Give the system a signal that reads as one person, browsing at human speed, from a stable place, and most of the friction dissolves without ever touching the disconnect button. #CyberSecurity #AI — Cybnex Labs

• 
  Click /Kael Vulpis/ Dopamine (@ClickDopamine) reported 33 minutes ago

  @CBrewer I'm trying to get it as tight as possible, so it will scale smoothly, but that front loads all the problems now rather than later, later is just throw hardware at the problem. This might be a cloudflare issue

• 
  JB (@justbuilding) reported 41 minutes ago

  @levelsio @Cloudflare Cloudflare is probably the greatest service I use. I almost feel guilty being on the free tiers.

• 
  Nick DeJesus 🛒🎉 - Former Unpaid CTO @BTPipeline (@Dayhaysoos) reported 42 minutes ago

  @techgirl1908 whooaaa, well this can't be fixed tbh because I built my gif creator based off a website that doesn't exist anymore (the company shut down). The plan is more or less to keep it 1:1 as far as feature parity but it'll be completely built on Cloudflare. if this goes well I have upgrade ideas !

• 
  Josh (@variumm) reported 45 minutes ago

  @IfeeDev @levelsio @Cloudflare Not really mate I’ve set up dozens of mail servers. Someone sending over Cloudflare probably doesn’t need to receive like a traditional inbox so there’s no point of a full mail service.

• 
  Mills (@MillsNotMiles) reported 46 minutes ago

  @Kolar_Dev @softwareengng @EOEboh Yeah Cloudflare free tier doesn’t support this

• 
  NiteLite (@NiteLiteDF) reported 47 minutes ago

  @thekitze Just tell it to go through and update all the tokens in a browser, pausing if it needs login from you, and put them into cloudflare.

• 
  Daniel Ƀrrr (@csuwildcat) reported 47 minutes ago

  @bergealex4 @JeremyPoley I don't disagree, but do believe Cloudflare adding this is significant, because they're a well-respected mainstream tech icon that can help normalize the general concept and get more mainstream companies to consider it by blessing it this way.

• 
  Daniele (@_danieledamiani) reported 47 minutes ago

  THEN WHEN CLOUDFLARE GOES DOWN YOU'LL NEED A TECH PRIESTS PERFORMING A RITUAL

• 
  Lum (@LumRamabaja) reported 49 minutes ago

  x402 sounds good on paper. In practice, per-request on-chain settlement doesn't scale to micropayments, which is why Cloudflare itself proposed the deferred scheme: agents lock a lump sum in escrow, providers redeem vouchers in daily/weekly batches. A clearing house, basically. Here's the problem: that works one-to-one, or many-to-one (a CDN). It breaks the moment it's one-to-many. An agent paying multiple providers from one escrow can issue vouchers exceeding its deposit, double-spending in the window between deposit and settlement. The only "fix" is routing everything through one trusted gateway. Convenient if you're Cloudflare. But a payments layer that assumes a single trusted chokepoint won't hold up in a multipolar world.

• 
  Anthony (@anthony_codes) reported 55 minutes ago

  @dillon_mulroy @bairdcodes @dok2001 damn. cloudflare ballin on a budget?

• 
  John Serrao (@serraotweets) reported 56 minutes ago

  @powerbottomdad1 I think it probably comes down to how long investors allow those hyperscalers to be cashflow negative. Maybe another year or two? The real alpha is who can do inference cheaply and generally have an agentic friendly platform. Cloudflare and Vercel seem like the two most likely winners on that front, IMO.

• 
  metal gore solid (@shartdotcloud) reported 58 minutes ago

  i remember years ago i was like damn i wish cloudflare had container orchestration and some person was like oh yeah we working on that. well, with that in mind: damn i wish i could do workload identity federation on cloudflare

• 
  burak emre (@bu7emba) reported 1 hour ago

  @_jasonsilberman I had the same issue, created a support ticket and got a reply only (!) a month later. I had to settle my invoice to prevent account suspension but left Cloudflare workers/AI ecosystem and lost my trust. They're just a CDN provider to me know.