What it is
Argo Smart RoutingArgoCloudflare's smart-routing product that sends traffic over the fastest paths on our private backbone. uses real-time network intelligence to send your traffic across Cloudflare's private backbonebackboneCloudflare's own private, high-speed links between data centers β faster and less congested than the public Internet. along the fastest, least-congested paths β think of it as Waze for the Internet. Tiered CacheTiered CacheOrganizing Cloudflare data centers into layers so fewer requests ever reach your origin. adds a cachingcacheStoring copies of content so it can be served quickly without fetching or recomputing it every time. hierarchy that raises hit ratios and shields your originoriginYour own web server or host where your website actually lives. Cloudflare sits in front of it..
Why it helps the client
- Cuts latency by an average of ~30% by avoiding congested public Internet routes.
- More consistent performance β fewer slow outliers for distant users.
- Higher cache hit ratios and less origin load through Tiered Cache.
- Works for dynamic, non-cacheable traffic that a CDN alone can't accelerate.
Why they'd want it
- A single toggle that makes the whole site faster β no code, no re-architecture.
- Measurable latency wins, backed by per-request analytics.
- Speed for APIs and logged-in pages, not just static assets.
π¬ How it actually works
- Argo Smart RoutingArgoCloudflare's smart-routing product that sends traffic over the fastest paths on our private backbone. uses Cloudflare's real-time view of the whole Internet β latencylatencyThe delay before data starts transferring β essentially how long a user waits. Lower is better., congestion, and packet loss measured across the network β to pick the fastest path from the edgethe edgeβThe edgeβ means Cloudflare's servers spread across the world, close to your users β as opposed to one central data center. to your originoriginYour own web server or host where your website actually lives. Cloudflare sits in front of it., often riding Cloudflare's private backbonebackboneCloudflare's own private, high-speed links between data centers β faster and less congested than the public Internet. and avoiding congested public peering.
- It optimizes the 'middle mile' (edgethe edgeβThe edgeβ means Cloudflare's servers spread across the world, close to your users β as opposed to one central data center. β originoriginYour own web server or host where your website actually lives. Cloudflare sits in front of it.), which a normal CDNCDNContent Delivery Network β a worldwide set of servers that keep copies of your content close to users so pages load faster. can't touch. That's why it accelerates dynamic, uncacheable content and APIAPIApplication Programming Interface β how software talks to other software, e.g. a mobile app calling a server. calls, not just static assets.
- Tiered CacheTiered CacheOrganizing Cloudflare data centers into layers so fewer requests ever reach your origin. (included) arranges data centers into a hierarchy so cache misses are filled from an upper tier instead of your originoriginYour own web server or host where your website actually lives. Cloudflare sits in front of it., further cutting origin load and latencylatencyThe delay before data starts transferring β essentially how long a user waits. Lower is better..
- It's a single per-zone toggle, billed usage-based (a small monthly base plus per-GB), and the analytics tab shows measured latencylatencyThe delay before data starts transferring β essentially how long a user waits. Lower is better. reduction and time saved so the value is provable.
π Key terms on this page hover any underlined term anywhere on the site for its definition
- backbone
- Cloudflare's own private, high-speed links between data centers β faster and less congested than the public Internet.
- latency
- The delay before data starts transferring β essentially how long a user waits. Lower is better.
- Argo
- Cloudflare's smart-routing product that sends traffic over the fastest paths on our private backbone.
- Tiered Cache
- Organizing Cloudflare data centers into layers so fewer requests ever reach your origin.
- cache
- Storing copies of content so it can be served quickly without fetching or recomputing it every time.
- origin
- Your own web server or host where your website actually lives. Cloudflare sits in front of it.
- CDN
- Content Delivery Network β a worldwide set of servers that keep copies of your content close to users so pages load faster.
- API
- Application Programming Interface β how software talks to other software, e.g. a mobile app calling a server.
- cache hit ratio
- The percentage of requests served straight from cache β higher means more work kept off your origin.
- the edge
- βThe edgeβ means Cloudflare's servers spread across the world, close to your users β as opposed to one central data center.
Live demo walkthrough
5 stepsScreens below are annotated recreations of the Cloudflare dashboard. The numbered orange pin marks exactly where to click.
Select the website
Websites
Select a website to manage its configuration.
π Do this
Open the site you want to accelerate.
π¬ Say this
βI'll start on our demo site. Argo works on any traffic proxied through Cloudflare.β
Open Traffic β Argo
Traffic
Argo
π Do this
Expand Traffic in the sidebar and click Argo.
π¬ Say this
βArgo lives under Traffic. This is where we optimize the network path every request takes across Cloudflare.β
Enable Argo Smart Routing
Traffic
Argo
π Do this
Toggle Argo Smart Routing on.
π¬ Say this
βThis one switch routes traffic over our private fiber backbone instead of the congested public Internet. Average latency drops about 30%, and β crucially β it speeds up dynamic content a CDN can't cache.β
Turn on Tiered Cache
Traffic
Argo
π Do this
Enable Tiered Cache, then point out the Argo analytics below.
π¬ Say this
βTiered Cache organizes our data centers into a hierarchy, so your origin gets hit far less and cache hit ratio climbs.β
Show the latency win
Traffic
Argo
π Do this
Point to the Argo Analytics panel: latency reduction, requests smart-routed, time saved.
π¬ Say this
βAnd here's the proof to leave behind: a real ~31% average latency reduction, tens of millions of requests smart-routed, and hours of round-trip time saved in a single day. Argo is the rare toggle where you can measure the win the same afternoon you flip it.β