Cloudflare Argo Smart Routing explained

What Argo Smart Routing does

Argo Smart Routing picks faster network paths between Cloudflare data centers and your origin server. Most traffic between an origin and the internet follows whatever the default BGP routes offer, which is not always the shortest or least congested path. Argo uses Cloudflare's real-time view of network conditions to route requests around congestion and packet loss instead of through it.

The name has history: the service launched as Argo, and today Cloudflare describes it as one feature within its origin safeguard, Smart Shield. You still hear it called _Argo Smart Routing_ in the dashboard and API, and the mechanics are unchanged. Cloudflare learns from live crossing times and retries dropped requests on a faster path, so fewer requests stall behind a slow link.

The result is a faster time to first byte (TTFB) measured from the origin to the Cloudflare edge, which means faster full-page loads for users far from your origin. Cloudflare publishes an average in the thirty percent range for latency reduction; your mileage depends on how far your visitors are and how congested the default routes are. A site whose visitors share a region with the origin gains little, while one serving a global audience from a single origin can gain a lot.

How it works

Smart Routing runs inside Cloudflare's network. There is no code or configuration change on your origin:

• Cloudflare tracks the health of transit paths between data centers and your origin.
• When a request arrives, Argo routes it over the currently fastest available path.
• Congested or lossy routes get used less, and traffic shifts to better routes in near real time.
• The origin-to-edge TTFB data is also what the analytics graphs show, so you can compare before and after.

Because it is a network path decision, it helps most when the origin is far from the user or when the origin's ISP path is congested. It does not make your application faster, and it cannot compress responses or cache like the CDN does. It changes the route, not the server.

Cost and availability

Argo Smart Routing is a paid, per-zone add-on with metered usage. It is offered as part of:

Enterprise customers can preview the product on a non-contract basis. Activation requires a billing profile on the account.

Before you commit, establish the baseline. Argo helps only when TTFB from origin to edge is a real cost for your visitors, so measure that number for at least a week, then compare again after you enable it.

When it is worth enabling

The questions to work through:

• Do you have a real proportion of far-from-origin visitors? A global audience on a single origin is the clearest case; a local audience gains little.
• Is origin TTFB a real part of your LCP? If the HTML document arrives slow from across an ocean, a faster path helps that directly.
• Have you already done the free TTFB work? DNS set sensibly, TLS ready on both ends, static assets cached at the edge, and dynamic routes not blocked by your own cache settings. If those are done and close-by visitors are fast but far ones are not, the network path is the next lever.

Argo is the one setting that specifically attacks that last problem. If caching, DNS, or your own origin still sit undone, fix those first; they do not bill per request.

Enable and measure

1. In the dashboard, go to Speed > Optimisation (Smart Shield area) and open the Argo Smart Routing toggle.
2. Switch it on; the feature bills from the moment traffic runs through it.
3. Keep the setup for at least two weeks so the analytics have enough samples.
4. In the analytics view, compare TTFB before and after for your main far-geo segments.

The toggle switches off instantly, so the decision is reversible. The measured results are the only legitimate reason to keep it on. Its design partners are cache control for how long Cloudflare holds content and cache purge for forcing freshness when it matters.