Edge Route & Latency Trace
PoP LatencyTrace edge routing, Cloudflare Ray ID, airport PoP data center location, and precise TTFB latency breakdown.
📖 Full Explanation
When users report latency anomalies, diagnosing whether the delay originates from DNS resolution, TLS negotiation, Cloudflare edge processing, or origin turnaround is essential. \1 sends high-resolution probes to dissect every phase of the HTTP connection.
⚙️ Command Options & Flags
| Option / Flag | Description | Default |
|---|---|---|
| -m, --method <method> | HTTP request method (GET, HEAD, POST) | GET |
| -H, --header <k:v> | Attach custom request header (repeatable) | - |
| -n, --count <num> | Number of trace probes to average latency | 3 |
🔬 Technical Corollary & Edge Mechanics
Connects directly to the domain and queries the edge diagnostic endpoint \1. Extracts client IP, colo (IATA airport code, e.g. BOM, DEL, LHR, SFO), TLS version, SNI verification, HTTP protocol (HTTP/2, HTTP/3), and measures sub-millisecond TCP handshake vs TLS handshake vs First Byte Arrival (TTFB).
🎯 Real-World DevOps Use Cases
Edge Data Center Verification
Confirm your traffic is routing to the nearest geographical Cloudflare point of presence.
Origin Latency vs Edge Overhead
Identify whether slow API responses are caused by backend database queries or edge caching rules.
💻 Live Output Simulation
$ cflare trace https://namishkumar.in ✔ Edge Trace Results: ┌──────────────────────┬──────────────────────────────────────────┐ │ Parameter │ Value │ ├──────────────────────┼──────────────────────────────────────────┤ │ Cloudflare Ray ID │ 8f293b4c102a9e-BOM │ │ Edge PoP Data Center │ BOM (Mumbai, India) │ │ Protocol │ HTTP/3 (QUIC) │ │ TLS Version │ TLSv1.3 (Cipher: AEAD-AES128-GCM-SHA256) │ │ DNS Resolution │ 1.8 ms │ │ TCP Handshake │ 8.2 ms │ │ TLS Handshake │ 12.4 ms │ │ Time to First Byte │ 38.6 ms (Total: 42.1 ms) │ └──────────────────────┴──────────────────────────────────────────┘