Leaseweb BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Leaseweb infrastructure. Leaseweb supports provider-announced BYOIP via its IP Announcement (IPAN) service, where your IPv4/IPv6 prefixes are originated from Leaseweb’s ASNs, and optionally Private AS BGP, where Leaseweb assigns you a private ASN for dynamic routing within your environment (while prefixes are still advertised from Leaseweb ASNs).
Provider Details
| Field | Information |
|---|---|
| Provider Name | Leaseweb |
| Website | IPv4 address assignment & IP Announcement summary | IP Announcement (IPAN) & Private AS BGP | Peering policy |
| ASN(s) | Global network ASNs: Primary global network ASN - AS16265 (LeaseWeb Network). Related regional ASNs (per PeeringDB): North America - AS7203, AS30633, AS394380, AS395954, AS32613 Europe - AS28753, AS60781, AS205025, AS205544 Asia-Pacific - AS59253, AS133752, AS136988, AS134351 CDN - AS60626 |
| Regions Supported | IP Announcement is available from Leaseweb locations in NL, DE, US, UK & APAC (per IPAN docs), mapped onto their global backbone (e.g. Amsterdam, Frankfurt, London, Ashburn/Washington DC, San Jose, Dallas, Singapore, Hong Kong, Sydney, Montreal and others). |
| Support Contact | Contacting Customer Care (tickets via Customer Portal, email, phone, live chat) | Support overview |
| Tech Article & Date | IPv4 address assignment and usage guidelines (IP Announcement summary) & IP Announcement and Private AS BGP. |
| BYOIP Scope | Provider-announced only: your IPv4/IPv6 prefixes are advertised from Leaseweb ASNs (IP Announcement). Announcing under your own public ASN is not supported. Optional Private AS BGP gives you a private ASN and BGP session in private environments (racks / VMware), but prefixes are still originated by Leaseweb ASNs. |
| Supported Versions | IPv4 & IPv6 prefixes supported for IP Announcement (minimum /24 IPv4 and /48 IPv6 for external advertisement). |
| Supported Services |
IP Announcement (BYOIP) supported for: Dedicated Servers, Dedicated Racks, Colocation Racks, Elastic Compute, VMware Single Tenant vSphere & VMware HCI, VMware vCloud. Not supported (per docs): Public Cloud, VPS, Shared Colocation units. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size |
External announcement (IPAN): minimum /24 IPv4 and /48 IPv6 to be advertised to upstream providers. Leaseweb prefers aggregated announcements; they can internally split space within the same data center down to approximately /26 IPv4 per rack for routing, while still advertising larger aggregates externally. |
| ASN Ownership Required |
Public ASN: not used for IP Announcement (prefixes are always originated from Leaseweb ASNs). Announcing under your own public ASN is not supported. Private AS BGP: Leaseweb assigns you a private ASN (64512-65534) and establishes BGP sessions; full internet routing table is not provided (default route only). |
| IRR / Route Objects |
For IP Announcement, Leaseweb requires an accepted authorization method and correct IRR data: - For RIPE space, delegate mnt-routes to Leaseweb’s maintainer so they can create route objects.- For other RIRs/IRRs (ARIN, RADB, APNIC, etc.), ensure appropriate route records exist for the prefixes and the chosen Leaseweb location (NL, DE, US, UK, APAC). |
| ROA or LOA |
LOA: Required if the organization/person requesting IP Announcement does not directly own the prefix (Letter of Authorization from the RIR holder). RPKI/ROA: Not strictly mandated in docs but strongly recommended to ensure global validation and to align with best practices. |
| RIR Limitations |
Prefixes must be properly registered with a major RIR (RIPE, ARIN, APNIC, etc.) and meet Leaseweb validation and policy requirements. No specific per-RIR exclusions are documented, but you must be able to create/adjust route objects and, where needed, delegate mnt-routes to Leaseweb. |
Step-by-Step BYOIP Process
A) IP Announcement (IPAN) - Leaseweb originates your prefixes
at least /24 IPv4 or /48 IPv6, properly registered with RIPE/ARIN/APNIC, and with correct IRR route objects (e.g. mnt-routes delegated to Leaseweb for RIPE).
Open a ticket via the Leaseweb Customer Portal or via your account manager, specifying the prefixes to be announced, the desired Leaseweb location(s) (NL, DE, US, UK, APAC), and the product(s) (Dedicated/Colo racks, Dedicated Servers, Elastic Compute, VMware).
provide network design details (routers, default gateways, segmentation of larger blocks into /24s, redundancy), and clarify whether Leaseweb should handle rDNS for the space.
If you are not the RIR holder of the prefixes, supply a Letter of Authorization (LOA) from the IP owner authorizing Leaseweb to announce the prefixes from its ASNs.
Leaseweb validates ownership/IRR data, configures IP Announcement from the appropriate Leaseweb ASN(s), and attaches the blocks to your services (as rack-bound space or Floating IPs). Monitor global propagation using external BGP/route-view tools.
Leaseweb assigns you a private ASN and configures BGP sessions from your rack/virtual edge towards its network (default route only; full table is out of scope).
Optionally combine with IP Announcement so that your own prefixes are advertised under Leaseweb’s ASNs while you use BGP internally for routing and failover (subject to the same IPAN conditions).
Implement BGP configuration on your routers/switches according to Leaseweb’s guidance, advertise your internal prefixes (up to the allowed number of subnets), and receive the default route from Leaseweb.
Test traffic flows and failover paths, then monitor routing and performance over time (looking glasses, external route monitors, and Leaseweb Customer Portal graphs).
Cost and Limitations
| Item | Details |
|---|---|
| Fees |
IP Announcement: initial delivery includes announcement of up to 20 prefixes; additional announcement/de-announcement changes incur an Announcement Change fee per prefix as described in Leaseweb’s Service Specifications. Any Leaseweb-provided IP addresses (if used alongside BYOIP) follow standard per-IP or per-subnet fees outlined in IPv4/IPv6 guidelines. |
| Bundled or Standalone |
IP Announcement is an add-on network service for: Dedicated servers, Dedicated Racks, Colocation Racks, Elastic Compute, VMware vSphere/HCI, VMware vCloud. Private AS BGP is an add-on for private environments (Dedicated/Colo racks, VMware Single Tenant vSphere & HCI) and can be combined with IP Announcement. |
| Traffic/Peering Restrictions | - All customer prefixes are announced only from Leaseweb ASNs; customer public ASNs cannot be used as origin. - Minimum externally advertised sizes: /24 IPv4, /48 IPv6; smaller internal segmentation only within the same data center. - Leaseweb prefers aggregated announcements and may review heavily de-aggregated plans on a case-by-case basis. - Private AS BGP allows up to 100 subnets to be announced (combined IPv4/IPv6) from your private ASN towards Leaseweb. |
| Other Limitations | - IP Announcement is not supported for Public Cloud, VPS, or Shared Colocation units. - Private AS BGP is available only in private environments (full/half racks, VMware Single Tenant/HCI) and provides a default route, not a full internet table. - Customer must operate BGP-capable network equipment and have internal networking expertise. - Prefixes and usage are subject to Leaseweb’s Acceptable Use, spam, and abuse policies; ranges with serious reputation issues may require remediation. |
Automation & Developer Access
- API Access: Yes - Leaseweb Developer API (REST) and Customer Portal for managing servers, networking, and IPs. BYOIP/IP Announcement onboarding itself is typically initiated via support tickets or account management rather than self-service API.
- CLI: Official "leaseweb-cli" command line interface for Leaseweb APIs (GitHub: Leaseweb organization).
- Terraform: Official "terraform-provider-leaseweb" published by Leaseweb for managing infrastructure as code.
- SDKs: Official Go SDK (leaseweb-go-sdk) and API definitions; additional community libraries available via GitHub and language ecosystems.
Abuse & Reputation Management
- Leaseweb’s Compliance / Abuse Prevention department handles abuse notifications (spam, attacks, blocklists). Customers are expected to respond quickly via the ticket system and work with Leaseweb on remediation.
- Customers remain responsible for monitoring the reputation of their announced prefixes and for following Leaseweb’s documented “Procedure to remove blacklist” and spam/abuse policies when delisting is required.