Skip to content

Openmetal BYOIP Integration Overview

BYOIP SUPPORTER
ASN AS400956
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: Singapore, Netherlands, United States

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with OpenMetal private cloud and bare metal infrastructure. OpenMetal supports BYOIP by originating your public IPv4 prefix from OpenMetal edge routers (provider-announced model), enabling you to preserve IP-based identity (allowlists, API endpoints, email reputation) while running workloads on OpenMetal. OpenMetal also supports provider-allocated dedicated IP blocks (e.g., /28) when you do not bring your own space. BYOIP can be used across OpenMetal’s networking stack, including direct attachment to instances and use with load balancers, with DDoS protections available at the edge.

Provider Details

FieldInformation
Provider NameOpenMetal
Website OpenMetal Homepage | Cloud Networking Feature Details (BYOIP /24+) | BYOIP Architecture Article (Anycast, DDoS, /24+) | Data Center Locations | OpenMetal Central: Add Public IP Address Blocks | Contact
ASN(s) OpenMetal originates BYOIP announcements from its own ASN (documented publicly as AS400956, “OPENMETAL-AS”). In BYOIP scenarios, you typically authorize OpenMetal’s origin ASN for your prefix (e.g., via RPKI ROA) so the announcement is not RPKI-invalid.
Regions Supported OpenMetal infrastructure is offered from Tier III data center spaces in:
United States: Ashburn, Virginia (US East) and Los Angeles, California (US West)
Europe: Amsterdam, Netherlands
Asia: Singapore
BYOIP practicality improves when you can deploy the same addressing across multiple locations (including anycast patterns) while keeping DNS and allowlists stable.
Support Contact Contact / Sales (sales@openmetal.io) | Legal / Customer Service references (customerservice@openmetal.io / support@openmetal.io) | OpenMetal Central support request workflow (requires login): Docs navigation includes “Creating a Support Request”.
Tech Article & Date Why Enterprise Workloads Need BYOIP Support That Hyperscalers Can’t Provide — OpenMetal’s overview of BYOIP for /24+ blocks, BGP edge routing, anycast use cases, and how BYOIP integrates with instances/load balancers (Updated on November 20, 2025).
BYOIP Scope OpenMetal’s BYOIP is a provider-announced prefix model:
1) Customer-owned IPv4 prefix (/24+): You bring a routable IPv4 block (minimum /24) and OpenMetal announces it from their edge routers/ASN for use within your OpenMetal environment.
2) Provider-allocated dedicated IP blocks: If you do not have your own IP space, OpenMetal can provide dedicated blocks (e.g., /28) associated with your deployment (less portable than true BYOIP, but dedicated within OpenMetal).
Supported Versions Documented: Public IPv4 BYOIP with a minimum of /24 for announcement from OpenMetal edge routers.
IPv6: OpenMetal operates IPv6 on its network, but customer BYOIP for IPv6 is not explicitly documented in the public BYOIP materials above; confirm current availability/requirements with OpenMetal support.
Supported Services BYOIP concepts apply to OpenMetal’s Hosted Private Cloud (OpenStack) and Bare Metal Dedicated Servers. Documented integration points include attaching BYOIP addresses to instances, using OpenStack load balancers, and applying firewall rules while maintaining dedicated VLAN isolation.

Technical Requirements

RequirementDetails
Prefix Size IPv4 BYOIP minimum: /24 (256 addresses) or larger for announcement from OpenMetal edge routers. If you do not bring your own space, OpenMetal can provide dedicated provider-allocated blocks (commonly referenced as /28 as an example of dedicated allocation).
ASN Ownership Required No customer ASN is required for the standard provider-announced BYOIP model. OpenMetal originates the prefix from its own ASN/edge routers. (If you maintain RPKI, you generally publish/adjust a ROA to authorize OpenMetal’s origin ASN so the route remains RPKI-valid.)
IRR / Route Objects Best practice: maintain accurate IRR/route objects for your prefix (where applicable) and align them with the announced origin ASN used by OpenMetal. This improves global routing acceptance and troubleshooting. Confirm any provider-specific requirements with OpenMetal support.
ROA or LOA If your prefix is protected by RPKI, publish/adjust a ROA authorizing the OpenMetal origin ASN to avoid RPKI-invalid announcements. OpenMetal may also request an LOA or equivalent proof-of-control during onboarding (common in provider-announced BYOIP workflows).
Service / Platform Dependencies You should have an active OpenMetal deployment (Hosted Private Cloud and/or Bare Metal) and networking configuration that supports public IP attachment and/or load balancer integration. OpenMetal documentation shows self-service workflows to add/attach provider IP address blocks to VLANs in OpenMetal Central; BYOIP announcements typically require provider-side routing work.

Step-by-Step BYOIP Process

Estimated Setup Time: Typically days to a few weeks depending on prefix validation, RPKI/IRR updates, and coordination/testing across applications (allowlists, DNS, partner firewalls).

Tested By Us: Not yet

Provider-announced BYOIP (Customer-owned /24+ via OpenMetal edge routers)

  • Confirm you have a globally routable public IPv4 prefix (minimum /24) under your control (owned/leased long-term) and that you can make any required routing registry updates (IRR) and RPKI ROA changes.
  • Choose the OpenMetal deployment region(s) where the prefix will be used (US East/West, EU Netherlands, Asia Singapore). If you plan anycast-style architecture, align application design and health/failover expectations accordingly.
  • Open a support request with OpenMetal to onboard BYOIP. Provide the prefix details, proof-of-control (LOA if requested), and the desired announcement scope (single site vs multi-site).
  • If you use RPKI, publish/adjust a ROA authorizing OpenMetal’s origin ASN (AS400956) for your prefix so the announcement remains RPKI-valid.
  • OpenMetal configures BGP announcements at their edge routers and verifies global propagation. Validate that DDoS protections and edge routing behavior meet your requirements (OpenMetal references DDoS protection up to 10 Gbps per IP in their networking materials).
  • Assign and use BYOIP addresses within your environment as needed: attach to instances, place behind OpenStack load balancers, and apply firewall policy. Update external allowlists/partners and confirm application behavior end-to-end (API clients, email sending, geolocation, compliance logging).

Provider-allocated dedicated IP blocks (not BYOIP, but dedicated within OpenMetal)

  • From OpenMetal Central, request additional public IP address blocks for your deployment (documentation shows block sizes ranging from 16 up to 256 addresses) and associate them with the correct datacenter and VLAN.
  • Assign the new public block to the appropriate provider VLAN, confirm status becomes ACTIVE, and then consume addresses on instances or load balancers according to your architecture.
  • Treat these addresses as stable inside OpenMetal (dedicated to your deployment), but note they are not portable to other infrastructure providers the way customer-owned BYOIP space is.

References: Cloud Networking Feature Details (BYOIP /24+), OpenMetal BYOIP architecture article (anycast, DDoS, /24+), Data center locations, OpenMetal Central IP block documentation.

Cost and Limitations

ItemDetails
Fees OpenMetal documents that clouds include a base public IPv4 block, and that additional blocks are available for a fee. BYOIP (customer-owned /24+) typically requires support-led onboarding to implement announcements; commercial terms and any one-time setup fees (if any) should be confirmed with OpenMetal sales/support.
Bundled or Standalone BYOIP is not a standalone service; it is delivered as part of OpenMetal’s cloud/bare-metal networking capabilities (edge routing + integration with instances/load balancers/VLANs).
Minimum Block Size Constraints Customer BYOIP is documented for /24 and larger IPv4 blocks. Smaller allocations (e.g., /28) are referenced as provider-allocated dedicated blocks, not portable BYOIP.
Operational Dependencies You are responsible for keeping your routing hygiene current (RPKI ROA/IRR where applicable). Many enterprises also maintain abuse workflows and reputation management for customer-owned space (email reputation, API allowlists, security feeds). DDoS posture and routing policy details should be validated in design/testing.

Automation & Developer Access

  • Self-service (OpenMetal Central): OpenMetal documents a workflow to add public IP address blocks and assign them to provider VLANs from their portal, enabling day-2 IP lifecycle management for provider-allocated space.
  • OpenStack APIs: Hosted Private Cloud is powered by OpenStack, enabling infrastructure-as-code patterns for networks, floating/public IP usage, load balancers, and security groups using standard OpenStack APIs/clients (subject to your OpenMetal deployment configuration).
  • BYOIP onboarding automation: The public documentation describes BYOIP announcements as a provider edge-router capability; in practice, initial prefix onboarding/announcement is typically implemented via support engagement rather than a fully self-serve workflow.

Abuse & Reputation Management

OpenMetal Homepage
Cloud Networking Feature Details (base IPv4 block, BYOIP /24+)
Why Enterprise Workloads Need BYOIP Support (anycast, /24+, DDoS, integration)
OpenMetal Data Center Locations (US/EU/Asia)
OpenMetal Central Docs: Adding Public IP Address Blocks
Contact OpenMetal

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.