Latency between our metros
Round-trip times on our own backbone, published in full. No form, no sales call.
City to city, round-trip
Values in milliseconds. Figures marked with a dot are direct corridors; the rest are the sum of the corridors on the shortest path, which you can see by hovering over the value.
| From / to | Amsterdam | London | Paris | Frankfurt | Milan | Marseille | Vienna | Sofia |
|---|---|---|---|---|---|---|---|---|
| Amsterdam | — | 5.40 | 8.20 | 5.75 | 14.05 | 18.40 | 16.65 | 27.65 |
| London | 5.40 | — | 7.10 | 11.15 | 19.45 | 17.30 | 22.05 | 33.05 |
| Paris | 8.20 | 7.10 | — | 8.40 | 16.70 | 10.20 | 19.30 | 30.30 |
| Frankfurt | 5.75 | 11.15 | 8.40 | — | 8.30 | 16.20 | 10.90 | 21.90 |
| Milan | 14.05 | 19.45 | 16.70 | 8.30 | — | 7.90 | 13.90 | 28.10 |
| Marseille | 18.40 | 17.30 | 10.20 | 16.20 | 7.90 | — | 21.80 | 36.00 |
| Vienna | 16.65 | 22.05 | 19.30 | 10.90 | 13.90 | 21.80 | — | 14.20 |
| Sofia | 27.65 | 33.05 | 30.30 | 21.90 | 28.10 | 36.00 | 14.20 | — |
Round-trip, measured between our edge routers in each metro. Add the latency of your own cross connect and equipment at each end.
Most carriers will give you a latency figure when you ask for one, on a route you already asked about. We would rather publish the whole table, because if you are choosing where to put a server or which metro to buy a port in, the numbers matter before the conversation starts.
The corridor figures are measured round-trip times on our backbone, not estimates from a map. Everything else in the matrix is the shortest path across those corridors, which is the path our routers select unless a fibre fault moves it.
Latency is a property of the route, so it changes when the route does. If a corridor is on a protection path during maintenance the figure will be higher until it returns. The control panel shows the current state of the corridors your services depend on.
The twelve measured paths
These are the physical corridors the matrix is built from. Each one runs on capacity we hold ourselves, with a diverse path available on the routes where we have one.
| Corridor | Round-trip |
|---|---|
| Amsterdam ↔ London | 5.40 ms |
| Amsterdam ↔ Frankfurt | 5.75 ms |
| Amsterdam ↔ Paris | 8.20 ms |
| London ↔ Paris | 7.10 ms |
| Paris ↔ Frankfurt | 8.40 ms |
| Paris ↔ Marseille | 10.20 ms |
| Frankfurt ↔ Milan | 8.30 ms |
| Frankfurt ↔ Vienna | 10.90 ms |
| Frankfurt ↔ Sofia | 21.90 ms |
| Milan ↔ Marseille | 7.90 ms |
| Milan ↔ Vienna | 13.90 ms |
| Vienna ↔ Sofia | 14.20 ms |
What they do and do not tell you
- These are backbone figures between our routers. Your own kit, cross connect and last mile add to them.
- A derived figure assumes the shortest path is available. During a fibre fault or planned work the traffic may take a longer corridor.
- Latency to a destination outside our network also depends on where we hand the traffic over, which is what Smart Routing decides.
- If you need a guaranteed figure on a specific route rather than a typical one, ask. We will tell you what we can commit to in writing.
Need a route that is not here?
We can quote latency on paths beyond our own corridors, including onward capacity from partners. Send us the two endpoints.
Ask about a route