This is an illustration, not a measurement.

This visualizer exists to compare how different Cloudflare Developer Platform services route a request — the shape of the path, the number of hops, and where state lives.

1. The locations drawn here do not represent Cloudflare's real points of presence, their count, or their placement. Cloudflare's network spans 335+ cities in 125+ countries; this map shows an approximate, possibly outdated subset.
2. Every latency figure is a simulated estimate, not a measurement. It is modeled from straight-line distance and invented per-service processing costs. Cloudflare does not publish per-service latency.
3. Service internals are simplified and in places invented — for example, Cloudflare does not publish where KV central storage lives or which cities have GPUs. Anything labelled "illustrative" is a stand-in chosen to make the diagram readable.
4. Region and jurisdiction boundaries shown here are approximations and are not an authoritative compliance boundary.

Do not use anything on this page for capacity planning, SLAs, latency budgets, or vendor comparison. For real numbers, measure your own workload.