Edge Location Coverage Calculator

Work out edge location coverage instantly with clear inputs, formula shown and shareable results.

About Edge Location Coverage Calculator

A latency target translates directly into a geographic service radius: 30 ms round trip allows about 3,000 km of fibre path, or roughly 2,000 km of straight-line distance after routing inefficiency. Coverage is then a population-geography question, and the users outside the target are the ones who determine whether additional edge locations are worth deploying.

Formula

Edge coverage

service radius km ~ target RTT / 2 x 200 (fibre km per ms); covered users = population x coverage share; users per location = population / locations

Worked example

With the default values below, Edge Location Coverage Calculator returns Users within the latency target of 164.00. Change any input above and every figure here is recalculated in your browser.

Inputs used

Edge locations deployedminimum 1: 40
User populationminimum 0.001 millions: 200 millions
Target latency to the nearest edgeminimum 0.1 ms: 30 ms
Share of users within the targetaccepts 0–100 %: 82 %

Results

Users within the latency target: 164.00 millions
Users outside the target: 36.00 millions
Average users per edge location: 5.00 millions
Fibre distance the target latency allows: 3,000 km

Step by step

1Values used
2Edge coverage
3Users within the latency target= 164.00 millions
4Users outside the target= 36.00 millions
5Average users per edge location= 5.00 millions
6Fibre distance the target latency allows= 3,000 km

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Do more edge locations always help?

Only where users are. Adding locations in already well-served regions gives negligible benefit, while one in an underserved region can move millions of users inside the target.

What limits edge deployment?

Cost per location, cache hit rate dilution as traffic spreads thinner, and operational complexity. Beyond a point, each location serves too little traffic to keep its cache warm.