Two sites. One transparent circuit. A latency you can plan around.
A DPLC is a point-to-point Domestic Private Leased Circuit between two locations inside Pakistan. We deliver it as a transparent layer-2 service — your VLANs cross unchanged, your CE devices see each other on the same broadcast domain — over our DWDM and MPLS core.
What a DPLC actually delivers.
DPLC stands for Domestic Private Leased Circuit. It is a dedicated, symmetric, point-to-point connection between two customer sites within Pakistan, delivered as a layer-2 Ethernet service. The circuit carries customer traffic transparently — 802.1Q tags, LACP bundles, jumbo frames, multicast — without us touching layer 3.
On our network, DPLCs ride the DWDM core between Lahore, Faisalabad, Multan and Islamabad and the MPLS edge for the last metro hop. We build them as Ethernet pseudowires (PWE3) or EVPN-VPWS instances, policed to the contracted CIR with a small burst tolerance, and tagged for the appropriate QoS class. Latency is measured at handover and locked into the SLA — typically 4–6 ms for intra-Lahore, 9–11 ms Lahore↔Faisalabad, 16–19 ms Lahore↔Islamabad.
When a DPLC is the right answer.
If you need a known latency between two sites, transparent layer-2 semantics, and you don't want the routing complexity of a VPN — this is the service.
Bank branch to data centre
Tier-1 banks running core banking traffic from a Lahore branch to a primary DC in Lahore Cantt or a DR site in Islamabad with a contracted RTT.
Synchronous DR replication
Storage replication between primary and DR data centres where round-trip jitter must stay inside a tight envelope for synchronous writes.
Voice trunking between PBXs
Enterprise SIP trunks or legacy E1s carried as TDMoE between two PBX locations, with PDV controlled to under 2 ms.
Telco backhaul
MNO and fixed-line operators backhauling aggregated traffic between regional MSCs and core sites without burning their own long-haul.
Stock-trading / market connectivity
Brokerages and prop-trading desks running market-data feeds from PSX-co-located servers to head office over a deterministic L2 path.
Manufacturing SCADA
Factories in Sundar / Faisalabad industrial estates linking PLCs and SCADA gateways to control-room SOCs in Lahore on an isolated layer-2.
The numbers we put on the order form.
| Metric | Target | Notes |
|---|---|---|
| Service type | L2 EVPL / EPL | EVC tagged or untagged at handover |
| Capacity | 2M – 100G | Steps: 2/10/100M, 1/2.5/10/40/100G |
| Handoff | 1G/10G/100G LR/ER | LC/UPC SMF; copper 1G on metro |
| MTU | 9216 B | Jumbo frames supported by default |
| VLAN handling | All-tags / port-based | Q-in-Q on request |
| QoS classes | EF · AF31 · AF21 · BE | p-bit / DSCP preserved |
| Metric | Target | Notes |
|---|---|---|
| Availability | 99.95% (single) / 99.99% (1+1) | Per circuit, monthly basis |
| One-way latency, intra-Lahore | ≤ 3 ms | Measured to handover |
| One-way latency, LHE↔ISB | ≤ 9.5 ms | Protected path |
| Packet delay variation | ≤ 2 ms p99 | Across 5-min windows |
| Frame loss | ≤ 1 × 10⁻⁵ | Within CIR |
| MTTR | ≤ 4 h | P1 incident, on-net |
Turn-up timeline for a typical DPLC.
- 01
Site survey
Day 0 – 7. Confirm both endpoints, assess fibre entry, agree on handoff and rack space.
- 02
Provisioning
Day 7 – 18. CE install if needed, PE port allocation, EVC config, route selection.
- 03
Acceptance test
Day 18 – 24. RFC 2544 throughput, latency and loss test, SLA baseline document signed off.
- 04
Handover
Day 24 – 30. Service taken under NOC monitoring, ticket-tested, billing starts on cutover date.
21–30 days end-to-end is typical for on-net endpoints. Off-net endpoints add the last-mile build to the schedule.
What customers usually ask.
Is DPLC the same as a generic 'leased line'?
Is the DPLC actually layer-2 or is it tunneled IP?
Can I run my own routing protocol over it?
What's the smallest capacity you'll sell?
How do you guarantee latency?
Can the circuit be 1+1 protected?
Do you support cross-border DPLCs?
Is the billing PKR or USD?
Two addresses, one circuit — quoted in 48 hours.
Send us the two sites, the capacity and the protection class. We'll come back with a route, latency budget, and an SLA matrix you can hand to your risk team.