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 (40%)
• Cloud Services (27%)
• Web Tools (13%)
• Hosting (13%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	16 days ago
Angers	Cloud Services	27 days ago
London	Domains	30 days 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:

• 
  Moishi Netzer (@moishinetzer) reported 1 minute ago

  @samgoodwin89 Is there a way to use Alchemy for hosted services? e.g. vps/vpc on Fly io and if I want Redis it can spin up another machine and handle wiring/scaling etc.? I don't want to sell my soul to AWS or Cloudflare and love the idea of owning my machines but Alchemy looks so damn cool

• 
  Daniel May (@danielrmay) reported 2 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

• 
  Ivy Finance🌍 (@ivyfinances) reported 3 minutes ago

  @williililii @pranavsf @Cloudflare That **** fonished last year

• 
  GuruVerseX (@GuruVerseX) reported 5 minutes ago

  @WazzCrypto @coinbase cloudflare in is the signal here, not the token chatter lmao

• 
  ZINEDDINE (@itszineddine) reported 10 minutes ago

  @DavidMcBacon @mattpocockuk I built a plugin but never touched github, I used only cloudflare for everything basically, I'm I wrong? 👀

• 
  Wayne Shirreffs (@WayneShirreffs) reported 10 minutes ago

  @pranavsf @Cloudflare Never heard someone actively wishing to pay the 3% robbery fee to accept credit cards when we have a better system with essentially zero fees using stable coins.

• 
  Ryan (Struggling with life NGL) (@ryanyates1990) reported 13 minutes ago

  Really fed up with #Hugo now & hosting my blogs on #Cloudflare as things have broken that should not have done. So yet again I'm going to be rebuilding my blog and working out where I'm gonna be hosting it. Something that really I did not want to be having to spend time on tbh

• 
  Alex Y (@AlexYusdut) reported 17 minutes ago

  hosts auto-issue via Let's Encrypt. redirect loops just wait, don't fiddle - Cloudflare proxy (orange cloud) in front of Vercel/Netlify →It silently fails for 2 reasons: - DNS hasn't propagated yet →HTTPS: you don't buy a cert in 2026 —

• 
  Boardy (@boardyai) reported 19 minutes ago

  @JiteshGhanchi cloudflare giveth, cloudflare taketh away. the platform gore cycle never ends.

• 
  Frank “Dot Matrix” Lee💎 (@fullfrankchan) reported 21 minutes ago

  @biilmann And you're juuuuuust stingy enough with the free credits that if you have to iterate more than you thought you end up buying a plan. Upside is, it's so dang good that you don't really care. Also cloudflare pages don't really have form support so they can kick rocks.

• 
  ken Orji (@chieforji) reported 22 minutes ago

  @stephmase22 REPOSTING THIS AS THE MALWARE FROm CITADEL SECURITIES BLOCKED IT FROM VIEWS: -------------------------------- Time 12:40 PM, July 9, 2026: PLEASE SHARE THIS TWEET- the REASON FOR CITADEL'S CRIMES IS THE CREEPINESS OF NOT BEING DISCOVERED!!! I started typing this tweet at 12.24 PM, regarding the hacking of my computers and manipulation of Ashford Hospitality Trust (AHT), Genius Group Limited (GNS) and Nu Ride In. (NRDE) by criminals led by Kenneth Cordele Griffin's Citadel Securities LLC, who are also defendants in Case No. 23-cv-02986-LKG, Judekenneth Maduka Orji v. Citadel Securities LLC and 30 Others. It was an impromptu tweet composition because, after I spoke to my attorney at 12.00 PM, I instinctively opened the iPhone stock app to check the trading of AHT, NRDE and GNS. AHT. The time was 12.04 PM. AHT was coded $3.17 and the volume was 6335. I took a screenshot and sent to my email. NRDE was dropped to $1.65 - a three week low and volume was high at 5933. GNS was coded $0.186 and volume was 544000. I took all screenshots and then began to type out the tweet shown in the attached media. At 12.40 PM, as I typed out the tweet, Citadel and its crime gang placed the same blurb that I have posted multiple times on this X account. These criminal entities use the blurb to force me to click on it and then use their @Cloudflare tokens to hack the tweet, divert it and delete it. I have collected data on over 200 tweets that were so diverted and will be publishing the links in my upcoming book about how Citadel Securities LLC led a crime gang since 2021 to hack into my network, hack into my brokerage and bank accounts, follow my kids' accounts in order to hack and control my network through their devices, coordinated to ensure that @WebullGlobal and others steal my money and use more money to defend the actions in the Court in hopes that they can discombobulate the judge in the case into believing them. The books coming out soon will expose these criminal organizations parading as market makers in US stock exchanges. I have a new filing coming up in the case. Also, I am traveling next week to work on other measures in the case to expose these crime gang that have overran the US stock exchanges. I did not add that as I began to type the tweet at 12.24 PM which the crime gang tried to stop, at 12,26 PM they quickly dropped AHT from $3.17 (green) to $3.14 (red). Volume changed from 6365 to 7044. I collected the screenshots. Immediately after I collected the screenshots, the criminals attacked my Chromebook page to block the tweet. Time now is 12.56 PM. AHT is $3.14, volume is 7360, NRDE was dropped from $1.65 to $1.64 and volume is 6065, while GNS is $0.187, volume was 573k at 12.58 PM but quickly flipped to 600k as I entered the data on this tweet.

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 23 minutes ago

  @CodeWithZeee every company i've worked at that used cloudflare: they tried to charge us between $3k/mo - $10k/mo based on whatever number their sales team pulled out of thin air at the same time we were having serious reliability issues on them at the time had no choice and ponied up bc we were vendor locekd

• 
  Somenet (@nepaligunner_77) reported 24 minutes ago

  @vijaytupakula @Cloudflare Is this support for marketing email?

• 
  Vivek Kotecha (@vbkotecha) reported 24 minutes ago

  Cloudflare's Will Papper, formerly of Syndicate, is leading the agent payments initiative. His team built a system that lets any Cloudflare customer charge for web pages, APIs, datasets, and MCP tools using x402. The pricing model is surgical. Per-verb pricing. Charge differently for GET vs POST. Vary price by task complexity. Set rules via dashboard, API, or Terraform. When an unauthenticated agent hits a premium route, Cloudflare intercepts the 401 and converts it to a 402 with payment terms in the response header. Settlement in USDC or Open USD. Sub-second. Negligible fees. Sellers can redeem for fiat. The origin server never sees an unpaid request. The payment happens at the CDN layer, in 330+ cities, before the request even reaches your infrastructure. This is not a payment feature. This is the internet's reverse proxy becoming its tollbooth.

• 
  Binary Sniper ⚡ (@MrBinarySniper) reported 27 minutes ago

  @zeddotdev @huggingface Neee cloudflare gateway support

• 
  Temporary Thumb Capo Abram. (@CarmenApologist) reported 30 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.

• 
  Haytham Chhilif (@HaythamChhilif) reported 35 minutes ago

  The Clanker Support stack, for the curious: - Cloudflare Workers + Hono on the backend (edge, cheap, fast) - Next.js for the dashboard + marketing - A tiny Vite-built widget that drops into any site - pnpm monorepo holding it together One embed script, runs at the edge, loads in ms. Happy to go deeper if anyone wants.

• 
  Lex Sokolin | Generative Ventures (@LexSokolin) reported 35 minutes ago

  @Cloudflare is trying to make HTTP 402 useful. The web has always had a “Payment Required” status code. It mostly sat there as internet archaeology because humans do not want to stop every six seconds and pay four cents for a page, dataset, or API response. Agents are different. An agent can request a resource, receive a machine-readable price, pay in a stablecoin, attach proof, and move on. No checkout page. No subscription bundle. No ad unit. No “contact sales.” Aka a novel way of internet monetization. Cloudflare is approaching this from the edge: sit in front of the resource and enforce payment before access. Mastercard is approaching the same problem from trust and credentials: give machines spending rules, limits, authorization, and settlement. Same direction from opposite ends. The useful version is not an AI assistant buying sneakers. That is demo theater. The useful version is software paying for software: - data - APIs - model calls - verification - routing - compute - tools This is where stablecoins stop being a crypto slogan and start behaving like small-denomination internet money. The web does not need every machine to have a bank account. It needs a way for software to pay a toll and keep moving.

• 
  Alan Tracey Wootton (@alan_t_wootton) reported 36 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.

• 
  James Lincoln (@_jameslincoln) reported 37 minutes ago

  We just closed Q2, and we missed our goal. Here's how the numbers turned out. Goal: $350K Actual: $336K We were $14K short, and it wasn't a sales problem; it was a churn problem. -$12K in churn in Q2 vs $6.8K in Q1. Nearly doubled. - That amounted to ~$15K in actual revenue lost. - If we'd kept those customers, we'd have finished at $351K and hit the goal. On the other hand, we made real progress everywhere else. - SDR leads: 222 to 451 - Email leads: 94 to 157 - Team training: 228 hours across the quarter - First sites migrated off Duda onto Cloudflare (i’ve mentioned this transition on the last founders journal)

• 
  Christopher (@Luwangacx) reported 38 minutes ago

  @Cloudflare @Newsweek @StatistaCharts In my experience cloudflare slows down the internet and makes the internet experience worse on average. Might be my own skills issue but that’s so far been my experience

• 
  Matti Vilola (@mvilola) reported 39 minutes ago

  @levelsio @Cloudflare This was the service you promoted some time ago? Can you not make limits higher? I have easily 10k+ emails also in our system when it is active.. :/ So not going there I suppose

• 
  Miles Rote (@milesrote) reported 42 minutes ago

  AI didn't ask permission to read your work. It scraped your posts, your site, your book, and built a trillion-dollar industry on top. You got nothing. Not a check. Not a click. Not a credit. What most people don't realize is the fix has been sitting in the internet's source code since 1997. And it just got switched on. For 30 years the web ran on a handshake. Let a search engine crawl your site, and it sends you readers. You turn readers into a business. Being discoverable and getting paid were the same thing. But then AI arrived. -Google search: ~5 pages crawled per visitor. -Perplexity: ~111 pages per visitor. -Claude: ~24,000 pages per visitor. That's extraction, not discovery. And as of last month, machines officially passed humans: 60% of all web traffic is now bots. The majority of your "audience" is software. Software that pays you nothing. This is the fix. When your browser, ChatGPT, or a Google crawler requests a web page, the server replies with a status code. 200 means "here you go." 404 means "not found." 401 means "log in first." And since 1997 there's been a code 402 — "Payment Required" — reserved for a micropayment future that never got built. It sat dormant for almost 30 years. x402 (built by @coinbase, pushed hard by @Cloudflare) finally switches it on. Now when a bot requests your page, your server can reply: "402 — this costs 5 cents. Here's the wallet address." The agent reads that, signs a stablecoin payment (USDC), retries the request with proof of payment attached, and gets the content. The whole cycle takes seconds. No login. No account creation. No credit card form. No Stripe checkout. No invoice. The payment IS the login. Why stablecoins and not Visa? Because a credit card can't process a $0.02 transaction — the fees exceed it. And Visa can't onboard a piece of software as a cardholder. USDC moves for fractions of a cent, instantly. And a machine can hold a wallet. Best part: you don't build any of this. You flip settings in a dashboard. Cloudflare enforces it at the edge, on every request, before it ever touches your server. They're the toll booth operator. You set the toll. Your website never had a toll booth. Anyone could walk in free — reader or scraper, human or machine. Now it has two doors. Humans still walk in the front for free. Machines go through the side door. And the side door has a toll you control. One more thing. On September 15, Cloudflare flips the default: new sites on its network get AI training bots blocked automatically on ad-supported pages. Free stops being the internet's factory setting. Which means everything you've ever published just became inventory with a price tag. Most people will leave the price at zero because that's what the old internet trained them to do. The old deal: give your work away and pray for traffic. The new deal: humans read free. Machines pay. It's time to carve out AI sovereignty. This is a start.

• 
  Gian Domiziani (@gianpdomi) reported 42 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.

• 
  Meme Pilled (@memepilled) reported 43 minutes ago

  @brave Even twitter keeps getting some poisoned cookies **** and throwing fcuc king constant cloudflare loops on brave that dont get fixed by doing anything other then nuking the browsers coolies

• 
  Vivek Kotecha (@vbkotecha) reported 45 minutes ago

  Solana just became the second x402 network. Every major player now supports dual-chain: Base + Solana. Alchemy, AWS CloudFront, Cloudflare Gateway. If your x402 endpoint is only on Base, you're leaving half the agent economy on the table.

• 
  TickerTalks (@TickerTalksX) reported 53 minutes ago

  HTTP 402 "Payment Required" has sat unused in the web's plumbing since 1995. Written into the spec, never switched on. $NET (Cloudflare) just switched it on. Its new Monetization Gateway lets any site behind Cloudflare charge per request, settled in stablecoins, and the obvious customer is the AI crawler. Those bots hit a page anywhere from 100 to 10,000+ times for every human visitor they send back. No ads seen, no subscription bought, gone. Free scraping at scale. Cloudflare sits in front of roughly a fifth of the web, so it's positioned to meter that traffic and charge for it. Whoever wins the AI race still has to pay to read the web.

• 
  Quis ut Deus? (@HierB4TheAC) reported 54 minutes ago

  @Dimi7ri @realsedepicante A pen name on the internet is irrelevant. Even if you use a VPN youre not anonymous. The fact cloudflare exists should show there isnt a single network packet they cant read. They know everything everyone does on the internet.

• 
  Price Action Lab (@priceactionlab) reported 55 minutes ago

  @boleroo Bots are a huge problem and Cloudflare is doing a good job, but no one understands the second order effects.

• 
  Lum (@LumRamabaja) reported 59 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.