🌐 NETWORK · IaaS · ELASTIC IP

One static IP. Every workload it can ever serve.

QCloud Elastic IP is a static public IPv4 address you allocate once and reassign in seconds — to any ECS, ELB, NAT gateway, or VPN, across KHI-1 and ISB-1. Hosted inside Pakistan, billed in PKR, with built-in DDoS protection and BYOIP support.

🛡️ Tier-3 Certified · 🇵🇰 100% Data Residency · ⚡ 99.999% SLA · 💸 PKR billing

LIVE IP POOL · KHI-1 24 / 4,800
203.135.12.40
203.135.12.41
203.135.12.42
203.135.12.43
203.135.12.44
203.135.12.45
203.135.13.40
203.135.13.41
203.135.13.42
203.135.13.43
203.135.13.44
203.135.13.45
203.135.14.40
203.135.14.41
203.135.14.42
203.135.14.43
203.135.14.44
203.135.14.45
203.135.15.40
203.135.15.41
203.135.15.42
203.135.15.43
203.135.15.44
203.135.15.45
203.135.12.42 → ecs-web-01 ✓ 203.135.12.43 detached 203.135.12.44 → elb-prod ✓ 203.135.12.45 reattached in 0.4s BYOIP block 203.135.50.0/24 advertised ✓ 203.135.12.42 → ecs-web-01 ✓ 203.135.12.43 detached 203.135.12.44 → elb-prod ✓ 203.135.12.45 reattached in 0.4s BYOIP block 203.135.50.0/24 advertised ✓

LIVE · QCLOUD EIP POOL · 12-MONTH ROLLING

0+
IP addresses allocated across QCloud
< 0ms
Median attach / detach time
0%
EIP availability SLA
0
Bytes ever leaving Pakistan

Numbers reflect QCloud EIP production telemetry · KHI-1 + ISB-1

WHAT IS EIP

A public IP address you own, hold, and move at will.

Unlike the ephemeral public IPs that come and go when an instance restarts, a QCloud Elastic IP is allocated to your account and stays yours until you release it. Attach it to any cloud resource. Detach when you want. Move it to a different workload, a different availability zone, or a different VPC — without changing a single DNS record on the outside world.

  • Static IPv4 — allocated once, yours until released
  • Reassignable across ECS, ELB, NAT, VPN, secondary ENI
  • Cross-AZ — survives availability-zone failover
  • BYOIP supported — bring your own /24 from APNIC
ecs-web-01 primary EIP 203.135.12.42 ecs-web-02 standby ✓ failover complete · 0.4s

One IP. Zero DNS changes. Same endpoint your customers already know.

FOUR PROMISES

Static where it matters. Elastic where it counts.

Static.

Once you allocate it, the IP is yours — no recycling, no surprise renumbering, no overnight changes.

Reassignable in seconds.

Detach from one resource and attach to another with one click or one API call. Effective immediately.

DDoS-protected by default.

Every EIP ships with always-on basic DDoS scrubbing at the edge. Enhanced anti-DDoS on demand.

Sovereign.

Allocated from Pakistan-resident pools, advertised from KHI-1 and ISB-1, never routed offshore.

FLEXIBLE BILLING

Pay by the hour. Pay by the gigabyte. Or hold the IP forever.

Three billing models. One static IP. Switch any time — no IP change, no DNS update.

Bandwidth:
Estimated:PKR ~ 3,650 / mo
≈ PKR 5.00 / hr
⚡ Pay-by-Bandwidth → predictable peak traffic, transactional APIs 📊 Pay-by-Traffic → variable workloads, dev/staging, periodic batch 📅 Subscription → 24/7 production with stable load, ~20% cheaper

Estimates are illustrative. Open the full calculator for an exact PKR quote.

Open pricing calculator →

WHERE IT GOES

Six attach points. One reassignable address.

ECS Instance
Elastic Load Balancer
NAT Gateway
VPN Gateway
Secondary ENI
HAVIP
EIP · 203.135.12.42

Move the EIP between any two of these in seconds — no DNS propagation, no customer-side change.

BUILT FOR

Six patterns we see in every Pakistani EIP rollout.

  1. 01

    Production failover

    Keep a hot standby behind the same IP. When the primary drops, the EIP moves in under a second; customer-side endpoints never change.

  2. 02

    DNS-free deployments

    Use the IP directly in API integrations, partner firewall allow-lists, and SBP-mandated IP whitelisting — no DNS dependency.

  3. 03

    VPN concentrators

    Pin your IPsec / WireGuard endpoint to a single static address so remote offices and branches never lose their tunnel.

  4. 04

    NAT egress fixed IP

    Give an entire VPC's outbound traffic one predictable public IP — ideal when a payment processor or partner only whitelists known IPs.

  5. 05

    Migration from on-prem

    Bring your existing /24 to QCloud (BYOIP) and keep every external integration intact — no IP change for partners, customers, or DNS.

  6. 06

    Multi-tenant isolation

    Assign one EIP per tenant in shared SaaS infrastructure for clean per-customer firewalling, logging, and traffic shaping.

FUNCTIONS

Three things every EIP does for you.

VPC EIP Internet

Internet egress, controlled.

EIPs serve as the egress point for any cloud resource that needs to reach the public internet. Flexibly associate and disassociate them from VMs, NAT gateways, or load balancers as your traffic patterns change. One IP. One audit trail. One firewall allow-list to maintain on the outside world.

Reassign in seconds — not minutes.

Detach an EIP from one resource and attach it to another through the console, REST API, or Terraform. The change takes effect immediately — no propagation delay, no DNS update, no customer-side reconfiguration. Bandwidth changes apply just as fast.

ecs-prod-01 ecs-prod-02 EIP · 0.4s
EIP Zone A Zone B

High availability by design.

Every EIP sits on QCloud's high-availability gateway fabric, which eliminates single points of failure and supports automatic cross-zone failover. Pair it with the ECS snapshot function and you have a complete recovery posture without scripting a single line of glue code.

THE LIFE OF AN EIP

Allocate. Attach. Reassign. Repeat.

1

Allocate

Reserve a static IPv4 from QCloud's pool or bring your own (BYOIP).

2

Configure

Set bandwidth cap, choose billing model, optionally enable enhanced DDoS.

3

Attach

Bind to any ECS, ELB, NAT, VPN, or secondary ENI in your VPC.

4

Reassign

Detach and re-attach to a different resource at any time. Instant.

5

Release

Return the IP to the pool when no longer needed. Or hold indefinitely.

$ qcloud eip allocate --region khi-1 --bandwidth 100
  ✓ allocated 203.135.12.42 · 0.3s
$ qcloud eip attach --eip 203.135.12.42 --target ecs-web-01
  ✓ attached · effective immediately
$ qcloud eip detach --eip 203.135.12.42
  ✓ detached · IP held in account

BRING YOUR OWN IP

Migrate to QCloud. Keep your IP reputation.

Already own a /24 from APNIC, ARIN, or RIPE? Bring it to QCloud and keep every existing integration, allow-list, and IP-bound certificate intact.

Before BYOIP

🏢 → 📦 → On-prem /24 (your ISP)
  • • Customer firewalls allow-list your IPs
  • • Partner integrations bound to specific addresses
  • • SSL certs pinned to IPs in legacy systems
  • • Reputation built up over years

After BYOIP on QCloud

🇵🇰 → 📦 → Same /24 (QCloud AS)
  • Same IPs — zero customer-side change
  • Allow-lists, integrations, certs all untouched
  • Reputation preserved end-to-end
  • Cost: zero per-IP hourly fee on BYOIP ranges
/24 prefix supported APNIC / ARIN / RIPE accepted ROA / RPKI validated 24–72h onboarding
EIP VS NATIVE PUBLIC IP

Why every production workload deserves an EIP.

Capability Native public IP QCloud Elastic IP
Persistence on instance restart✕ May change✓ Same IP always
Can be detached and reused✕ Tied to instance✓ Reassignable in 0.4s
Survives instance termination✕ Released✓ Held in your account
Cross-AZ failover✕ No✓ Native
BYOIP support✕ No✓ /24 prefixes accepted
Bandwidth adjustable on the fly✕ Fixed✓ Up to 1 Gbps, instant
Built-in DDoS protectionBasic✓ Always on + Enhanced option
Billing modelBundled✓ PAYG / Traffic / Subscription
Data residencyRegion-bound✓ 100% Pakistan-resident

Already on a native public IP? Migrate to EIP in under 60 seconds — no IP change, no downtime.

SECURITY

Three layers of protection. All on by default.

workload Enhanced anti-DDoS · Tbps-level Always-on basic DDoS Stateful security groups
  1. Stateful SGs — Define inbound/outbound rules at the resource level. EIP traffic obeys your SG.
  2. Basic DDoS scrubbing — Every EIP includes always-on volumetric DDoS protection at the network edge. No charge, no setup.
  3. Enhanced anti-DDoS — Opt-in for terabit-class mitigation, application-layer protections, and traffic profiling. Enabled at allocation time.
FREQUENTLY ASKED

Everything you wanted to know before you allocate your first EIP.

The default public IP is ephemeral — when you restart, stop, or replace the instance, the IP can change. An EIP is a static address allocated to your account; it persists until you explicitly release it. You can also move it between resources, which the default public IP cannot do.

Under 400 ms in 99% of cases. The change is propagated through QCloud's gateway fabric instantly — no DNS update, no propagation wait.

Three models — Pay-by-Bandwidth (fixed peak Mbps, hourly in PKR), Pay-by-Traffic (per GB egress), and Subscription (monthly/yearly, ~20% cheaper). BYOIP ranges have no per-IP fee.

Yes, a small hourly hold fee applies to EIPs not associated with any running resource, to encourage efficient pool usage. BYOIP IPs are exempt.

Yes — every EIP ships with always-on basic DDoS scrubbing. Enhanced anti-DDoS (Tbps-class) is available as an opt-in at allocation time.

Yes. If you released an EIP within the past 7 days, you can request the same IP back. For longer guarantees, use BYOIP.

Default quota is 20 EIPs per region. Quota increases are approved on request — typically same business day.

ECS instances, Elastic Load Balancers, NAT gateways, VPN gateways, secondary ENIs, and HAVIPs — all inside a QCloud VPC.

Yes. We accept /24 prefixes registered with APNIC, ARIN, or RIPE. Onboarding involves a ROA / RPKI update and typically completes in 24–72 hours.

From PTCL's Tier-3 / Rated-3 certified data centers in Karachi (KHI-1) and Islamabad (ISB-1). Your traffic never leaves Pakistan unless your application explicitly sends it outbound to the internet.

🇵🇰 PAKISTAN'S STATIC IP LAYER

Allocate your first EIP — on the house.

Get $100 in QCloud credit, a 1-month free trial of EIP, VPC, and ECS, and a real network architect on the call from day one. BYOIP onboarding included for teams migrating from AWS, Azure, or on-prem.

Scroll to Top