Build rules based on TCP transport and latency
Cloudflare now provides two new request fields in the Ruleset engine that let you make decisions based on whether a request used TCP and the measured TCP round-trip time between the client and Cloudflare. These fields help you understand protocol usage across your traffic and build policies that respond to network performance. For example, you can distinguish TCP from QUIC traffic or route high latency requests to alternative origins when needed.
New fields
| Field | Type | Description |
|---|---|---|
cf.edge.client_tcp | Boolean | Indicates whether the request used TCP. A value of true means the client connected using TCP instead of QUIC. |
cf.timings.client_tcp_rtt_msec | Number | Reports the smoothed TCP round-trip time between the client and Cloudflare in milliseconds. For example, a value of 20 indicates roughly twenty milliseconds of RTT. |
Example filter expression:
cf.edge.client_tcp && cf.timings.client_tcp_rtt_msec < 100More information can be found in the Rules language fields reference.
Source: Cloudflare
Latest Posts
- MC1422074: Microsoft 365 Copilot Adds Option for OpenAI-Operated Models via New Admin Setting
- Amazon SageMaker HyperPod now supports AMI-based node lifecycle configuration for Slurm clusters using continuous provisioning
- MC1423103: Copilot Notebooks Adds Support for Markdown (.md) Files as Reference Sources
- MC1423108: Microsoft Entra Improves Authenticator Passkey Restore Experience on iOS
