What is the challenge?
Why does dynamic content still feel slow even when you have a CDN?
CDNs help cached content. But every login, search, and API call still has to reach your origin — and BGP routing across the public internet is famously suboptimal. A request from Sydney to your origin in Virginia might cross three transit providers, hit congestion in Singapore, and take 400ms more than it needed to. Caching can't fix that, because the response isn't cacheable.
Architecture
How it fits together
Diagram coming soon
Architecture diagram for this solution will be added here.
Cloudflare's Solution
How Cloudflare solves it
- Real-time network telemetry. Cloudflare measures latency, packet loss, and congestion between every pair of edge locations continuously. Each path is scored in real time.
- Fastest path, not shortest path. When a request would normally cross congested transit, Argo routes it through Cloudflare's private backbone instead — often via 2–3 edge locations the public internet wouldn't choose.
- Origin-to-Origin acceleration. Works for HTTP, WebSocket, gRPC, and any TCP traffic going through Cloudflare. Especially impactful for cache-miss content, API calls, and long-distance origin connectivity.
- Measured improvement. Across Cloudflare's customer base, Argo delivers ~30% TTFB improvement on uncached requests on average — with much larger wins on specific long-haul routes.
- One toggle, no code changes. Enable Argo in the dashboard. No origin config, no SDK, no DNS changes.
FAQ
Common questions
How is this different from regular Cloudflare CDN routing?
The standard CDN routes you to the closest edge (anycast). From there to your origin, traffic goes over the public internet via standard BGP. Argo replaces that origin-bound leg with intelligent backbone routing — same closest-edge for the user, much faster path from there to your origin.
Does Argo work with Smart Routing for connections that aren't cached?
Argo specifically targets cache-miss traffic — that's the whole point. Cached requests don't need it (they never reach the origin).
What about Argo Tunnel — is that the same thing?
No. Argo *Tunnel* (now called Cloudflare Tunnel) is a different product: it's an outbound connector from your origin that creates a secure private link to Cloudflare without opening firewall ports. Argo *Smart Routing* is the path-optimization product. They can be used together.
Will Argo help with WebSocket / long-lived connections?
Yes. WebSockets and gRPC streams benefit too — the route stays optimized for the lifetime of the connection. WebSocket clients in Asia connecting to origins in US/EU see substantial improvements.
Let's Test!
Try it live
Demo coming soon
An interactive demo for Argo Smart Routing is being built. In the meantime, check the "Dive Deeper" section below for the official docs and product blogs.
Dive Deeper