INFRA Signal 545
Automatic Key Exchange: faster, post-quantum secure origin handshakes for 45 billion daily connections (and counting)
Cloudflare’s Automatic Key Exchange probes origin servers to select the fastest and most secure key agreement algorithm for TLS 1.3 handshakes, defaulting to post-quantum hybrid X25519MLKEM768 where supported.
This change reduces handshake latency by eliminating unnecessary HelloRetryRequests and accelerates the adoption of post-quantum cryptography without requiring manual configuration. For engineers, it shifts the burden of algorithm selection from guesswork to measurement, improving both performance and security at scale.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Automatic Key Exchange replaces static X25519 guesses with per-origin measurements, reducing HelloRetryRequests from 52% to 3.7%.
Post-quantum hybrid X25519MLKEM768 is now preferred automatically for origins that support it, with no manual setup required.
The system operates transparently for 45 billion daily connections, cutting p90 handshake latency by over 150 ms.
THE READ
What the cluster adds up to.
Cloudflare’s Automatic Key Exchange addresses a long-standing inefficiency in TLS 1.3 handshakes. The protocol requires the client to commit to a key agreement algorithm in the first packet, before the server has communicated its capabilities. Historically, Cloudflare defaulted to X25519 for all origins, a safe but suboptimal choice for roughly 30% of connections. By probing origins to learn their supported algorithms, the system now selects the fastest and most secure option on the first attempt, reducing the need for costly HelloRetryRequests.
The performance impact is measurable. With HelloRetryRequests dropping from 52% to 3.7%, the p90 handshake latency for origin connections has improved by over 150 ms. This is not just a marginal gain; for high-scale infrastructure, shaving round trips off every connection compounds into significant reductions in tail latency. The change is particularly valuable for global networks where network hops can add tens or hundreds of milliseconds to each retry.
Beyond performance, the system accelerates the adoption of post-quantum cryptography. Previously, enabling post-quantum key exchange required manual configuration on either the Cloudflare side or the origin server. Automatic Key Exchange removes this friction by defaulting to the post-quantum hybrid X25519MLKEM768 wherever the origin supports it. This is critical for mitigating harvest-now, decrypt-later attacks, where adversaries record encrypted traffic today to decrypt it once quantum computers become powerful enough to break classical encryption.
The trade-off is minimal. The probing mechanism adds negligible overhead, as it occurs asynchronously and is cached for future connections. The system is also backward-compatible; origins that do not support post-quantum algorithms or newer key exchange methods continue to work as before. However, the approach does rely on Cloudflare’s position as a reverse proxy, where it can observe and optimize the connection between itself and the origin. For engineers operating their own infrastructure, this highlights the value of centralized control in optimizing cryptographic handshakes at scale.
The broader implication is that security upgrades no longer need to wait for manual intervention. By automating the selection of post-quantum algorithms, Cloudflare is making progress toward its goal of a quantum-secure internet by 2029. This is a template for how large-scale infrastructure providers can drive adoption of new cryptographic standards without requiring action from individual operators. For engineers, it underscores the importance of designing systems that can adapt to new threats without disrupting existing workflows.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗