Per-zone post-quantum visibility in Logpush and Log Explorer
Cloudflare added a new ClientTLSKeyExchangeGroup field to the http_requests Logpush dataset and Log Explorer, allowing customers to see what percentage of their traffic uses post-quantum key agreement. This enables building per-zone reports and breaking down adoption by hostname, path, user agent, or country.
Cloudflare Radar ↗ publishes global statistics on post-quantum key agreement adoption across all Cloudflare traffic, but until now customers had no way to see the same measurement scoped to their own zones. This is now possible because the http_requests Logpush dataset — also queryable in Log Explorer — includes a new ClientTLSKeyExchangeGroup field.
The field reports the TLS key exchange group negotiated on the client-to-Cloudflare connection, by group name. Post-quantum connections appear as X25519MLKEM768, and classical connections appear as X25519, P-256, or another named group. A value of UNK means the group could not be determined, and NONE means TLS was not used.
With this field, you can build per-zone reports showing what percentage of your inbound HTTPS traffic is protected by post-quantum key agreement, break the number down by hostname, path, user agent, or country, and push the data into your SIEM via any Logpush destination.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Workflows createBatch() now supports count or instances options
The createBatch() method now accepts an options object to create up to 100 Workflow instances in a single call, with support for creating instances by count with shared options or by providing individual instance configurations with unique IDs. The result provides details on created instances and errors, with improved error reporting for duplicate or existing IDs.
Cloudflare One Client for macOS 2026.8.2100.0
GA release for macOS Cloudflare One Client with improved split tunnel handling that no longer briefly blocks traffic during reconnects, support for non-RFC 1918 local IPv4 networks, faster connects with lower memory use, and numerous reliability fixes across DNS, reauthentication, and client stability.