Global VPC
one network, every region.
A single private network that spans your regions. Place a subnet wherever your workloads run and reach them over private IP — no per-region VPC mesh to stitch together.
// teams shipping on Zenlayer
one private network
Global VPC
10.0.0.0/16
Los Angeles · 10.0.1.0/24
Tokyo · 10.0.2.0/24
Frankfurt · 10.0.3.0/24
01
One multi-region private network
Most clouds give you a VPC per region and leave you to peer them. On Zenlayer the VPC is global — create it once, put a subnet in each region your workloads run, and instances share consistent private addressing and routing.
- One VPC spans every region — subnets bind to regions within it
- Consistent private addressing and routing across geographies
- Add a region by adding a subnet, not a new network
No per-region peering to stand up and maintain as you add regions.
02
Connect your regions over the private backbone
Within one global VPC, link two regions over Zenlayer's private backbone with Cross-Region Bandwidth — traffic between your regions stays off the public internet.
- Region-to-region traffic over the private backbone
- Provision bandwidth between regions in the same VPC
- Size the inter-region link to the workload
Los Angeles
10.0.1.0/24
private backbone
Tokyo
10.0.2.0/24
IPv4 CIDR
10.0.0.0/16
your private block
Per-region subnet
/24
carved from the VPC
Private IPv6
optional
dual-stack
MTU
1300 / 1500 / 9000
jumbo frames
03
Dual-stack, sized to your network
Bring a private IPv4 block from the standard ranges, optionally enable private IPv6, and pick the MTU your workload needs.
- IPv4 from 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16
- Optional private IPv6 (dual-stack)
- MTU 1300, 1500, or 9000
MTU is set at creation — choose 9000 up front for jumbo frames.
04
Who Global VPC is for
Teams whose architecture spans regions and shouldn't have to hand-build the network between them.
Multi-region apps on one network
Global SaaS backends that need a single private network across the regions they run in.
Real-time & gaming control planes
Span regions without standing up and maintaining a per-region peering mesh.
Active-active across geos
Fintech and latency-sensitive workloads running in more than one region at once.
05
Build it with Terraform, the API, SDKs, or CLI
Declare the global VPC once and apply it — or drive the same workflow over the REST API, the Go and Node SDKs, or the CLI.
REST API
Terraform
Go + Node SDKs
CLI
developer_console — bash
# Terraform · zenlayer/zenlayercloud
resource "zenlayercloud_zec_vpc" "global" {
name = "global"
cidr_block = "10.0.0.0/16"
enable_ipv6 = true
mtu = 1500
}
➜terraform apply
Global VPC FAQ
Scope, cross-region connectivity, addressing, and MTU.
Is the VPC really global, or one per region?
Global. You create one VPC and place a subnet in each region your workloads run in — the VPC itself isn't bound to a single region.
How do instances in different regions reach each other privately?
They share the same global VPC, and Cross-Region Bandwidth carries traffic between regions over Zenlayer's private backbone instead of the public internet.
What CIDR ranges can I use?
A block within the standard private ranges — 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16.
Does it support IPv6, and can I set the MTU?
Private IPv6 is optional (dual-stack), and the MTU can be 1300, 1500, or 9000 for jumbo frames. MTU is fixed at creation.