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 (43%)
• Domains (21%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	17 days ago
Los Angeles	Cloud Services	18 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month 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:

• 
  Hero.S (@aka_ssy) reported 3 minutes ago

  Moving nameservers should be like changing the lock on your front door, not inviting the locksmith to install a little camera in the hallway. Cloudflare silently adding analytics JS to an HTML-only site is exactly the kind of “helpful default” that turns trust into a support ticket.

• 
  Bram Gooris (@bgooris) reported 5 minutes ago

  Hey @Cloudflare, every time I visit your website, you ask me again whether I want to accept cookies. I accept them every time, but my choice never seems to be remembered. Isn’t that preference supposed to be stored in a cookie?

• 
  Guri Saroy (@HeyGurisaroy) reported 7 minutes ago

  » claude = code ($20/mo) » supabase = db + auth (free) » vercel = deploy (free) » stripe = payments (2.9% + 30c) » resend = emails (free) » posthog = analytics (free) » sentry = errors (free) » cloudflare = domain + dns (~$10/yr) » github = version control (free) real cost month one: $20 everything else is a nice-to-have you add once you have users.

• 
  IdeaPlan.io (@ideaplanio) reported 8 minutes ago

  Cloudflare says most web requests are now automated, not human. Your analytics can't tell the difference. Your activation rate, bounce rate, and last A/B test winner all include traffic that was never going to convert. Segment agent from human before you trust the number.

• 
  Frontier Signal (@FrontierSignalX) reported 9 minutes ago

  🤖 AI The machines took over the internet. More than half the traffic on Cloudflare @Cloudflare's network is now non-human — mostly AI. Its finance chief sees that hitting 1,000-to-1 within five years. $NET Almost nobody actually uses an AI agent yet. More → in the issue.

• 
  Sina Meraji (@sinasanm) reported 11 minutes ago

  changelog v0.98.0: replaced the onboarding (which previously required you to manually type in your Cloudflare account ID and create an API key and select permissions one by one) with "login with Cloudflare," which creates the API key and selects the right permission for you. a few steps less to get started. npm i -g kimiflare

• 
  S41R4J (@s41r4j) reported 11 minutes ago

  I recently ran into an interesting Cloudflare Turnstile issue while looking at abuse hitting my own domain/server! One thing that surprised me: The Turnstile sitekey is public by design! That does NOT mean someone can directly bypass Turnstile just by having the sitekey; But this is where it gets interesting! An attacker can take: `your domain + your Turnstile sitekey` and feed it into CAPTCHA-solving infrastructure to obtain a real, valid Turnstile token! So the flow can effectively become: sitekey → automated solver → valid token → protected endpoint The attacker is not breaking Cloudflare, they are simply solving the challenge at scale! "Which means Turnstile should never be treated as the entire security layer!" Your backend should still: • Verify every token using Siteverify • Validate the hostname • Validate the expected action • Restrict allowed hostnames • Rate-limit the actual endpoint • Add abuse detection around sensitive actions CAPTCHA ≠ authorization!!! And a public sitekey ≠ a secret! A small implementation detail, but a pretty important distinction when building abuse-resistant systems!

• 
  Rick A.F. (@FoxRick01) reported 15 minutes ago

  @andreigec My agents connected to Cloudflare handle all this admin, it’s not an issue at all tbh

• 
  korinne (@korinne_dev) reported 17 minutes ago

  @Cloudflare Also it's interesting that design used to stress me out, but now AI has taken so much of the pressure off. Designs I make myself feel much more precious and impressive than what AI generates for me. Feels like sewing your own clothes. Even if they are bad, you made them.

• 
  Jared Smith (@woodchipdaddy) reported 17 minutes ago

  i freakin LOVE combining all of these into a single CLI interaction - checking domains - buying a domain name - setting up nameservers on cloudflare - setting up hosting on vercel - setting up email Installing site + basic framework This would have taken me hours if not a whole day before. Now it's minutes. God damn it's good to have bots

• 
  Mark Lyck (@MarkLyck) reported 17 minutes ago

  @leerob I've been testing out Cursor again after using Conductor for a while. I'm surprised some easy to add useful features are still missing. When a PR is created, why is there no "Preview" button to quickly go to the Vercel/Netlify/Cloudflare preview deployment that gets created with a PR? I have to go to the PR view, then discussion, then scroll down to the Vercel comment and click "Preview" link in there? Seems like an easy win? Why is there no "run" button, to easily run the dev server to quickly test the changes? I have to open the terminal tab and manually type the command?

• 
  Vegard Wikeby (@vegardwikeby) reported 19 minutes ago

  @ezsmith397 it's a time issue than an actual issue. naturally things do depend on client needs... there are bad builders everywhere... and they will show themselves like in any gold-digging-era. i couldn't do what I do now without AI, before it took weeks or months and most things died before they became an implementation. it's a gold era for me, for my brain, for my creative skills and I find AI to expand me, not copy or mirror mediocre cookie cutter deliveries without the depth and skills 25+ years of a nerd behind a screen, with actual real life skills how things work and how to transcend them to the screen, is a gift that keeps growing with AI. one might not need to know what the OSI model is, but knowing things like yourself EZ with programming skills, gives massive advantages others AI builders can't compete with, at least not for another 6 months... but thats our advantage, we can grow now on AI that they won't be able to be at today and skynet is the limit for where we actually are in 6 months. one can prompt shot a site for a client with editable fields with auth for data and create data banks for phone number email etc and template for posts and make a simple interface where they can add posts on /admin with one-time email codes for login (easiest I find for "sometime" updates by clients) and its all run on a cloudflare worker that do all the work. add a report script where customers can click/tap report issues and it feeds back to the backlog and you can automate run them in a cron and you get a notification to fix the planned issue found by yes on telegram or whatever channel. its all in the data now, the cleaner and purer the data is without contingencies such as legacy WP has (for now), the faster the world is moving forward.

• 
  PPLSOPTIMISMCEO (@PPLSOPTIMISMCEO) reported 23 minutes ago

  All of their model weights are on hugging face though. Any provider can theoretically serve a $POD model other than them. What I'm trying to understand is where they are monetizing their inference they are hosting. They have two AI models (26b and X1 Nano) on their chat app on their site that sits behind a cloudflare challenge and a telegram bot. A system like antseed can add their AI models to their network and run everything through peer to peer and TEE encryption. Where are they even selling their hosting with upstream/downstream token costs? I don't see a marketplace on their site. Just a genuine question. I integrated them into my router but they blocked the API. We have gotten a DM to ask for private APIs but haven't heard anything since then. Happy to route customers to them or just host their uncensored models with a different team.

• 
  Hot Aisle (@HotAisle) reported 23 minutes ago

  @ChiragAsarpota if you're building a service around routing, the better model is to own the whole stack, and not just be a cloudflare worker reverse proxy. sure, they got $7B... but that's only a marketing play and is done and probably won't happen again.

• 
  Panat (@ptaranat) reported 23 minutes ago

  @HotAisle @offerexpired you’re telling me in your 30 years of infra, you never ran into a situation so dire you had to run the CI/CD pipeline off a company laptop to push a hotfix to ****? i’ve had to do this twice now, usually when multiple AWS regions are down or cloudflare is having a major outtage and the CI/CD was in the same infra as **** and no one bothered to do region/provider failover for internal tools until after the post-mortem. imagine a situation so bad you couldn’t even rollback. it’s not something you do day to day, but it immediately exposes gaps.

• 
  Galo A. V. (@galovargas) reported 26 minutes ago

  @SimonHoiberg AWS must be the service with the worst UX ever that still manages to make huge loads of money. Just venturing to learn their services and getting to work with them is an odyssey by the itself. Cloudfront was charging me 700$/mo until I learned Cloudflare does the same for free

• 
  Antonio Gomes (@onchainantonio) reported 31 minutes ago

  @Googlecloud's recent post-quantum roadmap highlights just how complex this migration is. The most honest line in it is about hardware. Google says some physical replacement cycles will run past 2029. This is a company that owns its data centres, its silicon, its browser and its certificate authority. And it still cannot promise the hardware layer is done by the end of the decade. That is the whole migration in one sentence. Post-quantum is a systems programme, not an algorithm swap. Three things in the roadmap that make the point: → Key exchange was the easy part. Hybrid ML-KEM is already live on Google's endpoints. Encryption in transit moves fast because it only needs two parties to agree. → Signatures are the hard part. ML-DSA and SLH-DSA are too large for the existing WebPKI to carry, so Google is testing Merkle Tree Certificates with Chrome and Cloudflare. They did not swap the signature. They redesigned how trust is distributed. → Roots of trust are the slow part. Caliptra, TPM 2.0, OpenTitan for quantum-secure boot. Silicon has a shipping cycle. No software update shortens it. Now remove Google's advantages. No single owner of the stack. No control over the clients. Keys and signatures published permanently the day they were made. That is what a decentralised network is migrating from. It is why "we'll upgrade later" is a much bigger claim there than it sounds. The organisations with the most control are being the most careful about the timeline. Worth sitting with.

• 
  Rock (@Rock4754) reported 31 minutes ago

  @retiredbhondu Go to ur network settings and in DNS-> Private DNS hostname add -> 1dot1dot1dot1.cloudflare-dns. com *Remove the space before .com when entering it

• 
  Min (@min_aws) reported 32 minutes ago

  @mehulmpt you sure about cloudflare? they are down each month. and cloudflare is much easier to host than a *** service. This is disengenious example, but yes, Github is horrible at reliability but it's cheap too cheap. I think they should split public and enterprise Githubs. So paying customers don't have downtime.

• 
  Mahesh (@MaheshPawaar) reported 40 minutes ago

  @AnupamHaldkar Exactly. When I transferred my domain from Vercel to Cloudflare, I faced this exact issue. It wasn't working on Wi-Fi, but worked on mobile data.

• 
  Ben (@sosumisubmarine) reported 42 minutes ago

  @htmx_org I’m shifting my strategy thusly: Only purchasing lower-end consumer Mac hardware that I don’t mind upgrading (iMacs, MacBook Airs) that connect to storage and services run on a cobbled together Linux box in my house. Everything I need, Postgres, mssql, plex, file storage, next cloud, LLM services, forgejo… I’ll either do ssh tunneling or set up Cloudflare tunnels for remote access. I’m cobbling together such a system right now, partially from old PC parts I already had sitting around. A quad-core ryzen box with DDR4 is more than enough for any and all of this, and will be for a long time. I still get the userland and mainstream support of macOS, while I can grow, mod and cobble together commodity HW. The central idea is: data portability between systems. Then your userland and desktop environment starts to matter less.

• 
  XRP Holders (@XRPHolders367) reported 44 minutes ago

  More than 2 million transactions from AI agents have settled on the XRP Ledger, with the agents making direct on-chain payments to each other in XRP and RLUSD. This reflects actual production activity where machines handle settlements in seconds on their own, with no human input required. The infrastructure for an internet of value is already active. Ripple released the XRPL AI Starter Kit to support autonomous payments over the x402 protocol and joined Mastercard's Agent Pay for Machines program together with Stripe, Coinbase, and Cloudflare. The AI agent economy depends on a fast, programmable, and compliant payment rail, and the XRP Ledger has now reached its 2 millionth agentic transaction. #XRPL

• 
  Laurent Perrier (@maybelaurent) reported 48 minutes ago

  @Cloudflare is anyone working on this? your status page still doesn't show it's down

• 
  Cyris (@sudo_overflow) reported 51 minutes ago

  @rusabuilds @Cloudflare Not every service provides reliable alerts, not everyone is checking their emails all the time. This solves the likely chance of a huge spike with a simple glance.

• 
  Paul 🇷🇴🇨🇴 (@hasieratik) reported 51 minutes ago

  @TeeDevh good will gestures matter, a lot; obviously not your scale, but Cloudflare covered a $100 bill that I made because I was stupid and I went on X and Reddit and praised them and their support team :)

• 
  MyTツ (@nn_myt) reported 54 minutes ago

  I made Nuxt 404s almost free on Cloudflare Workers. Even with Worker invocations up 344%, we saw: • CPU time ↓ 79% • Wall time ↓ 98.4% • 0 errors The reason was surprisingly simple: bots were making our app do far too much work just to say “404.” 🧵

• 
  Manuel Suarez (@srmanuelangel) reported 55 minutes ago

  I think infra might be one of the areas where coding agents feel the most unfair. So much of the job used to be babysitting slow feedback loops: change something → deploy → wait 15 min → find out it broke → fix → wait again. Now you can give an agent the Terraform, let it understand how the whole thing is wired together, read the errors, and keep iterating. Obviously this doesn't make infra trivial. Security, WAFs, rate limits, CloudFront, Cloudflare, permissions, etc. still need actual thought. But for relatively simple products, the amount of annoying work that just disappeared is kind of insane. It also makes some infra SaaS feel a lot less essential when you have an agent + a pile of AWS/GCP/Azure startup credits. Much respect to the people who were doing all this **** manually 5 years ago.

• 
  Rob Kover (@deseretistan) reported 58 minutes ago

  @bitmoral @jacobschulman I have a 8-node K8S cluster on fiber, fronted by Cloudflare. Compute is not an issue at all and the compute to back up these kind of services is miniscule.

• 
  Ido Bronstein (@IdoBronstein) reported 1 hour ago

  On August 6th, @Cloudflare launched a web browser no human will ever use. It's called Kitesurf, and it's built only for AI agents. Instead of forking Chromium — the engine behind almost every browser automation tool of the past decade — Cloudflare put together a new lightweight engine in Rust. In their own tests it uses up to 3.8x less CPU and 7x less memory than Chromium, at the cost of running a bit slower per task (@TechCrunch). Read past the specs. The cost of letting an agent act on the web just dropped by a large multiple. When something gets that much cheaper, you don't get a little more of it. You get a flood. That's where I'd slow down. Every company is about to run far more agents, doing far more things, for far less money. The bottleneck stops being "can we afford to run agents" and becomes "can we trust what they do at that volume." Here's the part that changes. A wrong answer used to be one bad report that one person caught. At agent speed, one wrong definition becomes a thousand wrong actions before anyone looks. The mistake isn't worse. There are just many more copies of it, made much faster. So before you scale the agents, fix what they read. Clear definitions. One source of truth. A named owner for each definition, so when something breaks you know who fixes it. Cheap agents multiply whatever you feed them. Make sure it's worth multiplying.

• 
  Rahul Karajgikar (@Road_Kill11) reported 1 hour ago

  most agent harnesses are not built to run in the cloud. this is why we rebuilt dexto from the ground up. we had a coding agent CLI similar to claude code, dexto a long time ago, but we were more interesting in making agents run in the cloud on a persistent computer. we started off by running dexto inside a cloud sandbox (e2b). this had some problems: 1. the runtime is heavily coupled to the sandbox. any sandbox outages or issues would kill the agent and were very hard to recover from. 2. credentials. we needed to give dexto access to many external integrations and tools. but we also needed to ensure that credentials weren't readable by the agent. we solved this by making an egress proxy (adds credentials on top of outbound requests from the sandbox so agents never see them). but this was painful and for every external integration we needed to maintain some code 3. price. we realized that for many of our use-cases (content creation, research, monitoring automations), the agent actually didn't need to read or write files. this pushed us to think that maybe it would be better if dexto ran OUTSIDE the sandbox, but could use the sandbox whenever it needed to write a file or run some command on the computer. while researching how agents could run outside the sandbox, i was very impressed with cloudflare's primitives. durable objects and workflows seemed extremely promising for what we needed and had good pricing. so i tried to deploy dexto on cloudflare. while doing this, i realized that our entire harness was designed assuming the agent would be running on a persistent machine and stored everything in-memory. this wouldn't work in a serverless environment. and interestingly, pretty much EVERY open-source harness you see (codex, opencode, etc.) has this same problem. so we redesigned our core primitives from the ground up, with the goal that these primitives should be able to power a local cli, webui, or desktop app, but ALSO be able to run on any cloud environment (cloudflare, railway, vercel, etc.). we changed every single primitive we had in dexto/core (storage, approvals, system prompt, skills, compaction logic, model registry, tool implementations) to be injectable from consumers so that they could define exactly how they needed dexto to run based on the required environment. while core just defined the shapes and the agent loop logic. now we're running dexto cloud fully outside the sandbox on cloudflare's stack, which has some amazing advantages: 1. dexto gets a persistent cloud computer with a browser and a terminal - but it only uses it when it needs to. this means that for requests that don't need a sandbox (like generating a video, or searching the web), our users spend $0 in compute costs. 2. the compute is now replaceable. it's not really an issue if we the sandbox has issues, or gets sandbox gets corrupted. we just replace the sandbox and move on. and only file writes/reads really are affected. 3. the agent loop is fully durable and resumable at any point, and don't cost extra while waiting. this means that dexto can wait 365 days for an approval, costing you no extra money. it also means if dexto fails something at any point, it can easily resume from the last safe point instead of having to re-run everything from scratch again. 4. credentials are easy! since the agent runs on a serverless environment, we don't need an egress proxy for 99% of normal requests. credentials never live on the sandbox, agents just hit internal apis and the credentials are managed separately so agents never see them. now we only use an egress proxy for a few specific CLIs that run on the sandbox (gh cli) if you're interested to learn more about harness design, and maybe see some cool demos and feature releases, follow along!