Network Tools
Latency Reference
Indicative round-trip times between our Points of Presence, with the route each one takes. Fibre-path estimates, not live measurements.
From
From Sofia
Select a destination for the route.
| Destination | Route | RTT |
|---|---|---|
| — | ≈ 2 ms | |
| — | ≈ 2 ms | |
| — | ≈ 3 ms | |
| — | ≈ 3 ms | |
| — | ≈ 3 ms | |
| — | ≈ 5 ms | |
| —(via partner) | ≈ 5 ms | |
| —(via partner) | ≈ 6 ms | |
| —(via partner) | ≈ 6 ms | |
| —(via partner) | ≈ 12 ms | |
| —(via partner) | ≈ 12 ms | |
| —(via partner) | ≈ 24.5 ms | |
| Balchik → Poti(via partner) | ≈ 25 ms | |
| Balchik → Poti(via partner) | ≈ 28 ms | |
| Balchik → Poti → Yerevan(via partner) | ≈ 32.3 ms | |
| Frankfurt(via partner) | ≈ 35 ms | |
| Balchik → Poti → Tbilisi(via partner) | ≈ 83 ms |
Sorted by round-trip time
Plovdiv
2 ms
Montana
2 ms
Stara Zagora
3 ms
Pleven
3 ms
Blagoevgrad
3 ms
Burgas
5 ms
Varna
5 ms
Balchik
6 ms
Dobrich
6 ms
Istanbul
12 ms
Athens
12 ms
Frankfurt
24.5 ms
Tbilisi
25 ms
Yerevan
28 ms
Agarak
32.3 ms
London
35 ms
Dubai
83 ms
How to read these numbers
Round trip, not one-way
Every figure is a round-trip time (RTT): there and back on the fibre path, which is what ping and most SLAs report.
Estimated from the route
Values come from the physical route and fibre length (about 10 µs per km round trip). They sit at or above that physical floor.
Confirmed per order
Your exact latency depends on the route and protection you buy. Engineering confirms it in the quote. For live status, contact the NOC.
Need a latency figure you can put in a contract?
Tell us the two end points. Engineering replies with the route, protection options and a committed latency.