QUIC in Proxy Mode: Cloudflare’s 2x speedup isn’t just hype
📷 Published: Mar 23, 2026 at 12:00 UTC
- ★QUIC replaces TCP, doubling throughput in Cloudflare One
- ★User-space overhead killed—latency drops for real-world tasks
- ★SASE vendors now face pressure to match performance
When Cloudflare rebuilt its SASE client to use QUIC streams instead of TCP for Proxy Mode, it didn’t just tweak a setting—it eliminated an entire layer of friction. The result? A 2x throughput boost and latency reductions that actually matter for remote workers, not just benchmark charts.
The problem wasn’t TCP itself, but the user-space TCP stacks that added unnecessary overhead. QUIC, built for the modern internet, handles multiplexing and connection migration natively, without the round-trips that bog down legacy setups. For end users, this translates to faster file transfers, snappier SaaS apps, and fewer VPN-like stutters during video calls—the kind of improvements that show up in daily workflows, not just lab tests.
This isn’t theoretical. Cloudflare’s own data confirms the gains, and the shift aligns with a broader industry push toward QUIC adoption in performance-critical tools. But the real test isn’t the protocol—it’s whether competitors can replicate the gains without Cloudflare’s global edge network.
📷 Published: Mar 23, 2026 at 12:00 UTC
The real-world gap between protocol specs and user experience
For the SASE market, this move is a shot across the bow. Vendors like Zscaler and Netskope have long promised low-latency security, but Cloudflare’s QUIC implementation sets a new baseline. The pressure is on: either match the performance or risk losing enterprise customers who’ve grown tired of trade-offs between security and speed.
Yet there’s a catch. QUIC’s benefits depend on server-side support, and not every enterprise app or legacy service plays nice with HTTP/3. Cloudflare can enforce this at its edge, but most companies will hit compatibility walls—especially in hybrid environments. Early adopters may see gains, but widespread impact hinges on ecosystem adoption, not just one vendor’s upgrade.
The bigger question is whether this marks a turning point for SASE. If QUIC becomes the default for secure proxies, it could finally kill the myth that ‘security adds latency.’ But for now, it’s a high-stakes experiment—one that forces the industry to prove whether protocol upgrades translate to real-world wins or just better marketing slides.