Skip to content

Leaseweb BYOIP Integration Overview

BYOIP SUPPORTER
ASN AS16265
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: Singapore, Hong Kong, Germany, Netherlands, United Kingdom, United States, Australia

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

FieldInformation
Provider NameLeaseweb
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 SupportedIP 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 ScopeProvider-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 VersionsIPv4 & 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

RequirementDetails
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

Estimated Setup Time: Not formally stated by Leaseweb; in practice, expect completion within a few business days after all route objects and LOA/authorization are in place (coordinate timelines with Leaseweb Support).

Tested By Us: Not yet

A) IP Announcement (IPAN) – Leaseweb originates your prefixes

  • Verify that your prefixes meet the requirements: 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).
  • For racks/private environments: 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.

B) Optional: Private AS BGP (Leaseweb-assigned private ASN)

  • Confirm that you use a private environment that supports Private AS BGP (Dedicated / Colocation racks or VMware Single Tenant vSphere / HCI).
  • Request Private AS BGP via Leaseweb support. 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).

References: IPv4 address assignment & IP Announcement, IP Announcement and Private AS BGP, Peering policy.

Cost and Limitations

ItemDetails
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.

Leaseweb Homepage
IPv4 address assignment & IP Announcement
IP Announcement and Private AS BGP
Peering policy & peering contacts
Contacting Customer Care
Developer Portal & API documentation
Procedure to remove blacklist
Contacting Abuse Prevention department

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.