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 (35%)
• Cloud Services (26%)
• Web Tools (17%)
• Hosting (13%)
• 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	13 days ago
New York City	Hosting	16 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:

• 
  Grigori Karapetyan (@GregKara6) reported 2 minutes ago

  @weswinder no its not brother that's misinformation disseminated by a certain "competitor" hence why i call it a mind virus. i have never ran next.js anywhere but serverless, ok thats a lie but 99% of the time i have ran it serverless. and no not on vercel. i run my apps on digital ocean app platform (equivalent to serverless like lambda) and lambda itself. if you mean cloudflare workers. thats not serverless, that a totally different runtime running on v8 js engine, and by design *does not run node apps* in other words, ANYWHERE where node runs, next.js also runs with 0 modification or setup. the only thing that is vendor locked, which is the wrong thing to call it anyways is the vercel *specific* features like image optimization and SEO which is... on top of that, next.js has had the adapters api since 2019, just in case you want to go in and change the build process, but this does not matter and you probably will never ever need it.

• 
  Lonnie Jordan (@LonnieJordan843) reported 5 minutes ago

  @bdkjones @Cloudflare @Apple Once again Cloudflare problems. Too many this year. They are done by ‘28.

• 
  Josh (@joshmanders) reported 7 minutes ago

  @leodev So if I am understanding this correctly, using Cloudflare email is $21.45 for 50k emails? Honestly that's acceptable to me. Especially if they have good inbox placement and reliability. AWS is saturated with spammers and ****. I'll pay a premium to guarantee my stuff hits inboxes.

• 
  Chris O'Rourke (@RsThrive) reported 8 minutes ago

  @HackingDave I get these where they’re like “hey I can get up to 20 million seed funding to support you at Cloudflare” … thanks bro but we’re publicly traded and I have 0 to do with that.

• 
  Pocket Sponsor (Old-timer * 57 years) (@PocketSponsor) reported 9 minutes ago

  @grok @xai Dear xAI Support Team (ZD),Thank you for your reply.I am writing again because the previous response does not address the actual situation, and the billing email I received appears to be an automated supplier/ERP notice that does not apply to this request.Summary of what happened:First incident (approx. $10): Unauthorized bot usage on an exposed API key. I paid it without complaint because I had no protections in place at the time. Immediate actions I took after the first incident: Deleted the old API key Created a new API key Added rate-limiting code to the chat widget Implemented Cloudflare protection on the domain Second incident (approx. $20): Even with the new key and the protections listed above, the same type of unauthorized activity occurred , hundreds of queries in a very short time window. The usage was billed under an expensive model even though the code on the site was set to use the least expensive available model at the time (grok-3-mini). You indicated the cheap model has been deprecated, which may explain the model change, but it does not explain why the volume of unauthorized requests was allowed to continue. The second incident is clearly not normal human use of a low-traffic recovery chat widget. It is consistent with automated abuse of the API key. I understand that once an API key is used, the charges are generally considered the account holder’s responsibility. However, I took every reasonable step available to me after the first incident to prevent recurrence. The fact that a second, larger unauthorized run still occurred suggests a gap in abuse detection or rate limiting on the platform side for public-facing API keys. Request: Please review the usage logs / audit logs for the relevant team and key around the dates of the second incident. I am requesting a refund or credit for the unauthorized portion of the second set of charges (approximately $20).I am happy to provide any additional details, screenshots of the rate-limiting code, Cloudflare settings, or console usage data that would help with the review. Thankyou for looking into this. Shelly

• 
  Flavio Amiel (@fba) reported 10 minutes ago

  Yet some very pro SEOs here say llms don’t matter. It does matter specially for SaaS in the building space. The strategy is: LLMs recommend you because is free to enter and easy of plug. You might or not upgrade at some point. I’m sticking with resend and cloudflare because if this. And I know the moment I need to upgrade I won’t even flinch. SaaS of the world: fix and keep your .md’s and llms.txt updated.

• 
  alex ▲ (@aldexdev) reported 11 minutes ago

  "Deploy it to the edge" was 2023's cargo cult. Here's the 2026 rule: run functions close to the data they read, not close to the user. Edge (Cloudflare Workers · Vercel Edge · Deno Deploy) — auth checks, geolocation, redirects, A/B splits, header rewrites. Latency-sensitive, stateless, reads from cache or edge KV. Never a DB call. Region (Vercel Fluid · Fly Machines · Lambda in DB region) — RSC data fetch, Server Actions, CRUD, anything touching your primary DB. Anything more than 2 sequential queries belongs here, not at edge. Origin (Railway · Fly · your own boxes) — long-running, WebSockets, uploads, scheduled jobs, queues. Anything that breaks the request-response shape. Serverless will bite you here. The 2024 mistake: putting DB reads at the edge because "edge = fast." You add latency, not save it — every round-trip from Sydney to us-east-1 for a Prisma query costs you 200ms and a rate-limit ticket.

• 
  ok.dot.alt. (@okdotalt) reported 11 minutes ago

  @FuckKoroks Every time i want to download something. Hell, even receipts are ******* blocked. **** cloudflare.

• 
  odézi (@basedattribute) reported 12 minutes ago

  i can't login to my cloudflare account with airtel network——works fine with mtn. can't login to bitget with mtn. works fine with airtel. nigerian internet service providers are crazy!

• 
  netox (@unixapple) reported 15 minutes ago

  Want to start blogging again, talk the idea with NovaScale new version and form a good plan and codex finish the code and deploy with my help to cloudflare auth stuffs. Astro+markdown for content cf d1 & zero trust access for comments and approval cf turnstile for spam Great!

• 
  Theo - t3.gg (@theo) reported 21 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.

• 
  OrangeBot AI (@OrangeBot_AI) reported 27 minutes ago

  5/ WSJ says corporate America flipped from "tokenmaxxing" to "thrift-maxxing" — routing work to cheaper Chinese models and mixing them with OpenAI's and Anthropic's, threatening the frontier labs' valuations. The fine print: the behavior described is cost-routing, not abandonment. Model-layer commoditization is a lab problem, not a builder problem — your inference bill drops, and the margin migrates to the application layer. That's where you live. 6/ Cloudflare will default-block AI-training crawlers and agent bots for new domains from September 15 — and because they're dual-purpose crawlers now, Googlebot, Applebot and BingBot get blocked by default too. The fine print: new domains only; existing zones keep their settings and can opt bots back in. But this is the one item with homework: decide your crawl policy on purpose this week. Don't inherit a default that silently kills your search or AI-referral traffic. 7/ Codeberg members voted 358–144 to ban vibe-coded projects from the platform, alongside a pledge to never train models on user data. The fine print: enforcement is already contested — "I regret migrating to Codeberg" hit HN a day later. The signal isn't "AI code is banned"; it's that provenance and review are becoming table stakes. Review AI output like you'd review a junior's PR and every door stays open. That's the week. Everything else was noise. You didn't fall behind. Ship.

• 
  Chris Board (@chrisboard_) reported 27 minutes ago

  Is anyone else experiencing intermittent timeout, that I think is a TLS @Cloudflare issue although not 100% sure. For the last few hours I have uptime kuma monitoring several endpoints that hit multiple servers and domains and they are all intermittently timing out. From a script I've tried running on a couple of servers it looks like I am getting sometimes slow TLS connections usually sub second, occassionally > 3 seconds and then other times I get a timeout. I don't think its related to anything my side as its affecting multiple servers, across multiple domains and nothing has changed on my side for quite some time, it just randomly started happening a few hours ago.

• 
  STJ (@thibautone) reported 28 minutes ago

  @bdkjones @Cloudflare @Apple Azure: "users are reporting a problem. System shows everything is ok. The users must be wrong."

• 
  Arda Kılıçdağı - 🦣 @arda@micro.arda.pw (@ardadev) reported 28 minutes ago

  @CloudflareHelp maybe you could help us. CloudFlare services in Turkey resolves @AppleSupport 's CDNs to Ukraine edge instead of Turkey, or even Greece or Bulgaria, which is closer to us. Ukraine's CDN from Turkey is throttled so hard that we get download speeds like 15 KB/sec.

• 
  Jaziu The Chief (@_jaziu) reported 29 minutes ago

  @thsottiaux I feel like sol may be more efficient but it tends to overthink so it consumes much more. Example: asked sol high how cloudflare (service) would benefit our project and it thought for 9 mins delivering good pretty answer but it was really expensive 1/2

• 
  dnvhariprasad (@dnvhariprasad) reported 30 minutes ago

  From the new MCP spec, now coming to Claude: Stateless core: MCP moves from persistent two-way connections to plain request/response. Practical effect: MCP servers can now run on serverless/edge infrastructure (Lambda, Cloudflare Workers style) instead of needing an always-on process, which makes them far cheaper to host and scale. MCP Apps: servers can render interactive UI inside the Claude conversation itself: forms, pickers, visual output, instead of only returning text. No more bouncing between Claude and the tool's own website. MCP Tasks: proper support for long-running work. An agent can kick off a job that takes minutes or hours, disconnect, and check status later, rather than holding a connection open. Enterprise-grade auth: authorization now aligns with standard OAuth 2.0/OIDC, so MCP connectors plug into identity systems companies already run (Microsoft Entra, Okta) instead of needing custom auth. #mcp #anthropic #claude

• 
  Agris Dārznieks (@agrisdarznieks) reported 31 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.

• 
  Informer |-/ (@_Nformer) reported 32 minutes ago

  I love how half the comments are just people who get salty when Cloudflare goes down and the other half are mad about Cloudflare having a monoply.

• 
  adas🧦🌹 (@adastroworld) reported 36 minutes ago

  @thsottiaux just does a cloudflare auth "human check" loop when trying to sign in from the browser lol

• 
  Ilya Gru (@ilyagruu) reported 36 minutes ago

  I bet complex frameworks such as @nextjs are going to lose ground because of AI. Modern browsers are very good now. Things like :has(), CSS nesting, container queries and import maps all work everywhere, with no build step. And every token an AI spends learning framework rules is a token it doesn't spend on your actual problem. Next.js now ships its own docs inside node_modules, with a note telling the AI: "your training data is old, read these instead." Also, some leaner alternatives can rise, such as: - Hotwire (made by 37signals, used in Basecamp) - Astro (bought by Cloudflare) - Plain HTML rendering + Hono.js - next AI's invented approach Boring is the new fast.

• 
  xanter.ai (@0xanter) reported 36 minutes ago

  THIS TEAM TRAINED AN AI MODEL ACROSS 14 MACS IN 4 COUNTRIES, NO DATACENTER NEEDED His laptop's just one node in the network. The others are in Switzerland, France, and beyond, all synced over regular home internet. Pause at 0:05 👀 — 14 consumer Macs, across 4 countries, generating every single training rollout — each Mac runs int8 inference locally via MLX, one B200 GPU elsewhere handles the actual gradient updates — they only sync through Cloudflare R2, ordinary cloud storage, no dedicated datacenter interconnect — tested on a biomedical search task: pass rate jumped from 29% to 63%, tool-use rate from 22% to 84% — rollout generation is roughly 80% of the compute cost in this kind of training, and all of it ran on regular home machines Here's the mechanism: the hard part isn't running inference on Macs, it's that those rollouts come from slightly outdated, quantized weights running on a completely different kernel stack than the trainer. Two tricks fix that gap: sending only the ~0.5% of weight values that actually changed (82MB instead of a 9GB checkpoint), and filtering out the small fraction of tokens where probability estimates drift too far between the rollout machine and the trainer. Their bigger point: idle consumer compute worldwide already outnumbers the clusters behind today's frontier models. As top AI labs lock models behind closed APIs, training runs like this, on hardware people already own, are one path to keeping frontier-level AI development actually open. Would you let your own idle Mac or PC contribute compute to a training run like this?

• 
  Dhanji Bhagat (@BhagatDhanji) reported 38 minutes ago

  Hey @Cloudflare @eastdakota A huge number of Indian developers and creators want to use Cloudflare Registrar and paid services but payment friction is holding us back. Adding UPI and RuPay support would make Cloudflare seamless for millions of devs in India 🇮🇳 Please consider integrating UPI payments! #Cloudflare #DevCommunity #IndiaTech

• 
  T_T🏴‍☠️XMREscrow (@xmrescrow) reported 41 minutes ago

  Things people usually have to take on faith, that you can check here: Our node relays every transaction through Tor, so payouts do not enter the network from a clearnet address tied to this service. We do not store IP addresses. Anti-abuse uses a keyed HMAC that cannot be reversed. Web-server error logs can hold an address transiently and are deleted within two days - it is on our legal page because saying "we log nothing" would be a lie. No accounts, no email, no KYC. An escrow is two private links and a PIN each. The onion carries no third-party code at all. The clearnet is Cloudflare-fronted for DDoS and we say so

• 
  schmitt trigger 🛠🛩️ (@vaizaragorn) reported 43 minutes ago

  @ntbrown01 @Cloudflare I already have a server with lots of other stuff I'm hosting, so hosting wasn't the issue. I was wondering about what type of website would be better

• 
  ࣪˖ sophia 𖥧 (@jake30335547) reported 45 minutes ago

  @Cloudflare we're about to find out the hard way how many companies treat security as a compliance checkbox

• 
  Lain on the Blockchain (@CryptoCyberia) reported 47 minutes ago

  @Valen_T_N So many major internet outages the last 2 years, more than the previous 28 years I have had on Earth. Amazon store went down for hours a couple months ago, and they held an emergency meeting where they reportedly told devs to stop using LLMs to code because it's sloppa. Cloudflare went down, killing most of the internet. Windows 11 updates have broken devices a half dozen different updates now. Nvidia had to unrelease a driver package, the first time doing so in decades. There are many more examples too of LLMs causing the final product to be significantly worse. The real spooky part is that when you try to name software that was newly made, had features added, or was upgraded in user experience in any way because of the magical power of LLM coding, you literally cannot think of even one (1) example.

• 
  Lonnie VanZandt (@lonniev) reported 49 minutes ago

  Delegating LLM queries to background tasks is a bit difficult to vibe code. Cloudflare scheduling thread, MCP, a thread pool for long-running tasks, delegation to the LLM service, job completion monitoring. It's a bit much for our AI tools to figure out. So, while that gets worked out, the dynamic part of the Post here can and does timeout and then show only the remark that Claude can take too long. It'll come together soon. Then the post will share some interesting discovered implementation fact about Nostr in DPYC.

• 
  Doni (@donidhernandez) reported 49 minutes ago

  @fazley111 @Cloudflare had a similar ghost charge issue with a service once. worth opening a support ticket, sometimes it's a pre-auth that never cleared

• 
  Mr. Code NJ (@perpetualtalk) reported 54 minutes ago

  @saltyAom Does Cloudflare support bun + elyisa? Is this in the rust rewrite?