Worldstream BYOIP Integration Overview
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Worldstream’s infrastructure. Worldstream is a Dutch cloud infrastructure and bare metal provider with its own data centers, multi-terabit backbone, and an extensively peered AS49981 network. BYOIP at Worldstream is implemented as a “bring your own IP range” feature: Worldstream can originate your IPv4 prefixes from its ASN 49981 (or route them for use with your own ASN) so they can be attached to dedicated servers, bare metal compute, private cloud, and colocation workloads.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Worldstream |
| Website | Worldstream - Solid IT. No Surprises. | IPv4 Pricing & Bring Your Own IP range | Worldstream Network Detailed | Knowledge Base |
| ASN(s) |
AS49981 - WorldStream B.V. Worldstream operates AS49981 as a globally visible, RPKI-valid network with IPv4 and IPv6 prefixes and hundreds of BGP peers and upstreams. This ASN is used to originate Worldstream-owned space and can also be used to originate customer-owned IPv4 ranges under the BYOIP feature, or Worldstream can route your space for use behind your own ASN. |
| Regions Supported |
Worldstream’s core infrastructure is hosted in its company-owned European data centers with connectivity extended via the Worldstream Elastic Network (WEN): - Naaldwijk (NL): primary Worldstream data center campus. - Haarlem (NL): additional Dutch site interconnected via WEN. - Frankfurt (DE): interconnected WEN location with low-latency links to the Netherlands. BYOIP announcements are made from AS49981 and are primarily tied to these locations and to Worldstream’s European backbone; prefixes are globally routable on the internet while traffic is physically anchored in these data centers. |
| Support Contact |
Use the Worldstream Knowledge Base and “Ask question” link to open tickets about IP addressing and routing, or contact Sales/Support via the main website: - Knowledge Base & Support - Contact & Sales (general inquiries) |
| Tech Article & Date |
IPv4 Pricing - Bring Your Own IP range (March 22, 2023) - documents additional IPv4 pricing, the “Bring your own IP range” option, and requirements such as LOA, RPKI ROA, and route objects. Worldstream Network Detailed (January 17, 2023) - describes network design, WEN locations (Naaldwijk, Haarlem, Frankfurt), IPv6 limits, and security measures. Why we ignore UCEPROTECT listings (May 15, 2024) - explains Worldstream’s stance on certain RBLs and general guidance for blacklist checks. |
| BYOIP Scope |
Worldstream’s BYOIP feature is exposed as “Bring your own IP range” for customers with servers or colocation in their data centers. You can supply one or more public IPv4 prefixes that Worldstream will announce on your behalf, subject to routing and RPKI validation. BYOIP ranges are then usable as: - Primary address space for dedicated servers, bare metal nodes, or private cloud workloads. - Routed subnets in colocation racks or across the Worldstream Elastic Network (WEN) between Naaldwijk, Haarlem, and Frankfurt. Worldstream can originate your space from AS49981 or, with the correct routing and RPKI setup, route it in combination with your own ASN. |
| Supported Versions |
IPv4: BYOIP is explicitly documented for IPv4 ranges (one or more subnets) that are globally routable and maintained at a recognized RIR. These prefixes can be announced from AS49981 after LOA, route object, and RPKI ROA validation. IPv6: Worldstream offers native IPv6 at no additional recurring charge and can assign IPv6 ranges to servers, but IPv6 BYOIP (customer-owned IPv6 prefixes) is not documented publicly. Customers should confirm IPv6 BYOIP options with Worldstream support. |
| Supported Services | - Dedicated servers, bare metal compute, and private servers hosted in Worldstream data centers. - Colocation services in Naaldwijk and other Worldstream locations. - Worldstream Elastic Network (WEN) VLANs and inter-site connectivity between Naaldwijk, Haarlem, and Frankfurt. In all cases, BYOIP is a network feature layered on top of these services; it does not function as a standalone IP transit product. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size |
Worldstream does not publish a strict minimum prefix length for BYOIP, but practical considerations apply: - Each IP you receive is part of a /24 subnet in their default addressing model, and global IPv4 routing conventionally accepts prefixes down to /24. - BYOIP is described as “your own IP range” and is billed per subnet when announced via Worldstream. In practice, customers should expect to bring /24 or larger IPv4 prefixes for stable global routing and confirm any more-specific requirements (e.g., multiple /24s aggregated to larger blocks) with Worldstream support. |
| ASN Ownership Required |
Worldstream does not require you to have your own ASN to use BYOIP. The IPv4 pricing/BYOIP article states that you must create a route object at your RIR with either: - Worldstream ASN 49981 (WorldStream B.V.), or - Your own ASN, if you prefer to be the BGP origin. Customers without their own ASN typically let AS49981 originate the space, whereas customers with an ASN can design a more advanced routing setup with coordination from Worldstream. |
| IRR / Route Objects |
To use BYOIP with Worldstream, the official requirements include: - Create a route object at your RIR for the IP range with AS49981 as the origin ASN (or your own ASN). - Ensure that only one route object is present for the IP range (multiple conflicting route objects are not allowed). These requirements align your RIR/IRR data with the intended origin ASN and reduce the risk of routing conflicts. |
| ROA or LOA |
Worldstream explicitly requires both commercial and cryptographic proof of control: - LOA (Letter of Authorization): You must provide a signed LOA giving Worldstream written permission to announce your prefix(es) or to perform the necessary routing changes on your behalf. - RPKI ROA: You must create a valid RPKI ROA for the IP range in the RIR where it is maintained, authorizing the origin ASN (AS49981 or your own). This can be done directly at the RIR or by your leasing partner if you lease the range. Worldstream’s BYOIP feature is conditional on these validations being in place and correct. |
| RIR Limitations | - The IP range must be publicly routable IPv4 space maintained with a recognized RIR (e.g., RIPE, ARIN, APNIC) and not currently announced elsewhere. - You must be able to create and maintain the required route object and RPKI ROA at that RIR. - Only one active route object is allowed for the range while it is being announced via Worldstream; additional route objects or simultaneous announcements elsewhere are not permitted. |
Step-by-Step BYOIP Process
Estimated Setup Time:Typically days to a few weeks, depending on how quickly you can produce LOA documentation, update RIR/ROA data, and coordinate testing. Much of the lead time is on the customer side (RIR changes and validation).Tested By Us:Not yet
Validate prerequisites
Confirm that you have active services with Worldstream (dedicated servers, bare metal, private cloud, or colocation) and that your IPv4 range is public, routable, and currently not announced elsewhere.
Prepare LOA and RIR objects
Draft a Letter of Authorization (LOA) formally granting Worldstream permission to announce the specified IP range(s). In your RIR portal (or via your leasing partner), create a route object for the prefix with origin ASN 49981 (or your own ASN if you prefer to be the origin) and ensure that only one route object exists for the range.
Create an RPKI ROA
In the RIR where the range is maintained, create a valid RPKI ROA for the prefix that authorizes the correct origin ASN (AS49981 or your own). Verify that the ROA is visible and in a “valid” state before requesting the announcement.
Submit the BYOIP request
Open a Worldstream support ticket (or contact your account team) referencing the “Bring your own IP range” option, and provide the LOA, prefix list, RIR/route object details, and ROA information. Indicate which services (servers, VLANs, sites) should receive the announced subnets.
Worldstream implements routing
After validation, Worldstream will configure the necessary BGP announcements from AS49981 (or coordinate routing towards your own ASN) and plumb the prefixes into your dedicated servers, WEN VLANs, or colocation environment. They may also adjust internal routing and security policies as needed.
Test and roll out
From test hosts on the internet, verify reachability, path length, and geolocation of your BYOIP addresses. Confirm that traffic flows correctly into your Worldstream environment and that reverse DNS, application bindings, and firewall policies are updated. Once validated, gradually migrate workloads and DNS records to your BYOIP ranges.
1
Validate prerequisites
Confirm that you have active services with Worldstream (dedicated servers, bare metal, private cloud, or colocation) and that your IPv4 range is public, routable, and currently not announced elsewhere.
Validate prerequisites: Confirm that you have active services with Worldstream (dedicated servers, bare metal, private cloud, or colocation) and that your IPv4 range is public, routable, and currently not announced elsewhere.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees |
Worldstream publishes transparent pricing for IP services: - Additional IPv4 addresses: €3.50 per IPv4 address (for Worldstream-owned IPs attached to servers). - Bring Your Own IP Range: one-time administrative fee of €49 per subnet when announcing your own IP range via their network. - IPv6 addresses: currently no extra recurring charge for assigning IPv6 ranges to servers. Standard service charges (servers, colocation, bandwidth/traffic) apply in addition to these IP-related fees. |
| Bundled or Standalone |
BYOIP is not sold as a standalone IP transit or routing product. It is an add-on feature for: - Dedicated servers, bare metal, private cloud, and colocation inside Worldstream facilities. - Worldstream Elastic Network (WEN) VLANs connecting Naaldwijk, Haarlem, and Frankfurt. Customers must maintain an underlying hosting or infrastructure service with Worldstream to use BYOIP. |
| Traffic/Peering Restrictions | - Traffic for BYOIP ranges will follow Worldstream’s AS49981 routing and peering policies when they originate your space; you cannot directly control upstream selection unless you coordinate a design using your own ASN. - Certain incoming ports are blocked by default in the Worldstream network for security reasons (e.g., some amplification-prone UDP ports), and running DHCP servers on public interfaces is prohibited. - Standard fair-use and anti-abuse policies apply to all traffic, including BYOIP ranges announced via Worldstream. |
| Other Limitations | - Your IP range must not be actively announced elsewhere while Worldstream is originating it, and there must be only one route object for the range. - ROA and route object accuracy are your responsibility; invalid or missing RPKI data may delay or prevent announcements. - Worldstream focuses on European data centers; if you need multi-continent presence with the same BYOIP ranges, you will need additional providers or your own global network to complement their footprint. |
Automation & Developer Access
- API Access: Worldstream exposes a public API (v1) for managing servers and related infrastructure tasks. BYOIP itself is provisioned via tickets and internal workflows, but once ranges are announced you can use the API and automation tools to manage servers that consume those IPs.
- Automation / WHMCS modules: Third-party WHMCS modules exist for automating Worldstream dedicated server provisioning and lifecycle management. These modules are built on the Worldstream API and can help integrate BYOIP-backed servers into reseller or hosting portals.
- Infrastructure-as-code: While there is no official Terraform provider for Worldstream today, customers commonly combine Worldstream’s API with tools like Ansible or custom scripts to automate server provisioning, configuration, and IP assignments that include BYOIP ranges.
- BYOIP workflow: There is no public, BYOIP-specific API. Enabling and modifying BYOIP announcements is handled through support tickets and account management rather than self-service portal calls.
Abuse & Reputation Management
- Worldstream publishes guidance on handling blacklist listings and specifically notes that some RBLs (such as UCEPROTECT) may use questionable business practices; customers are generally advised to focus on reputable RBLs and practical impact rather than panic over every listing.
- For BYOIP ranges, you as the prefix holder retain primary responsibility for the long-term reputation and RBL status of your space. Worldstream’s network security measures (blocked ports, DDoS protection, abuse handling) help limit abuse, but delisting and interaction with RBL operators remains a customer task.
- Because AS49981 is widely visible on the global internet with active RPKI, route leaks and invalid origins affecting your prefixes can be monitored using tools such as Cloudflare Radar, HE.net, or other BGP monitoring platforms. You should track routing health and respond promptly to anomalies or abuse reports involving your BYOIP ranges.