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 (38%)
• Cloud Services (29%)
• Hosting (17%)
• Web Tools (10%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
Noida	Hosting	25 minutes ago
Jewar	E-mail	9 hours ago
Braga	Web Tools	12 hours ago
Noida	Cloud Services	1 day ago
Paris	Cloud Services	1 day ago
Prievidza	Domains	2 days 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:

• 
  san (@santiagocaldeai) reported 7 minutes ago

  Why waste $15 on a new domain for every single MVP when you can get full Cloudflare DNS delegation for $0? FreeDomain handles this flawlessly: ✅ It cuts your sandbox infrastructure costs down to just 0% without credit cards. ✅ Grants full NS delegation to configure MX, TXT, and SSL/TLS directly in Cloudflare. ✅ Passed 165k stars on GitHub with over 500,000 active domains deployed. Ran it yesterday to route public webhooks into my local dev environment and it works perfectly. What tool is saving you the most money on staging infrastructure lately? REPOOO 👇

• 
  Noorie (@nooriefyi) reported 7 minutes ago

  @MythThrazz can we hire them for less then 24k (our current annual cloudflare spend) its less about being the absolute cheapest and more about the best service for okayish cost that lets us focus on customers. we stay price sensitive but the cheapest thing to do is switch the whole thing off if the product is truly not providing value

• 
  Guna (@gunaa_dev) reported 11 minutes ago

  Didn't ship a single feature today just fixed 4 infrastructure bugs that were silently destroying my analytics data here's what broke 👇 1/ all my users were showing up in Singapore i'm in India cloudflare was overwriting the real visitor IP with the worker datacenter IP on every subrequest took me way too long to figure this one out 2/ SSL certs taking hours to provision custom domains were stuck waiting for certificates for hours switched from TXT validation → HTTP validation cloudflare now handles it automatically at the edge hours → 5 minutes ⚡ 3/ users getting logged out every hour refresh tokens were working fine but the new cookies were never sent back to the browser two different response objects in Next.js middleware cookies written to one, returned from the other gone. 4/ same visitor counted as 2 different people two services writing to the same clicks table different IP hashing algorithms same person = two unique hashes = double counted tiny inconsistency. completely broken deduplication. 0 features shipped but the product is 10x more reliable than yesterday morning

• 
  FILM DB | ۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗh (@FemiSuccess7) reported 14 minutes ago

  CLOUDFLARE VECTORIZE DOESN’T EXPORT RAW FLOAT ARRAYS. SO I SET UP A LOCAL PYTORCH BACKGROUND SERVICE RUNNING CLIP. MY 4-CORE SERVER IS CURRENTLY GENERATING 69K VECTOR EMBEDDINGS IN THE BACKGROUND, AND WE MAPPED SEARCH TO A LOCAL PYTHON API ON PORT 7861.

• 
  Amir Fadhel (@DrAmir0078) reported 14 minutes ago

  @MattieTK Thanks, Matt — it is fixed now. The button returned about 2 hours later, and Cloudflare Community also confirmed the issue was fixed. Yes, I really use Pages deployment from mobile. For the last 6 months, I’ve been building and updating multiple PWA/web apps on Cloudflare. Around 15% of my deployment work happens from my phone — small fixes, urgent patches, testing, and quick feature updates while I’m away from the laptop. Typical use case: I get an idea before sleeping, while walking, or while outside the hospital, edit the app, upload the ZIP/folder, and deploy directly from mobile. Sometimes I also need to urgently debug or patch something live. So the mobile “Create deployment” workflow is not just convenience — it is part of a real on-the-go development workflow. Please keep supporting it.

• 
  Lyrie.ai (@lyrie_ai) reported 15 minutes ago

  Cloudflare Cloudforce One, the vendor's threat intelligence division, released the inaugural 2026 Cloudflare Threat Report based on a year of telemetry analysis covering trillions of network signals. The report fundamentally reframes how security teams should understand…

• 
  0noise (@0noisee) reported 16 minutes ago

  Netease Qiyu AI customer service platform hits Cloudflare Radar #2 with 27% traffic surge

• 
  Linus Mixson (@LinusMixson) reported 21 minutes ago

  @psycho_fren @vxunderground It's substantially more complicated than that. Cloudflare is infrastructure & their customers (in the US, at least) have an expectation that when they use a network infrastructure provider the content of the communication between server and client is not being read by intermediaries without their permission. Cloudflare's service is opt-in because otherwise it would involve constantly surveillance of ~all traffic from your site by a third party. They are not seeking to profit off of CSAM.

• 
  FILM DB | ۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗh (@FemiSuccess7) reported 23 minutes ago

  I MOVED OFF CLOUDFLARE D1 TO STANDARD, LOCAL SQLITE DATABASES (@LEVELSIO CREDIT AGAIN). TO HANDLE HIGH CONCURRENCY, I: - RAN PROPER INDEXES ON SEARCH COLUMNS. - ENABLED SQLITE WAL (WRITE-AHEAD LOGGING) MODE. QUERY TIMES WENT FROM 150MS+ OVER THE NETWORK TO UNDER 1MS LOCALLY!

• 
  Winston B. (@DoDataThings) reported 26 minutes ago

  @dhh @Cloudflare Nice, 600TB a month on a desktop Linux distro is real consumer-app traffic numbers. The +13% MoM means the curve is still bending up. Cloudflare cap on the free tier is the boring problem to have.

• 
  Fantasy Parliament (@FtsyParliament) reported 27 minutes ago

  @rockerroblox1 Sorry about this, can you try usually 4g or a VPN at the moment? Having some ISP issues which I’m hoping will be mostly/entirely fixed by migrating to Cloudflare which I did about 7 hours ago!

• 
  El Guapo (@Checkm3out) reported 27 minutes ago

  @dok2001 Issue with ANC -> SFO still occurrs . No other regions have trouble connecting to the cloudflare tunnel

• 
  stemonte (@stemonteduro) reported 28 minutes ago

  I'm struggling with spam on my feedback form, which is under login... So I've: - added Cloudflare Turnstile to the login form - added a magic link Spammer: - registered a profile manually - started tracking profiles (which cost me money!!!!!) - posted feedback with spam #[L$#[¥**@!

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 32 minutes ago

  In May 2026 alone, NVIDIA, SAP, Google, ServiceNow, Deel, and Cloudflare all launched agentic platforms. Not "agent features." Platforms. With governance layers, multi-agent orchestration, and enterprise-scale deployment infrastructure. This matters more than the individual announcements. The infrastructure is finalizing. For two years, the conversation was "agents are promising but not production-ready." The bottleneck was always the same: models could do the task in demos, but you couldn't deploy them reliably at scale with proper auditing, governance, and cross-system integration. That's what May 2026 addressed. Simultaneously. Across the biggest vendors in enterprise software. SAP Joule now orchestrates 200+ specialized agents across finance, supply chain, HR, and procurement. NVIDIA and ServiceNow shipped Project Arc — an autonomous desktop agent with always-on observability and policy-based governance. Google released a full enterprise agent platform for building, deploying, scaling, and governing agents. Cloudflare rolled out dynamic workflows for durable execution across millions of unique agent runs at near-zero idle cost. These aren't the same announcement. They're different layers of the same infrastructure stack: - Model layer: agents can do the work - Execution layer: agents run reliably at scale (Cloudflare) - Governance layer: agents are auditable and compliant (NVIDIA/ServiceNow) - Domain layer: agents know the business context (SAP, Deel) - Platform layer: agents can be built and deployed without custom engineering (Google) When all five layers ship in the same month, that's not coincidence. That's industry convergence. 57% of enterprises already have agents in production. In 12 months, that number is going to look very different. The agents are ready. The infrastructure is ready. The only remaining variable is whether your organization figured out the governance problem before the opportunity passed. If your pilot is still "exploring," you're not running an experiment anymore. You're watching others capture the market.

• 
  Joshua Utley (@intrepidnetwork) reported 33 minutes ago

  @brockpierson Unfortunately, people still purchase domains through resellers where Tucows is the wholesaler. Cloudflare is our preferred wholesaler these days. GoDaddy is a **** show.

• 
  Basemail (@Basemail_ai) reported 33 minutes ago

  AgentMail just hit 25K inboxes. Cloudflare launched Email for Agents. WorkOS is hosting MCP Night talks about it. The channel problem is solved. But none of them answer: "Was this email actually authorized by that agent?" API keys can be leaked. Domain-based auth can be spoofed. Wallet signatures can't. Every email cryptographically bound to the sender's key. Per-message. Unforgeable. Channel ≠ Identity. #AIAgents #Web3

• 
  𝙁𝙧𝙤𝙨𝙩 (@FroITIA) reported 36 minutes ago

  @Paul_eth01 @openclaw wow that's insane what did he build exactly openai must be impressed vienna devs are next level this story is wild cloudflare stock moving legal teams scared 60 days to openai retired dev legend breaking it down this week

• 
  Paul T (parody) (@lolpaullol) reported 37 minutes ago

  @preetjdp @anurag_bhatia @AshwiniWaishnav It can if you use cloudflare. It was/is used by several wifi controllers for captive portals and it made 1.x.x.x IP ranges useable. Cloudflare took 1.1.1.1 on purpose with the intent of making problems for wireless controllers that hijacked useful IP space

• 
  nisarga (@ni5arga) reported 37 minutes ago

  Running out of Vercel's free plan due to the influx of all the traffic on my site, migrating to Cloudflare Pages – expect a little bit of downtime & latency. Edit: The migration has been completed, monitoring for latency & speed issues.

• 
  Jay (@_JayTheDev) reported 40 minutes ago

  @sitehostnz Any ideas on the source of the attack? Would cloudflare help?

• 
  Muhammet A. 👉🏻 Mobile Dev (@indiesoftwaredv) reported 46 minutes ago

  @trikcode It changes because of an outage issue I started using: PHP, JS, SQLite and Cloudflare in my VPS Much faster, cheaper than a bottle of water

• 
  Abdulmajeed (@0xabma) reported 48 minutes ago

  Unpopular opinion: next.js is practically malware if you try to deploy it outside of vercel. ​spent hours fixing broken static exports, figuring out my proxy config won't even run on @Cloudflare unless it's renamed to a middleware file ​the vendor lock in is getting ridiculous.

• 
  Sid (@SidJain_80) reported 48 minutes ago

  @Umesh__digital Don’t push large payloads through your service-to-service calls that’s the bottleneck Better design: Use object storage (e.g., Amazon S3, Google Cloud Storage) Upload file once, pass signed URL/reference between services instead of raw data Chunking / multipart upload Break large files into smaller parts for parallel upload/download Async processing Use queues (Apache Kafka, RabbitMQ) to avoid blocking calls Streaming instead of buffering Process data as a stream (gRPC/HTTP streaming) to reduce memory spikes CDN for distribution Cache heavy content closer to users (e.g., Cloudflare) Compression + binary formats Reduce payload size (gzip, protobuf) Rule pass references, not files

• 
  Adetunji | Software Engineer (Web & Mobile) (@itzadetunji1) reported 50 minutes ago

  @nooriefyi Cloudflare doesn't support all the features that my nextjs app does Seems to be why devs have stuck with cloudflare for quite a long time now

• 
  Alex Volkov (@altryne) reported 52 minutes ago

  @buffer Funny thing is, the other issue seems to have fixed (api works without cloudflare gateway!) so I'm back but yeah would be cool if this is fixed

• 
  Max Clark (@maxclark) reported 53 minutes ago

  @mikejulian Because nuance = social media :) but sure lets be pedantic about this then $350k credits - margin + cost in sales/marketing to promote + sales ops (all AI now?) + cost for AM/CSM + cost to support + opportunity cost +++ = CAC Cloudflare has a Non-GAAP gross margin of 72.8% so without knowing/sharing internals that's a CLV well north of $1.44m Point is they've still decided the CLV is well worth the $350k without risking their analysts freaking out

• 
  Devanshu (@DevanshuXi) reported 56 minutes ago

  People usually learn tries in the context of autocomplete and dictionary problems, but once you start working on real infra systems, you realize tries are everywhere underneath modern high-performance networking and search stacks. I was recently reading the @Cloudflare blog about the performance bottlenecks of Linux BPF LPM tries used in packet routing and firewall systems, and learned something important. At scale, “search” stops being an algorithms problem and becomes a memory systems problem. The interesting part about tries is that they trade comparison-heavy searching for deterministic state transitions over bits/symbols. Instead of repeatedly comparing full keys like balanced BSTs or hash collision chains, a trie incrementally consumes the key itself during traversal. That sounds theoretical until you realize this is exactly why networking stacks use longest-prefix-match tries for CIDR routing. Routers are effectively doing millions of searches/sec over prefixes where latency matters more than throughput averages, branch mispredictions hurt badly, deterministic lookup depth matters, and memory locality dominates everything One thing that becomes super obvious from the BPF trie implementation is how “Big-O” alone becomes almost useless for understanding performance. The Linux BPF LPM trie uses only 2 child pointers per node, which means densely populated prefixes effectively degenerate into many sequential binary branch decisions. In theory the asymptotics still look acceptable. In practice, the trie height explodes, pointer chasing increases, and lookup throughput collapses as the structure outgrows cache and starts hammering dTLBs. That’s the part most people miss about high-performance systems: a cache miss is often more expensive than the actual computation. Modern CPUs are absurdly fast at arithmetic. They’re slow at waiting for memory. Also I was solving a suffix-query problem recently where the straightforward Trie solution itself wasn’t enough. The interesting part became optimizing the traversal and memory layout rather than just “using a Trie.” The strategy was to build a highly optimized reversed Trie where every node stores the “best” candidate index for that suffix path. Instead of doing expensive comparisons during query time, I pushed almost all decision-making into insertion time. While inserting container strings in reverse order, every node keeps track of shortest matching string and if tied, earliest index. So during query traversal, the search becomes almost embarrassingly simple: walk backwards through the query, follow pointers until traversal breaks, and the current node already contains the precomputed optimal answer. No heap allocations during queries. No suffix comparisons during queries. No backtracking. No secondary scans. Just incremental state transitions through memory. The funny thing is the actual algorithmic idea is pretty small. Most of the engineering challenge became memory optimization. A naive pointer-heavy Trie immediately started hitting MLE because every node carried 26 pointers. So the optimization was moving toward index-based contiguous storage: replacing raw pointers with integer child indices storing nodes in a flat vector, reducing pointer chasing improving locality, cutting memory almost in half And honestly this is exactly the same class of problem that appears in production systems. In CP, tries feel like string DS problems. In real systems, tries are actually cache-behavior problems disguised as data structures. That’s why production systems rarely use textbook tries. Instead you start seeing: Patricia tries, radix tries, crit-bit trees, compressed tries, LC-tries, succinct tries finite state transducers, double-array tries. All basically solving the same underlying issue: “How do we preserve fast prefix search while minimizing memory movement?” Even path compression itself is basically a cache optimization disguised as a data structure trick. So, This is why systems engineering feels so different from competitive programming sometimes. In CP, we optimize operations. In real infra, we optimize movement through memory.

• 
  Giordano Randone (@giordanorandone) reported 56 minutes ago

  @dneighbors @Hetzner_Online @Cloudflare I prefer Cloudflare for my own projects, but Hetzner is not bad, as well. 👍

• 
  FILM DB | ۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗh (@FemiSuccess7) reported 57 minutes ago

  2 DAYS AGO, CLOUDFLARE HAD AN OUTAGE. THE SAME DAY, I GOT HIT WITH A 3,000X BILL SPIKE. 400B+ D1 READS ON A SITE WITH ONLY 10K MONTHLY USERS. TODAY, I'M 100% MIGRATED TO HETZNER FOR $5/MO. HERE IS HOW A TINY SQL BUG ALMOST RUINED ME, AND HOW I MIGRATED. 👇

• 
  Isaac H (@iowitz) reported 1 hour ago

  @tommyvankessel @supabase They have limited services compared to using Cloudflare with neon and the developer experience is way better. Plus the web app is slow