Why add a new Atlantis interconnect?
On a carrier-neutral backbone, depending on a single international egress creates both capacity and failure risk. The new Atlantis interconnect on KuzeyDC AS62425 adds another physical/logical path alongside existing local and global transit options, diversifying Istanbul-origin traffic toward the Balkans and Central Europe.
The Atlantis session is provisioned with the same security discipline—prefix filtering, RPKI validation and max-prefix limits. The goal is not “more ASNs,” but measurable gains in latency, jitter and failover time.
What the Istanbul–Sofia corridor unlocks
Bulgaria is a natural network bridge between Turkey and Central Europe. Dense interconnect facilities in Sofia (e.g. TELEPOINT and regional exchanges) create alternate paths to European destinations. Steering KuzeyDC customer traffic carefully over the Atlantis path:
- Reduces dependence on global transit alone (e.g. Cogent / RETN)
- Provides a second Balkan egress during maintenance or outages
- Enables shorter AS-paths to regional content and hosting networks
BGP and traffic engineering
Community policies define destination-aware preferences. Domestic CDN/peering priority (Cloudflare, Google, Meta) is preserved, while Balkan and Eastern European targets can be weighted toward Atlantis based on measurements.
- Track Sofia and European PoP RTT with synthetic probes
- Validate prefixes that shift to Atlantis during failover drills
- Report capacity with peak / 95th-percentile utilization
Result: colocation, dedicated and cloud customers gain a more resilient Balkan egress without single-carrier lock-in. For peering or cross-connect requests, use the Networking page or contact NOC.