Western Europe
Sofia → Frankfurt on three diverse terrestrial routes; London via Frankfurt. Delivered through partners.
- FrankfurtEquinix FR5, NewTelco Frankfurt≈ 24.5 ms(partner)
- LondonTelehouse North≈ 35 ms(partner)
Sofia Connect · Network
One backbone, four corridors, three continents.
From Frankfurt and London through Sofia, across the Black Sea to the Caucasus, and onward to the Gulf. Our own equipment runs across Bulgaria; the international corridors are delivered through partners. Drawn the way engineers think about it: stations, lines and diverse routes.
- Points of presence
- 18
- Countries with PoPs
- 8
- Autonomous system
- AS47872
- Caucasus Cable System
- 1,182 km subsea, via partner
Path Builder
See exactly how your traffic travels
Pick two points on the network. You get the physical route, an indicative round-trip time and what we can deliver at each end.
- Own PoP
- Partner PoP
- Terrestrial route
- Protected parallel routes
- Subsea cable
- Partner leg
Tip: tap a station on the map to set the destination.
Indicative round trip
≈ 52.5ms
Fibre-path estimate, confirmed per order. Not a live measurement.
Route
Frankfurt
terrestrial · 24.5 ms · 3 protected routes
Sofia
terrestrial · 6 ms · 2 protected routes
Balchik
subsea · 15 ms · Caucasus Cable System, 1,182 km
Poti
terrestrial · 7 ms
Yerevan
Part of this route is delivered through partners; RTT indicative.
The corridors
Four international corridors, one national backbone, all homed on Sofia.
Aegean & Bosphorus
Sofia → Istanbul and Sofia → Athens, each on two protected terrestrial routes. Delivered through partners.
- IstanbulEquinix IL2≈ 12 ms(partner)
- AthensLamda Hellix≈ 12 ms(partner)
Black Sea & Caucasus
Sofia → Balchik on two protected routes, Caucasus Cable System to Poti, then terrestrial to Tbilisi. Yerevan on two routes (via Tbilisi and direct from Poti); Agarak via Yerevan on two routes. The whole corridor, including capacity on the Caucasus Cable System, is delivered through partners.
- BalchikPartner access to the Caucasus Cable System≈ 6 ms(partner)
- TbilisiCloud9 Data Center≈ 25 ms(partner)
- YerevanFirebird≈ 28 ms(partner)
- AgarakArmenia–Iran Border Landing Station≈ 32.3 ms(partner)
Gulf (partner)
Handed off to a long-haul partner. Route and latency quoted per request.
- DubaiDatamena DC1≈ 83 ms(partner)
Points of presence
Every PoP, what we deliver there and the indicative round trip from Sofia. At partner PoPs the service is delivered through a partner and we have no equipment of our own on site.
| PoP | Facility | Operated | IP Transit | Ethernet / L2VPN | DWDM Wavelengths | Dark Fiber | RTT from Sofia |
|---|---|---|---|---|---|---|---|
| SofiaBG | Equinix SO1 & SO2, Telepoint | Own | ● | ● | ● | ● | core |
| FrankfurtDE | Equinix FR5, NewTelco Frankfurt | Partner | ● | ● | ● | – | ≈ 24.5 ms |
| IstanbulTR | Equinix IL2 | Partner | – | ● | ● | – | ≈ 12 ms |
| AthensGR | Lamda Hellix | Partner | – | ● | ● | – | ≈ 12 ms |
| LondonGB | Telehouse North | Partner | – | ● | ● | – | ≈ 35 ms |
| TbilisiGE | Cloud9 Data Center | Partner | – | ● | ● | – | ≈ 25 ms |
| DubaiAE | Datamena DC1 | Partner | – | ● | ● | – | ≈ 83 ms |
| YerevanAM | Firebird | Partner | – | ● | ● | – | ≈ 28 ms |
| AgarakAM | Armenia–Iran Border Landing Station | Partner | – | ● | ● | – | ≈ 32.3 ms |
How we show latency
Round-trip times on this page are indicative fibre-path estimates, not live measurements. Each one is at or above the physical floor for its route: fibre length times roughly 10 µs per kilometre for the round trip. Exact figures are confirmed per order and depend on the route you buy.
The public-internet comparison uses typical server-to-server pings published by WonderNetwork (6–20 Oct 2026). Public routes between these cities often detour through Western Europe, which is exactly the gap a direct path closes.
Need a path that isn't on the map?
Tell us the two end points. Engineering replies with route options, diversity and lead time.