Skip to content
VCloud
Menu
INTERNET · B2B ACCESS

Dedicated internet, sized for the network behind it.

Symmetric, uncontended internet over fibre to your office, branch or DC — sold by capacity, not by package. From 100 Mbps to 10 Gbps, with optional BGP, IPv6 dual-stack, and an SLA matrix that covers latency and packet loss, not just uptime.

100 M – 10 G symmetric 1:1 contention IPv4 + IPv6
N S W E AJK ISB Islamabad SKT Sialkot GUJ Gujranwala SGD Sargodha LHE Lahore FSD Faisalabad SAH Sahiwal MUL Multan DGK DG Khan BWP Bahawalpur RYK Rahim Yar Khan KHI Karachi VCLOUD · BACKBONE AS137492 · DWDM 100/400G NOC ONLINE · 24×7 CAPACITY · 1.6 TBPS UTILISATION · 48% CORE HUB CORE / AGG POP DWDM FIBRE 0 200 KM 400
OVERVIEW

Bandwidth that does what it says.

B2B Internet is dedicated internet access for organisations that treat connectivity as infrastructure, not a utility bill. Each circuit is sold at a committed CIR with no contention against other customers, delivered over our own fibre to the building, and handed off on an Ethernet port at the speed you ordered. We don't oversubscribe and we don't reshape the traffic.

The IP layer is built to be useful: a /29 of public IPv4 by default, /48 of IPv6, full reverse DNS delegation, and the option to run BGP if you want to bring your own AS and prefixes. For customers without their own AS, we offer a Public-PA assignment with portability inside our footprint. Routing is dual-stack, MTU 1500 to the internet edge, and 9000 inside our fabric for customers crossing into our DCs.

WHO BUYS IT

Five customer profiles we see most weeks.

01

SaaS / fintech engineering offices

Engineering-heavy companies with 50–500 staff in Lahore or Islamabad whose CI, video calls and customer support all live on the link.

02

Bank head offices and regional branches

Primary internet for branch offices, with the bank's own MPLS overlay running on top for transactional traffic.

03

Hospitals and large clinics

Telemedicine, PACS imaging upload, and EHR sync that need uncontended upstream during peak hours.

04

Universities and research centres

Campus-wide internet with the option to peer with academic networks and selectively rate-limit student traffic upstream of us.

05

Industrial / manufacturing HQs

Plants in Sundar, FIEDMC and the Multan industrial estate that run their ERP and SCADA monitoring across our access.

06

Embassies and missions

Closed-network sites that pair our internet with their own VPN concentrator and want nothing in between.

SPECIFICATION

The technical small print.

Service & addressing
Metric Target Notes
Capacity 100M – 10G symmetric 1:1 contention; CIR = port speed
Handoff 1G/10G LR LC/UPC Copper 1G on metro tail
IPv4 default /29 PA Larger blocks via RIPE LIR
IPv6 default /48 PA Per-customer subnet, BGP-tagged
Reverse DNS Full delegation Customer-managed zone
BGP (optional) Single or dual-session Bring your own AS + prefixes
Performance & SLA
Metric Target Notes
Availability 99.95% Single-feed; 99.99% on dual-PE
Round-trip to PKIX ≤ 8 ms From any Punjab PoP
Round-trip to LHR (London) ≤ 165 ms Via primary upstream
Packet loss ≤ 0.1% Monthly average within CIR
DDoS scrub trigger Auto + community-tagged RTBH 666 / scrub 100
MTTR ≤ 4 h P1 incidents
DEPLOYMENT

Turn-up timeline.

  1. 01

    Survey

    Day 0 – 5. Address check, fibre entry, building permits if required.

  2. 02

    Last-mile fibre

    Day 5 – 18. Microtrenching or duct pull, splice, ONT or pre-term fibre.

  3. 03

    Logical config

    Day 18 – 22. PE port, IP allocation, BGP session if requested, monitoring.

  4. 04

    Acceptance + go-live

    Day 22 – 28. Throughput test, latency baseline, billing starts on cutover.

Where existing on-net fibre reaches the building, turn-up is 5–10 business days. Off-net builds extend the schedule by the civils duration.

FAQ

Common pre-sales questions.

Is the bandwidth really 1:1 or are you shaping it?
1:1. The CIR equals the port speed. We do not shape, throttle by application, or oversubscribe at the access PE. The first hop where contention is even theoretically possible is at the upstream peering edge, and we run our peering well below 70% utilisation.
Can I bring my own ASN and IPs?
Yes. We'll run a single or dual eBGP session, accept your prefixes (we filter against IRR + RPKI), and announce them upstream tagged with our communities. We support RFC 8950 (IPv6 next-hop for IPv4) for customers who want a single-stack BGP session.
What about DDoS?
Volumetric attacks under 50 Gbps are mitigated on-net. Larger attacks are scrubbed via our upstream's wash-in-place service. RTBH community 65500:666 is honoured for customers who want to blackhole their own /32 or /128 during an attack.
How do you handle PTA-mandated blocks?
We comply with directed blocks at the edge as required by the regulator. We don't run intermediate filtering, deep packet inspection or selective slowdowns of customer traffic. Our compliance posture is documented on the compliance page.
Can I get one circuit terminated in two buildings (LAG / dual-feed)?
Yes — dual-PE handoff with LACP for active/active, or one primary + one standby with sub-second BGP failover. Both are quoted as a single logical service.
What's the longest term you offer?
1, 3 and 5-year terms. Three years is the most common; five-year customers get one unlimited capacity uplift inside the term as long as the access port can carry it.
How does pricing scale?
Per-Mbps cost falls steeply with capacity. A 1 Gbps circuit is roughly 4× the price of 100 Mbps, not 10×. Beyond 2 Gbps, pricing transitions to a port-based model with included transit and a 95th-percentile overage.

Tell us the address and the capacity.

We'll come back with a feasibility check, a price, and an estimated install date — usually inside two business days.