Network
Argo Smart Routing review
Score: 6/10Real latency wins with an unpredictable bill.
The breakdown explains the score. It is not an average. How to read these.
Last updated
Argo routes traffic over Cloudflare’s private backbone to avoid internet congestion. It can make a noticeable difference to TTFB on cross-continent traffic, especially in regions with messy peering.
The problem is the pricing model: per-GB billing means your bill scales with your success, and a traffic spike (or an attack that gets through to origin-bound requests) shows up on the invoice. It’s one of the few Cloudflare products where the cost dashboards need regular attention.
Turn it on if origin latency matters and your traffic profile is predictable. If you serve heavy assets, do the math first. More aggressive caching may be better value.
Status page incidents
Published under Argo Smart Routing, plus incidents whose title names it.
- Last 3 years
- 10
- 2 from the title
- Major or critical
- 3
- Median time open
- 9.7 h
- Since March 2020
- 22
Counts what Cloudflare published, not what broke: time open is how long the status entry stayed open, and nothing before March 2020 is tracked at all. Incidents Cloudflare tagged against nothing but named in the title are counted too. The caveats in full.