Bring Your Own IP
on your terms.
Announce your own IPv4 and IPv6 ranges from Zenlayer, under your own ASN, across every region you deploy in.
// teams shipping on Zenlayer
announced over BGP
Your IP space
203.0.113.0/24 · AS65000
Held at your RIR
Portable across providers
Sending reputation intact
01
Announce your own IP space under your ASN
Bring a prefix you already hold at your RIR — RIPE, ARIN, or another — and Zenlayer announces it over BGP under the ASN you specify. The IPs your users, allowlists, and upstreams already know don't change.
- Announced under your own ASN over BGP
- No renumbering, no NAT workarounds
- Routes from our backbone as it would from your own network
Your address space stays portable — take it to another provider whenever you want.
02
IPv4 and IPv6 BYOIP ranges
Bring IPv4 prefixes from /22 to /24 and IPv6 prefixes from /24 to /48 — submit both in a single request.
- IPv4 — prefixes from /22 to /24
- IPv6 — prefixes from /24 to /48
- Dual-stack from the start — no separate workflow for v6
IPv4 prefixes
/22 – /24
e.g. 203.0.113.0/24
IPv6 prefixes
/24 – /48
e.g. 2001:db8::/32
Dual-stack
v4 + v6
in a single request
Held at your RIR
RIPE · ARIN · …
you own the block
Submit
prefix + ASN
validate
RPKI + IRR
ownership
provably yours
Announced
under your ASN
03
Validated before it's announced
Before a prefix carries traffic it clears two independent ownership checks — RPKI and IRR — so the route announcement is provably yours and won't be filtered downstream.
- RPKI + IRR dual validation proves ownership
- Announced under your ASN once verified
- Attach to instances like any other address
04
Who BYOIP is for
The teams whose architecture depends on the IPs themselves — not just the compute behind them.
Consumer-VPN operators
Carry your own IP diversity across regions, not a provider's shared pool.
ISPs & networks
Keep portable address space as you move between providers.
Reputation / allowlist teams
Payment, mail, or partner integrations that can't afford to renumber and re-earn trust.
05
Bring it in with the API, SDKs, or CLI
Submit your prefix and ASN in one call — IPv4 and IPv6 together — and BYOIP runs the RPKI + IRR checks before it goes live. Drive it over the REST API, the Go and Node SDKs, or the CLI.
REST API
Go + Node SDKs
CLI
developer_console — bash
# Bring your own IPv4/IPv6 prefix into ZEC
$ curl -X POST https://console.zenlayer.com/api/v2/zec \
-H "Content-Type: application/json" \
-H "X-ZC-Action: CreateByoip" \
-H "Authorization: <your signed credentials>" \
-d '{
"byoipList": [
{
"cidrBlock": "203.0.113.0/24",
"asn": 65000,
"regionId": "asia-southeast-1",
"networkType": "BGPLine"
}
]
}'
# → [] validation failures (empty = RPKI/IRR passed)
BYOIP FAQ
Prefix lengths, ASN, and ownership validation.
What prefix lengths can I bring?
IPv4 prefixes from /22 to /24, and IPv6 prefixes from /24 to /48. You can submit IPv4 and IPv6 ranges in the same request.
Do I keep my own ASN?
Yes. Zenlayer announces your prefixes over BGP under the ASN you specify, so your routing identity stays yours.
How do you confirm I own the range?
Every prefix is validated against RPKI and IRR before it is announced, so the route is provably yours and won't be filtered downstream.
What do I need before I start?
A prefix you hold at your RIR (RIPE, ARIN, etc.) within the supported lengths, and the ASN you want it announced under.