Punjab backbone,
routes published.
Fourteen PoPs across ten cities, ring-protected on the Lahore–Islamabad–Faisalabad triangle, with metro builds inside the major industrial estates. We publish per-segment latency, handoff specs and route diversity on request — not just on a sales call.
Cities and routes shown reflect the Q-2 2026 capacity plan. Tail-end towns are reachable via aggregation hops — see the city list below.
Where we are, in plain text.
| Code | City | Role | PoPs |
|---|---|---|---|
| LHE | Lahore | Core / DC | 4 |
| ISB | Islamabad / Rawalpindi | Core / Peering | 2 |
| FSD | Faisalabad | Core | 2 |
| MUL | Multan | Aggregation | 1 |
| GUJ | Gujranwala | Aggregation | 1 |
| SKT | Sialkot | Aggregation | 1 |
| BWP | Bahawalpur | Aggregation | 1 |
| SGD | Sargodha | Tail-end | 1 |
| SAH | Sahiwal | Tail-end | 1 |
| DGK | DG Khan | Tail-end | 1 |
The trunk segments.
- Length
- ~120 km
- RTT (p95)
- 1.2 ms
- Capacity
- 100/400G
- Length
- ~96 km
- RTT (p95)
- 1.1 ms
- Capacity
- 100/400G
- Length
- ~96 km
- RTT (p95)
- 1.1 ms
- Capacity
- 100/400G
- Length
- ~148 km
- RTT (p95)
- 1.3 ms
- Capacity
- 100/400G
- Length
- ~170 km
- RTT (p95)
- 1.4 ms
- Capacity
- 100/400G
- Length
- ~96 km
- RTT (p95)
- 1.1 ms
- Capacity
- 100/400G
- Length
- ~150 km
- RTT (p95)
- 1.3 ms
- Capacity
- 100/400G
- Length
- ~129 km
- RTT (p95)
- 1.2 ms
- Capacity
- 100/400G
- Length
- ~124 km
- RTT (p95)
- 1.2 ms
- Capacity
- 100/400G
- Length
- ~109 km
- RTT (p95)
- 1.1 ms
- Capacity
- 100/400G
- Length
- ~126 km
- RTT (p95)
- 1.2 ms
- Capacity
- 100/400G
RTT figures are p95 measured between PE devices on the route, last 90 days. Lengths are cable-route, not great-circle.
Where we land outside our own metal.
PKIX (Pakistan Internet Exchange) — Karachi
Lahore Carrier MMR (LL-MMR-04)
Islamabad Carrier MMR (ISB-MMR-09)
Karachi Submarine Landing
Open peering policy at PKIX and at our Lahore / Islamabad MMRs. Settlement-free PNI is available for networks that meet our public peering policy on PeeringDB. Submarine reach is delivered via partner LDIs at Karachi landings.
What we drop, what we sign, what we publish.
RPKI invalids dropped
Inbound and outbound. We publish ROAs for every prefix we originate.
MANRS-aligned
Anti-spoofing at customer edge, prefix filtering against IRR + RPKI, coordination contacts in PeeringDB.
Looking glass
Public read-only at lg.vcloud.com.pk. show route, traceroute and ping from any of our PE devices.
GRACEFUL_SHUTDOWN
RFC 8326 supported on all eBGP sessions. Signal pre-drains for planned maintenance.
Communities documented
Customer-facing communities for prepend, scope, blackhole and TE published in the welcome email.
IPv6 default
Every customer port comes up dual-stack. We don't price IPv6 separately.
Need a route, a ping window or a peering session?
Drop us the prefixes, the cities and the capacity. The same engineer who designs the route will be on the call when you scope it.