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 (36%)
• Cloud Services (23%)
• Web Tools (18%)
• Hosting (14%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	14 days ago
New York City	Hosting	17 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	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:

• 
  John Webber (@johnwebber) reported 2 minutes ago

  I use Claude and Codex side by side all day. I needed to migrate a client from one cloudflare account to another, big complex project so I decided to use Fable. I proceeded to hit my limits, switched to API pricing so it could get the job done...then Anthropic has an outage...

• 
  Reem (@DreamySenora) reported 3 minutes ago

  @Medifi @Cloudflare a lot of infrastructure problems today are really trust problem

• 
  احمد (@born2code) reported 4 minutes ago

  @threepointone I did that with fargate (so I can use OpenAI subscriptions), sqs and dynamo. The problem with workers is that cloudflare blocks the OpenAI subscription calls (I suspect this this OpenAI buy blocked at CF edge), which is a non starter at the rate I use tokens

• 
  Theo - t3.gg (@theo) reported 4 minutes ago

  "npx t3 connect" This one's been a lot of work. You can now set up remote control for T3 Code on any internet-connected box with literally one command. All for free. T3 Connect is a minimal open source tunnel layer allowing you to control T3 Code instances remotely without needing Tailscale set up. I've been daily driving it for a month and it has changed how I code. Julius and I put a lot of effort into making setup as smooth as possible. Step 1: Install Claude Code, Codex, OpenCode, or Grok Build Step 2: Run "npx t3 connect" Step 3: Click link and sign in Step 4: You can now control that computer on T3 Code web, desktop or mobile (dropping very soon) We are currently providing this for free (s/o CloudFlare for bumping our tunnel limits). Every user can connect up to 3 devices. We don't want to charge for this, but if the bill gets unacceptable we may have to change course. If you hit limits or have issues, you can always fork, self host, or use Tailscale. T3 Connect may seem like a small ergonomic win. Tbh that's exactly what it is. Regardless, it's one I'm really proud of.

• 
  Pedro Martins (@nikuscs) reported 8 minutes ago

  My rust slop tunnelling service is now public! Wormhole 🪱 - Private Tunneling Relay to run on your vps or @Cloudflare workers + Durable Objects - Cloudflare named & random named tunnels - @Tailscale support - Prefix your next/vite dev servers with wormhole and get a url without worry about ports ( grabbed from portless ) with a few extras - Generates stable worktrees urls when used with private relays, so you can preview your website anywhere. Repo in the comments 👇

• 
  kedy (@big_kedy) reported 9 minutes ago

  Quick explainer on @moonpay PayBox since I keep seeing confusion about it. It’s not a coin. It’s not an airdrop. It’s a payment tool. Basically, it lets you connect Claude or ChatGPT to your money so you can just type what you want, like swap $100 into SOL or book me a flight, and the AI sets it up for you. The security model is the actual innovation here: Your wallet key isn’t stored in one place. It’s split into fragments using multi party computation and kept across separate, hardware isolated enclaves. That means no single party, not MoonPay, not the AI model, not your phone by itself, ever holds enough of the key to move your money alone. For card payments, it routes through Visa’s agentic commerce protocol, which keeps your actual card number out of the transaction entirely. You control how much autonomy it has. Two modes: “Always Ask” makes it stop and get your passkey approval on every single transaction. “Autonomous” lets it act on its own but only within spending limits and rules you set ahead of time. Where the tech comes from: MoonPay acquired an Israeli cryptography firm called Sodot for around $100 million earlier this year specifically for this kind of key splitting infrastructure, it already secures over $50 billion in assets and 10 million+ wallets for other crypto companies, so it’s not brand new or unproven tech, just newly pointed at AI agents. Why this matters more broadly: Other attempts at “AI does your shopping” have struggled, OpenAI’s own in chat checkout feature reportedly got shut down earlier this year after barely a dozen merchants adopted it. PayBox is trying a different approach: instead of building a closed system, it rides on x402, an open payment standard for machine to machine payments that’s now backed by companies like Anthropic, Stripe, AWS, and Cloudflare. The idea is it can reach any service built to accept that standard, rather than needing merchants to build something custom just for it. The honest caveat: Solving who’s allowed to authorize a payment is different from solving whether the AI made a smart decision. An agent operating autonomously within its limits can still execute a transaction that’s technically valid but a bad call, so the permission settings you choose actually matter.

• 
  Hunter Leath (@jhleath) reported 9 minutes ago

  this article will be out of date in 6 months, and the reason why is in the second paragraph: > We wanted off VMs because giving every user an always-on machine with attached disk was too expensive to scale. The hard part is that coding agents assume Linux. if you were a betting person, would you bet that either: a) someone will figure out a way to deliver full-VM semantics at a fraction of the cost, allowing coding agents to continue to assume Linux or b) everyone will converge on a cloudflare stack that requires rewriting everything into javascript? you can guess where I am, Linux isn't going anywhere. *especially* because it's: - portable across providers - users can build different price vs. performance vs. security options themselves - it works with 100% of the existing software out there there are *already* more interesting ways to fix costs in VMs, like Archil's serverless sandboxes which don't charge you at all during the "inference" part of the step what would happen to costs when we intelligently decide on the server-side, for each bash invocation, whether it needs real Linux or just-bash? this stuff is going to become 1000x cheaper

• 
  WIV Reports — Uncensored (@WIVReports) reported 10 minutes ago

  @BasedTorba I canceled my Gab AI subscription. I paid for a full year and got hard-locked out of prompt submissions. Support claimed my ISP was blocking the site. Developer Tools (attached) explicitly showed Cloudflare returning HTTP 429 Too Many Requests on your socket io endpoint (Ray ID: a2377c992a865050-SEA). Support's official response? "Dev ops confirms you are not blocked by CF and says your understanding of what you are seeing is an incorrect assumption." An HTTP 429 from Server: cloudflare is, by definition, an edge rate limit. Instead of escalating basic DevTools data to fix a socket routing bug, support gaslit a paying customer and issued a partial refund to shut down the ticket. If this is how Gab handles infrastructure bugs and long-term users, people should know what to expect. Andrew, email chain is available if you actually care about fixing your support and edge config.

• 
  The Whimsical Time Traveller. (@ObservanTimeGuy) reported 10 minutes ago

  @Fuckingbonehead @WG99_X @PenguySays you'd fit in at Cloudflare, you dense ****

• 
  💗Mommy Cammy Findom💗 (@TrainerCameron1) reported 12 minutes ago

  @SteveChopz I cant wait to buy a standee or more sadly tho the site cloudflare isnt letting me connect I think the website is down rn

• 
  Nik (@TheRealNikR) reported 12 minutes ago

  @galluzzo_julian @webflow You can service 4-5 sites with a $20 Claude Code sub + AstroJS + Cloudflare free hosting. Even if the site blows up in traffic, the fact that you'll likely never pay another dime for hosting is a dagger. Webflow also has bandwidth caps and charge when you go over.

• 
  Publisher in a Box (@publisherinabox) reported 16 minutes ago

  Most publishers will see "charge AI bots to crawl your site" and think revenue. It is not a revenue decision. It is a visibility decision. And the wrong call can erase you from the answers your audience is already reading. Here is what happened. Cloudflare launched pay-per-crawl in July 2025. AWS added the same capability to its firewall on June 15, 2026. Two of the largest infrastructure companies on the web now sell a toll booth for machines, built on HTTP 402, a status code written in 1997 and left dormant for nearly three decades. The background matters. For three decades the deal was simple: let the crawler in, it indexes you, it sends people back. AI crawlers kept the first half and dropped the second. Cloudflare's own data shows training accounts for nearly 80% of AI bot activity. The search-purpose fetches that can actually return a citation are a small slice of what remains. Most of the crawling is pure extraction that sends nobody back. So a toll booth sounds fair. And for certain publishers it is. If you own a deep, licensable archive, a reference database, or proprietary data sets, and your distribution does not depend on those crawlers, charging makes sense. Your content is genuinely worth paying for and you can afford to refuse bots that will not pay. But here is the part the launch announcements leave out. For publishers whose strategy depends on being the answer an AI agent gives, the crawler IS the distribution. Wall it out and you might collect a few cents while deleting yourself from the place where your audience now asks questions. Adobe's 2026 data showed AI-referred traffic to US retailers up 393% year over year. The crawler you would charge and the answer engine that refers a visitor to your site are often the same pipeline. The operator move before you charge anything is to watch the door first. Find out which AI bots actually reach your site and what they take. Separate the ones that feed answers and send referrals from the ones that extract content and return nothing. Then meter one bot on one path and watch what happens to both crawl volume and your presence in AI-generated answers. Let the data inform your policy, not the hype. No public study has yet shown how much citation share a site actually loses by tolling a specific bot. The logic of the cost is sound, but the magnitude is unknown. That is why this stays a decision you make on your own data, not on a rule of thumb. One more thing worth noting for publishers building diversified businesses. Your Facebook page, your website traffic from Google Discover, your newsletter list, and your presence in AI answers are all real audiences with real economics. AI citation is the newest of them and it is growing fast, which is exactly why the publishers who start showing up in those answers now are the ones building an edge before the rest catch on. The operators who win here are the ones already running multiple discovery channels and adding this one while it is still wide open. The toll booth is real. The choice is yours. Before you meter a single bot, know which of them are the ones putting you in front of your audience, and treat your spot in those answers as an asset worth keeping.

• 
  Jacob Hands (@jachands) reported 17 minutes ago

  @dok2001 Fix the Cloudflare codemode MCP server to properly request scopes for all APIs - I had to stop using it because it's missing auth for so many APIs.

• 
  Charity Gamble (@cgambledev) reported 18 minutes ago

  Took an old laptop (2013), installed Ubuntu 26.04 LTS, then installed Forgejo to host my own repos. Set up a Cloudflare tunnel & installed Cloudflared to handle it. Set the laptop to never go to sleep. Cloned my Obsidian vault from GitHub, pushed it to my Forgejo.

• 
  Dylan Garcia (@_dylanga) reported 20 minutes ago

  @CherryJimbo @Checkm3out @Cloudflare I agree. I gave the region fallback feedback to them after their most recent ENAM outage

• 
  Punyapal Shah (@MrPunyapal) reported 29 minutes ago

  @peterfox What if Laravel cloud have static site support via cloudflare r2 bucket 👀 Exactly like aws s3

• 
  IRONSCALES (@IRONSCALES) reported 31 minutes ago

  An email claiming to be Interactive Brokers told recipients their W-8BEN tax form had expired. Clean branding, right down to the NYSE, FINRA, SIPC footer. The Renew Certification button ran through the recipient organization's own link-protection wrapper, which reported it clean because the proxy loaded. The real destination was a domain registered the same morning the email went out, and it answered automated scanners with a Cloudflare challenge instead of a page. No history to score, nothing to render, verdict unknown. Themis weighed the convergence instead: a sending domain unrelated to the brand, a DKIM body-hash failure, a same-day destination hiding behind a bot check, and zero personalization sprayed across multiple mailboxes. Any one signal is deniable. All of them together are not. (Link to full teardown in comments)

• 
  𝚆𝚒𝚕𝚏𝚛𝚒𝚎𝚍__デク ✝️ (@ash__borne) reported 32 minutes ago

  Hello Software/Security engineers At what point can you confidently say that you're "doing" #ZTNA ? I knew about the concept, but never really dove into it. Currently testing tools like Cloudflare WARP/Access Seeing some things about mTLS (still blurry)

• 
  high priestess of tomatoes (@ActualMuscovite) reported 33 minutes ago

  cloudflare is really just an intrusive nightmare on all levels now, it's at the point where it wants to verify me every time i use a basic search function in firefox like is there anyway for me to lobotomize the damn thing

• 
  Hunter Guo (@hunterguo101) reported 34 minutes ago

  Anthropic just shipped the biggest MCP update ever (MCP 2026-07-28). Most takes are protocol trivia — stateless, extensions, auth. The real signal, if you actually build: your distribution channel just got upgraded. MCP is now the HTTP of the AI era — and the pipe is enterprise-grade, runs on serverless, and can render your UI inside Claude itself. The numbers: 400M+ monthly SDK downloads (4x this year), TypeScript and Python each past 1B cumulative, 950+ MCP servers in the Claude store used by millions daily. The standard war is over. The question is whether you're on the rail. Three things that matter: — Core went stateless. Deploy your server to Lambda/Vercel/Cloudflare Workers and scale horizontally behind a plain load balancer. Building an MCP server now costs about as much as writing one serverless function. — Extensions are first-class. MCP Apps render interactive UI right inside the Claude chat (sandboxed iframe). Your interface lives inside Claude — you don't build a front-end, pull users, or educate a market. Make the capability; the channel carries the UI and the users. — The pipe reaches inside the firewall. MCP Tunnels connect Claude to internal servers with no public IP and no inbound firewall rules. Figma, Intuit, Netlify, Zoom are on board. The takeaway: stop building another app to fight for attention. Build an MCP server and let the agent ecosystem be your distribution. Agents are the new distribution channel. This update paved the road.

• 
  Pete Stewart (@pj_stew) reported 41 minutes ago

  @founder_sohan You can use mist open source models with Worker AI, which is a fraction of the cost of SaaS services like OpenAI, and if you use Cloudflare AU Gateway with it, you can also use any of the main SaaS services and switch between models as needed. You can see in the article I wrote yesterday about video transcription that I used Whisper on Worker AI to make a much cheaper transcription service for Achene.

• 
  yohance (@yohanc33) reported 43 minutes ago

  @leinwand @eastdakota @Cloudflare Cool, I happened to apply for this fall’s SWE position (and the previous fall, as well as the previous summer, no luck so far :p). Think I could get a referral? I’ve used several cloudflare infra products (R1, Workers, Workers AI, Workflows, etc). Working on mastercard’s service mesh this summer using Go.

• 
  Mauricio - Mauker Makes 🇧🇷🇩🇪 (@Mauker) reported 47 minutes ago

  @3DInPhil @reprinted3D @printablescom It's like what you said. That's not really on Printables. When using a VPN, you share an IP address with many people, and one of them probably did something bad that got that IP banned. The alternative is to change the server, or try to reason with Cloudflare.

• 
  Haaris Malik (@haarismalikkk) reported 47 minutes ago

  Cloudflare has made infrastructure feel like less of a problem. As a designer that was one of the main things that put building my own products out of reach. Even Cloudflare used to feel like a lot. Now that most of it sits in one place, the technical side doesn't feel like the headache it used to be. Build once and let the platform improve around you. That matters even more for agentic software, which is why I'd bet on Cloudflare as the place to build it. That doesn't mean building good software becomes easy. They can't do that for you. But infrastructure is no longer the excuse.

• 
  Alex🌖⃤ (@axldefi) reported 49 minutes ago

  The job is not done yet, the person/entity doing these false reports just to slow us down, started reporting on our IMAGES subdomain now. Crazy to me how all of these databases flagged a Cloudflare Image hosting url as phishing when the only thing they do is to serve a image and main website is full GREEN. We'll clear these one out as well, one by one. We got motion now! Never give up! We're building at maximum speed and fire to elevate these blockers in the road! Ride until Valhalla!

• 
  Agris Dārznieks (@agrisdarznieks) reported 49 minutes ago

  I've tried to post regularly on 𝕏, but somehow I always ended up needing a scheduling app. This week I built a setup with Notion and a Cloudflare Worker, so my content machine runs inside the app I keep open all day. Now when an idea hits, I write it down and schedule it.

• 
  Rach (@KnudRach) reported 54 minutes ago

  @Cloudflare can you help restore a staging site that went down?

• 
  Dhruval (@dhruvalgolakiya) reported 55 minutes ago

  thank you theo, this is all we needed took ~45 minutes from start to finish to set up the mobile app and self-host everything ( well claude took 45 min but same thing ) > cloudflare > neon db > clerk moved everything to my mac mini, and now i can access it from my macbook and iphone anywhere. goodbye tailscale and network connection issues with it

• 
  Syed Balkhi (@syedbalkhi) reported 58 minutes ago

  @carlhancock Yup. I have multiple WooCommerce stores in many millions in annual revenue, and I know several customers who're much bigger using Woo. If a Woo store can't scale, it's likely a hosting infrastructure problem. We just switched our WooCommerce to @LevamoHosting and the speed is incredible with Cloudflare Enterprise, Auto-scaling, Redis Object cache, etc. Other hosts like Rocket, Pressable, etc all offer solid Woo hosting options that will scale.

• 
  Andrew McGarry (@beyondcontent) reported 59 minutes ago

  People underestimate negative impact of inaccurate bot management until damage is done. Don't expect Cloudflare to be subtle by default. False positives can be a different kind of bad. Log files @datadoghq can help.