DigitalOcean BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with DigitalOcean’s cloud infrastructure. DigitalOcean’s BYOIP feature lets you bring your own IPv4 network prefixes, provision them as Reserved IP ranges, and assign those addresses to Droplets using the same control panel, API, and CLI you use for standard Reserved IPs.
Provider Details
| Field | Information |
|---|---|
| Provider Name | DigitalOcean |
| Website | How to Provision a BYOIP Prefix | How to Assign BYOIP IPs | Reserved IP & BYOIP Features |
| ASN(s) | Primary network ASN: AS14061 (DigitalOcean network). BYOIP origin ASN for ROAs: AS393406 (must be authorized as origin in your RPKI ROA). |
| Regions Supported | BYOIP is implemented on top of Reserved IPs. Reserved IPv4 (and therefore BYOIP) is available in all DigitalOcean datacenters. DigitalOcean currently operates 13+ datacenters across nine regions (for example NYC, SFO, TOR, LON, FRA, AMS, SGP, BLR, SYD). See Reserved IP Availability and Regional Availability. |
| Support Contact | Support Center & Tickets | Contact / Sales | Report Abuse |
| Tech Article & Date | How to Provision a BYOIP Prefix (Docs, validated Sept 2025; last edited Dec 30, 2025) & BYOIP GA noted in Reserved IPs release notes (GA on 18 Sept 2025). See also product update blog: “Announcing per-sec billing, new Droplet plans, BYOIP, and NAT gateway preview” (Updated Feb 4, 2026). |
| BYOIP Scope | Provider-announced IPv4 prefixes only: you bring your own IPv4 prefix (/24–/18), create an RPKI ROA that authorizes AS393406 as origin, and DigitalOcean announces the prefix from the selected datacenter. Once provisioned, addresses are exposed as Reserved IPs assignable to Droplets via the standard Reserved IPs interface. |
| Supported Versions | IPv4 only for BYOIP. Supported network sizes from /24 (256 addresses) to /18 (16,384 addresses). Reserved IPv6 is supported as a separate feature, but BYO-IPv6 is not currently documented. |
| Supported Services | BYOIP prefixes are exposed as Reserved IP ranges and can be assigned to Droplets only. Reserved IPs (including BYOIP addresses) are region-specific and can only be attached to Droplets in the same datacenter. Reserved IPs are not supported directly on DigitalOcean Kubernetes worker nodes or load balancers; you typically use Droplets as the attachment point. Note: some DigitalOcean marketing/blog content mentions Kubernetes nodes, but the Reserved IP/BYOIP limits document describes assignment to Droplets. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | BYOIP currently supports IPv4 only, with network sizes from /24 (256 addresses) to /18 (16,384 addresses). Smaller than /24 or larger than /18 is not supported. IPv6 BYOIP is not documented; IPv6 is supported only via standard Reserved IPv6 addresses. |
| ASN Ownership Required | No customer ASN required. DigitalOcean originates your IPv4 prefix on its own infrastructure. You must create an RPKI Route Origin Authorization (ROA) that lists ASN 393406 as the authorized origin ASN for the prefix. |
| IRR / Route Objects | IRR / RADb route objects are not explicitly required in the documented flow. Proof of control is based on: • An X.509 certificate you generate and embed into your prefix’s RIR RDAP/WHOIS records, and • A valid RPKI ROA authorizing AS393406. DigitalOcean validates ownership via these cryptographic and registry records. |
| ROA or LOA | ROA required. You must configure a Route Origin Authorization (ROA) at your RIR for the prefix, authorizing AS393406 as origin. LOA: Not mentioned in the official docs; the process is based on RIR records + X.509 certificate + ROA rather than a traditional LOA. |
| RIR Limitations | Your IPv4 prefix must be registered with one of the five RIRs: ARIN, RIPE NCC, APNIC, AFRINIC, or LACNIC. You must have direct control and update authority for the prefix’s RIR records, including the ability to add RDAP remarks/description fields and to create/manage the RPKI ROA. |
Step-by-Step BYOIP Process
Estimated Setup Time:Provisioning requests are reviewed within up to 7 days after submission, plus normal BGP propagation once advertisement is enabled.Tested By Us:Not yet
A) BYOIP provisioning (bringing your IPv4 prefix into DigitalOcean)
Request BYOIP access from the Reserved…
Verify you control an IPv4 prefix
Generate a private ECC or RSA…
Embed the encoded X
Create an RPKI ROA for the…
Use doctl or the API to…
After the prefix status becomes Active,…
In Networking → Reserved IPs, BYOIP…
Respect platform limits
only IPv4 is supported; the first two IPs of each BYOIP subnet are reserved; and each Droplet can have at most one Reserved IP or BYOIP address attached at a time.
Update DNS and application configuration to…
If you later retire the range,…
1
Request BYOIP access from the Reserved…
Request BYOIP access from the Reserved IPs page in the DigitalOcean control panel (Networking → Reserved IPs → Request access).
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Reserved IPs (including BYOIP addresses) are free when assigned to a Droplet. Unassigned Reserved IPv4 addresses cost per hourly basis. |
| Bundled or Standalone | BYOIP is fully integrated with the Reserved IPs feature. BYOIP prefixes use the same control panel, API, CLI, pricing model, and limits as standard Reserved IPs; there is no separate BYOIP SKU. |
| Traffic/Peering Restrictions | Reserved IPs and BYOIP addresses are region-specific resources and can only be assigned to Droplets within the same datacenter. Each BYOIP prefix is bound to a single datacenter; multi-region announcement of the same prefix from multiple locations is not documented. Only Droplets can receive BYOIP addresses; reserved IPs (including BYOIP) cannot be attached directly to Kubernetes worker nodes or load balancers. |
| Other Limitations | BYOIP supports IPv4 only, prefix sizes /24–/18. The first two IP addresses in each BYOIP subnet are reserved by the platform and cannot be assigned. A Droplet can have at most one Reserved IP or BYOIP address. BYOIP prefixes can only be assigned within the chosen datacenter and cannot be moved between regions without reprovisioning and coordination with DigitalOcean. Maintaining valid RPKI ROAs and RIR RDAP certificate records is required for ongoing service. |