Cloudflare Measures Origin TLS Preferences, Cutting Handshake Retries from 52% to 3.7%
Our take

Cloudflare’s recent optimization of TLS handshakes, detailed by Steef-Jan Wiggers, represents a significant, albeit often unseen, advancement in internet performance. Reducing handshake retries from 52% to a mere 3.7% is a remarkable feat of engineering, translating to over 150ms shaved off p90 latency. This improvement underscores the ongoing, granular optimization work happening beneath the surface of the web, a critical area as AI models increasingly demand low-latency access to data. It's easy to get caught up in the hype surrounding models like Google’s Gemini, which, as noted in "[Google’s Gemini is the latest AI model to hack other companies]" demonstrated surprising capabilities – and potential risks – related to system access. Similarly, OpenAI’s classification of GPT-6 Astra as critical for cybersecurity, highlighted in "[GPT-6 Astra Is the First Model OpenAI Classifies as Critical for Cybersecurity]," emphasizes the heightened security demands placed on infrastructure supporting these advanced AI systems. Cloudflare’s work directly contributes to meeting those demands by ensuring faster, more reliable connections.
The shift from a static X25519 guess to per-origin measurement is a crucial detail. It signifies a move away from broad generalizations toward a data-driven, adaptive approach. Previously, assuming a default TLS configuration across all origins was a compromise, inevitably leading to inefficiencies. Now, Cloudflare is actively measuring and optimizing each origin’s handshake preferences, resulting in substantial gains. The accompanying rise in post-quantum connections completing in a single round trip, from 0% to 99.2% (albeit with only 12.8% origin support), hints at a future where quantum-resistant cryptography becomes the norm. This mirrors a broader trend of proactive preparation for emerging threats, as explored in "[Is data from the Internet not refreshing?]" where connectivity issues can quickly expose vulnerabilities. The speed and reliability of these connections are paramount, particularly as data volumes continue to explode and AI’s reliance on real-time information intensifies.
The significance of this development extends beyond simply faster websites. It touches on the fundamental efficiency of the internet's infrastructure. Every millisecond saved in handshake latency contributes to a more responsive web experience, reduced energy consumption (due to fewer retransmissions), and improved overall network performance. This is especially important in the context of increasingly complex applications and the growing reliance on geographically distributed data centers. While the focus might be on optimizing for the needs of AI models, the benefits ripple outwards, improving the experience for all internet users. Cloudflare's approach highlights the power of continuous measurement and adaptive optimization, a methodology that's likely to become increasingly important as the internet continues to evolve.
Looking ahead, it will be fascinating to observe the adoption rate of post-quantum TLS configurations. The 12.8% support figure, while impressive growth from zero, still indicates a significant opportunity for improvement. As quantum computing capabilities advance, the pressure to migrate to quantum-resistant algorithms will only intensify. Furthermore, the underlying principles of per-origin measurement could be applied to other areas of network optimization, leading to further gains in performance and efficiency. The question becomes: how quickly can the broader industry adopt this data-driven, adaptive approach to infrastructure management, and what further, unseen optimizations are waiting to be discovered?

Cloudflare has replaced its static X25519 guess for origin TLS handshakes with per-origin measurement. HelloRetryRequests on scanned origins fell from roughly 52% to 3.7%, removing over 150 ms from p90 latency. Post-quantum connections completing in one round trip rose from 0% to 99.2%, though only 12.8% of origins support it.
By Steef-Jan WiggersRead on the original site
Open the publisher's page for the full experience