Cloudflare halves DNS build delay with targeted zone builds and cuts peak memory by 85%
Cloudflare's Zone Builder now rebuilds only what a zone setting change provably touches, instead of whole zones that can hold more than 20 million records.
Cloudflare's Zone Builder now rebuilds only what a zone setting change provably touches, instead of whole zones that can hold more than 20 million records.
Two new optional headers, CloudFront-Viewer-ISP and CloudFront-Viewer-TLS-Details, are forwarded to the origin through an origin request policy.
A proxied DNS record can now point at an RFC 1918 or CGNAT address and reach the origin over the customer's Cloudflare One link; private-to-private traffic is targeted for a closed beta in early 2027.
18.2 million network-layer attacks were mitigated in July to September; CLDAP floods all but vanished while DNS amplification rose 215% and the US again tops the list of targets.
The ceiling rises 50% from 256 ACUs, only on Platform Version 4 and specific engine versions; existing PV4 clusters change the setting without downtime.
All three FIPS 203 parameter sets are supported; private keys stay in FIPS 140-3 Level 3 HSMs, and UAE, Bahrain and China Regions are excluded.
A closed beta of a geographically fenced key manager wraps decryption keys so only servers inside the chosen region can unwrap them, built to resist harvest-now-decrypt-later.
A new system turns observed crawler behaviour into an explainable trust band; scores are due on Radar later, and customers will be able to set their own threshold.
Announced on 15 October, the option sits between TRIM_HORIZON and LATEST; it works through the Kinesis adapter 2.5.0 or later, needs no new permissions and costs nothing beyond GetRecords.
Amazon CloudWatch can now send each log event from a pipeline to a different log group based on processed fields, and apply several parsers in sequence, such as a JSON envelope followed by Grok.