Case Study: Dedicated Private Line and B2B Internet for a Technology Company in Prague — Smíchov

New Telekom s.r.o. delivered for a technology company based in an office complex in Prague — Smíchov three interconnected network services: guaranteed symmetrical B2B Internet 10 Gbit/s on FTTO fiber, a dedicated MPLS VPN private line between the Prague office and a colocation data center in Prague, and a CloudConnect private circuit to Microsoft Azure ExpressRoute outside the public internet — all under one contract, with a unified 99.9% SLA and 24/7 technical support from the New Telekom NOC in Prague. The project in Prague — Smíchov was completed 7 weeks from contract signing to full operation.

Why Prague — Smíchov and who was the customer?

Prague — Smíchov has undergone a fundamental transformation over the last decade, changing from an industrial district into one of the most significant office centers in Prague. Modern office complexes around the Anděl metro station (line B) and Prague Smíchov railway station now host branches of multinational corporations, technology companies, and regional headquarters of Central European holdings. Prague 5 — Smíchov is one of the best-covered locations in all of Prague in terms of fiber infrastructure — New Telekom's direct backbone routes pass through the entire area, enabling connection implementation without dependence on third parties. The customer — a Czech technology company with 85 employees developing a SaaS logistics platform — relocated to a new office in Prague — Smíchov and required enterprise-grade connectivity from day one of operation. The technical requirements stemmed directly from the nature of their business:

• The development team works daily with repositories on GitLab and AWS CodeCommit — symmetrical upload is critical for pushing large repositories
• The production infrastructure runs on Microsoft Azure in the West Europe region — latency and reliability of the connection to Azure directly impacts the SaaS platform's customer SLAs
• Customer data is stored for regulatory reasons in a private colocation data center in Prague — requiring a dedicated private line outside the public internet
• Backup connectivity in case of primary connection failure — failover within 60 seconds, ideally automatic

What New Telekom designed and why?

Architecture: Three layers of connectivity in Prague — Smíchov

New Telekom designed a three-layer architecture that exactly mirrors the customer's data flows — each layer serves a different purpose and has its own guaranteed parameters: Layer 1 — Guaranteed B2B Internet Prague (FTTO 10 Gbit/s): Primary internet connectivity for the development team, access to public cloud services (AWS, GitHub, npm registry, Docker Hub), corporate email, and general web traffic. No aggregation, no bandwidth sharing, with direct peering at NIX.CZ in Prague. Layer 2 — Dedicated Private Line MPLS VPN Prague: A dedicated Layer 3 MPLS VPN circuit between the office in Prague — Smíchov and the customer's colocation data center in Prague — physically separated from the public internet. Customer platform data, database replications, and backups never traverse the public internet infrastructure. Circuit capacity: 2 Gbit/s symmetrical, guaranteed 1:1. Layer 3 — CloudConnect Private Circuit to Microsoft Azure (ExpressRoute): A dedicated private line from the office in Prague — Smíchov via the New Telekom network and CloudConnect directly to Microsoft Azure ExpressRoute in the West Europe region — outside the public internet. For a SaaS company dependent on Azure, a private circuit is essential: guaranteed latency below 7 ms, consistent throughput, and isolation from public internet fluctuations. SD-WAN orchestration: All three layers are managed by SD-WAN logic on a Juniper NFX250 router — automatic traffic prioritization (QoS), failover switching between layers, and centralized monitoring from the New Telekom NOC in Prague.

What was physically delivered and installed in Prague — Smíchov?

FTTO Fiber Connection to the Office in Prague 5

New Telekom brought a dedicated OS2 Single-Mode fiber pair to the customer's office premises in Prague — Smíchov from the nearest distribution node of the New Telekom backbone network in Prague 5. The route, with a total length of 340 meters, used existing building technical ducts without requiring construction modifications. The fiber was terminated with LC/UPC connectors in the customer's data rack, with route attenuation measured at 1.2 dB using an EXFO FTB-720 OTDR. The connection simultaneously carries all three layers of connectivity — Internet, MPLS VPN, and CloudConnect — as logically separated VRF (Virtual Routing and Forwarding) instances on the backbone router. Physically, it is a single fiber route; logically, all three services are completely isolated.

Active Equipment — Juniper in Prague — Smíchov

• Juniper MX204 — customer backbone router with 400 Gbit/s capacity, three separate VRF instances for Internet, MPLS VPN, and CloudConnect, hardware support for BGP, MPLS, IPv4/IPv6 dual-stack, and QoS DiffServ with prioritization for VoIP (EF DSCP) and critical cloud traffic
• Juniper EX3400-24T — access switch with 24× GbE and 4× 10GbE SFP+ uplinks, PoE+ for IP phones and Wi-Fi access points
• Juniper NFX250 — SD-WAN CPE for orchestrating multiple access routes, automatic failover, centralized management via Juniper Contrail
• Fortinet FortiGate 200F — NGFW firewall with IPS, SSL/TLS inspection, and application control to protect the internet layer; separate security policies for MPLS VPN and CloudConnect layers (no SSL inspection needed on private routes)
• APC Smart-UPS 3000VA UPS — backup power for all active equipment for 60 minutes

Dedicated Private Line MPLS VPN Prague — Smíchov ↔ Prague Data Center

The MPLS VPN circuit was established as a Layer 3 VRF instance on the New Telekom backbone network — a dedicated virtual private circuit with guaranteed throughput of 2 Gbit/s symmetrical and latency below 2 ms between Prague — Smíchov and the customer's colocation data center in Prague. The circuit does not traverse the public internet at any segment of the route. Technical parameters of the MPLS VPN line in Prague:

• Protocol: BGP with the customer's private AS number, MP-BGP for both IPv4 and IPv6 prefixes
• QoS: three traffic classes — EF (Expedited Forwarding) for database replications, AF41 for backups, BE (Best Effort) for other traffic
• MTU: 9,000 bytes (jumbo frames) to maximize transfer efficiency for large database blocks
• Monitoring: NetFlow v9 export to the New Telekom NOC Prague, SNMP v3 polling every 30 seconds

CloudConnect Private Circuit to Microsoft Azure in Prague

The CloudConnect private circuit is implemented via New Telekom's own physical network and the cloudconnect.cz platform — a direct private connection from the customer's office in Prague — Smíchov to the Microsoft Azure ExpressRoute peering location in Prague (the CE Colo Prague data center), from where it continues to Azure West Europe (Amsterdam). Customer SaaS platform data travels from the application servers in Azure to Prague and back along a dedicated physical route — without traversing the public internet at any segment. Parameters of the CloudConnect circuit for the customer in Prague — Smíchov:

• Capacity: 1 Gbit/s symmetrical (upgradable to 10 Gbit/s without physical intervention)
• Latency Prague — Smíchov ↔ Azure West Europe: < 7 ms guaranteed
• Egress traffic from Azure via CloudConnect represents a significant saving compared to standard Azure egress rates
• Ingress traffic to Azure: free in all regions
• Management via the cloudconnect.cz portal — capacity changes in real-time without physical intervention

SD-WAN Failover Logic — Automatic Switching in Prague

SD-WAN orchestration on the Juniper NFX250 ensures automatic switching during the failure of any layer:

What results did the project in Prague — Smíchov deliver?

After the complete three-layer architecture was deployed in Prague — Smíchov, the customer's connection achieved the following measured parameters: The reduction in Azure egress traffic costs was immediately reflected in the monthly Azure billing — for a SaaS company transferring tens of TB of data monthly between application servers in Azure and its customers, this represents a direct financial saving that in many cases exceeds the cost of the CloudConnect circuit itself.

Why is Prague — Smíchov an ideal location for enterprise network infrastructure?

Prague 5 — Smíchov offers several specific advantages for B2B connectivity compared to other Prague locations: Density of fiber infrastructure in Prague 5: The area around Anděl, Nádražní, and Radlická streets is one of the best fiber-covered parts of Prague. Backbone routes of multiple operators — including New Telekom — pass through the entire Prague 5 area, enabling the implementation of redundant last mile routes via physically separate streets. Proximity to data centers in Prague: The distance from Smíchov to the main Prague colocation data centers (the Vinohrady, Žižkov, Holešovice areas) ranges from 3–8 km — the resulting latency of private MPLS VPN lines between Smíchov and data centers in Prague is therefore typically below 2 ms. For database applications requiring synchronous replication, this latency is critical. Connection to the New Telekom backbone network in Prague: The New Telekom distribution node in Prague 5 is connected to the New Telekom backbone network with direct access to NIX.CZ (Neutral Internet eXchange) in Prague — a neutral exchange point where direct Czech and international operators exchange traffic. The resulting latency from Prague — Smíchov to NIX.CZ is below 1.1 ms — a real measured value, not a marketing promise.

How CloudConnect changes the economics of cloud traffic for companies in Prague?

For companies in Prague running production infrastructure on Microsoft Azure, AWS, or Google Cloud Platform, the CloudConnect private circuit in 2026 is a standard tool for optimizing cloud costs — not a premium choice. Via the CloudConnect private circuit, egress rates are significantly more favorable compared to standard data transfer over the public internet. Combined with the fact that ingress traffic is always free, companies achieve real savings in total egress costs. At the same time, the CloudConnect private circuit from Prague eliminates the security risks associated with transferring sensitive customer data over the public internet — which for companies subject to GDPR (EU Regulation 2016/679) or NIS2 (Act No. 181/2014 Coll.) is a direct compliance argument, not just a technical preference. A detailed overview of CloudConnect technology is available at cloudconnect.cz — including tools for analyzing potential savings on egress traffic for your specific data volume.

Frequently Asked Questions about Dedicated Private Line and B2B Internet in Prague

What is the difference between a dedicated MPLS VPN private line and B2B Internet in Prague?

B2B Internet in Prague from New Telekom is a guaranteed symmetrical connection to the public internet infrastructure — with direct peering at NIX.CZ and international interconnection to Frankfurt. A dedicated MPLS VPN private line in Prague is a dedicated data circuit between two specific points (office ↔ data center, or office ↔ branch) over the New Telekom backbone network — data never uses the public internet. Both services can run simultaneously on a single physical fiber connection as logically separated layers.

What is CloudConnect and why is it advantageous for companies in Prague connected to Azure or AWS?

CloudConnect is a private MPLS VPN line operated over the New Telekom network and the cloudconnect.cz platform — a direct private connection from an office or data center in Prague to Microsoft Azure ExpressRoute, AWS Direct Connect, or Google Cloud Interconnect without traversing the public internet. For companies in Prague, it brings three specific advantages: guaranteed latency (typically < 7–9 ms to Azure West Europe or AWS eu-central-1), reduction of egress costs, and compliance with GDPR and NIS2 requirements for secure data transfer.

Can a redundant last mile for an MPLS VPN circuit be implemented in Prague — Smíchov?

Yes. The Prague 5 — Smíchov area has a dense fiber infrastructure enabling two physically separate routes via different streets. New Telekom standardly designs a primary fiber route and a secondary route taking a different street — excavation or failure on one route will not compromise the other. As a third level of backup, automatic failover to LTE-A Pro mobile connectivity via a New Telekom eSIM with switchover within 10 seconds is available.

How quickly can B2B Internet or MPLS VPN be deployed in Prague — Smíchov?

For locations in Prague 5 — Smíchov with an available New Telekom backbone route in the immediate vicinity of the building, the standard time from contract signing to deployment is 3–5 weeks for B2B Internet and 4–6 weeks for an MPLS VPN circuit. The project described in this case study was fully completed in 7 weeks (including all three layers simultaneously). For urgent cases, New Telekom offers a temporary solution via an LTE-A Pro backup connection with activation within 48 hours.

Does New Telekom offer dedicated private lines to other locations in Prague besides Smíchov?

Yes. New Telekom implements dedicated MPLS VPN private lines and B2B Internet across the whole of Prague — Prague 1 (city center, Old Town, Malá Strana), Prague 2 (Vinohrady, Nusle), Prague 3 (Žižkov), Prague 4 (Michle, Pankrác, Chodov, Krč), Prague 5 (Smíchov, Stodůlky, Zličín), Prague 6 (Dejvice, Bubeneč, Ruzyně), Prague 7 (Holešovice), Prague 8 (Karlín, Libeň, Kobylisy), and industrial zones near the D1, D5, D8, and D11 highways. New Telekom's own backbone fiber network in Prague covers all key office and industrial locations.

Conclusion

The project in Prague — Smíchov demonstrates how a three-layer network architecture — guaranteed B2B Internet Prague, a dedicated MPLS VPN private line Prague, and a CloudConnect private circuit to Microsoft Azure — simultaneously solves three different problems: development team performance, security, and cost-effectiveness of cloud operations. Companies in Prague dependent on cloud platforms (Azure, AWS, GCP) while also operating sensitive data in private data centers in Prague do not need to choose between security and performance — the right network architecture with a dedicated private line and a CloudConnect circuit offers both, with provably lower total costs than a purely internet-based solution. Do you have an office in Prague — Smíchov, Prague 5, or anywhere else in Prague and are looking for dedicated private lines, guaranteed B2B Internet Prague, or a CloudConnect private circuit to the cloud? Contact the New Telekom team via the contact page — we will perform a free site survey and design an architecture precisely for your data flows and cloud environment.

---

This case study was prepared by the expert team of New Telekom s.r.o. The technical parameters correspond to the state at the time of project handover. The customer's industry and number of employees are disclosed with the customer's consent; the exact address of the building is not disclosed for commercial reasons. The information corresponds to the technological state as of January 2026.

Technologies and Standards Used

• Juniper MX204, EX3400-24T, NFX250 — backbone router, access switch, SD-WAN CPE
• Fortinet FortiGate 200F — NGFW firewall with IPS and SSL/TLS inspection
• CloudConnect / cloudconnect.cz — private MPLS VPN circuit to Microsoft Azure ExpressRoute
• Microsoft Azure ExpressRoute — private circuit to Azure West Europe
• OS2 Single-Mode fiber cable — FTTO connection Prague 5
• EXFO FTB-720 — OTDR fiber route attenuation measurement
• BGP, MPLS, MP-BGP, VRF, IPv6, QoS DiffServ — network protocols
• NetFlow v9, SNMPv3, syslog — monitoring and oversight by New Telekom NOC Prague
• NIX.CZ — Neutral Internet Exchange Prague, direct New Telekom peering
• RIPE NCC — BGP AS and IP address space management
• 3GPP LTE-A Pro — backup mobile connectivity (New Telekom eSIM)
• EU Regulation 2016/679 (GDPR) — personal data protection during transfer
• Act No. 181/2014 Coll. (NIS2 transposition) — cybersecurity
• ČSN EN 50173-1 — structured cabling for commercial premises