Skip to content
BYOIP

NovoServe BYOIP Integration Overview

BYOIP SUPPORTER
ASN 24875
IPv4 support
IPv6 support
LOA support
ROA support
Process Manual
Locations supported
Other: Congo, Democratic Republic, Egypt, Ethiopia, Nigeria, Bangladesh, China, India, Indonesia, Iran, Japan, Pakistan, Philippines, Thailand, Turkey, Vietnam, Germany, Russia, Mexico, United States, Brazil

Location

This page provides a practical BYOIP (Bring Your Own IP) integration overview for NovoServe (novoserve.com). NovoServe explicitly supports—and publicly encourages—customers to announce their own IPv4/IPv6 prefixes under their own ASN on the NovoServe network so that workloads running on NovoServe bare metal can keep stable egress/ingress IP reputation and identity.

Important framing: NovoServe’s BYOIP model is a classic BGP-based provider announcement approach for dedicated servers / bare metal (not a hyperscaler control-plane “import prefix” feature). NovoServe’s network team provisions the BYOIP setup (including creating a virtual router instance and establishing a BGP session), and your organization remains responsible for typical “IP-holder duties” such as abuse policy handling and reverse DNS management for your own space.

Provider Details

FieldInformation
ProviderNovoServe (NovoServe B.V. / NovoServe LLC)
Websitehttps://novoserve.com/
Category (BYOIP.info taxonomy)Hosting Providers → Bare Metal Providers / Dedicated Server Hosting
BYOIP SupportYes (explicitly documented; BYOIP is supported for both IPv4 and IPv6)
BYOIP ScopeUse your own public IP prefixes on NovoServe dedicated servers (announced via BGP on the NovoServe network)
Geography / Deployment Locations Europe: The Netherlands (Amsterdam OUM, Amsterdam SHR, Rotterdam).
North America: New York metropolitan area.
Denmark (Copenhagen) is mentioned as available for larger projects.
IPv4 / IPv6BYOIP is supported for IPv4 and IPv6 (announce your own prefixes under your own ASN)
Minimum prefix size (provider guidance)Provider guidance indicates /24 or larger for announced IP blocks
RPKI / IRR expectationsProvider guidance indicates that route objects and ROAs are required for the BYOIP flow; where ROA creation is not possible, a Letter of Authorization (LoA) is used instead (and LoA is required for ASNs per provider guidance)
BYOIP Process TypeManual / assisted (NovoServe’s network team sets up the virtual router and BGP session; announcements may be accelerated when ROA is present per provider guidance)
Subnet-to-location policy (operational note)Provider guidance indicates that a single IP subnet is used in a single data center location and that smaller networks are generally not split across sites (plan at least one /24 per location for multi-site deployments)
Network ToolingLooking Glass and speedtest tooling are published for network diagnostics and evaluation
DDoS Protection (context)Provider guidance states that dedicated servers include always-on DDoS protection by default (separate from BYOIP, but relevant to edge/routing operations)
Support / Contacts (published) Support portal entry point: https://novoserve.com/contact-support
Peering inquiries (published): peering@novoserve.com
NOC (published): noc@novoserve.com
General support (published): support@novoserve.com

BYOIP Overview (NovoServe model)

NovoServe’s BYOIP approach is based on BGP route origination for customer-owned prefixes. In practical terms:

  • You obtain your own public IP space (IPv4 and/or IPv6) and typically your own ASN.
  • You prepare routing authorization artifacts (ROA/RPKI and IRR route objects) per provider guidance.
  • NovoServe provisions a virtual router instance and establishes a BGP session to your environment so your prefixes can be announced under your ASN on NovoServe’s network.
  • Your NovoServe servers then use your IP space for services (e.g., VPN egress IP stability, mail/IP reputation continuity, brand trust, migrations without IP renumbering).

Technical & Administrative Requirements

Based on NovoServe’s published BYOIP guidance, you should plan for the following prerequisites before requesting BYOIP enablement:

  • IP resources: Your own IPv4 and/or IPv6 prefix(es). Provider guidance indicates a /24 or larger for announced IP blocks.
  • ASN: Your own ASN is recommended/encouraged for announcing your prefixes under your own routing identity.
  • Routing authorization: Provider guidance indicates IRR route objects and RPKI ROA creation is mandatory for their standard onboarding flow.
  • LoA fallback: If ROA creation is not available (e.g., broker cannot support RPKI), provider guidance indicates you must provide a Letter of Authorization (LoA). Provider guidance also states LoA is required for ASNs.
  • Operational responsibility: Provider guidance states you are responsible for your own abuse policy and typically also for DNS/rDNS management for your IP space.

Onboarding Process (High-level)

The following sequence mirrors NovoServe’s published BYOIP onboarding flow and adds practical operator context where appropriate:

  1. Acquire resources: Obtain an ASN and IP space via a sponsoring LIR / RIR process (or an IP broker / LIR pathway), aligned with your registry’s policies.
  2. Prepare routing objects: Create the necessary IRR route objects and RPKI ROAs for the prefix(es) and ASN you intend to originate.
  3. Engage NovoServe networking: Request BYOIP enablement and provide your ASN and the prefix(es) to be announced. If ROA cannot be used, provide an LoA per provider guidance.
  4. BGP session provisioning: NovoServe’s network team provisions a virtual router instance and configures the BGP session to your environment.
  5. Route propagation: Once the route is originated, allow time for full Internet propagation; validate using external route collectors and NovoServe’s published network diagnostic tools (e.g., looking glass).
  6. Put prefixes into service: Configure your servers/services to use the BYOIP space (NAT/egress policies, service binds, firewalling, monitoring, and abuse handling).

Configuration Notes for Operators

Because NovoServe provisions the BGP session on their side, your core tasks are typically: (1) ensuring routing authorization is correct (ROA/IRR), and (2) ensuring your edge/router is ready to exchange routes safely. Below is a vendor-neutral checklist you can apply to most BYOIP-with-BGP engagements.

  • Confirm session parameters: exchange ASN details, peering IPs, and any session security requirements (e.g., MD5) with NovoServe networking.
  • Prefix filtering: ensure you only advertise the exact prefix list authorized for the session; avoid accidental more-specific leakage.
  • RPKI posture: keep ROAs aligned with your intended origin ASN; NovoServe’s guidance indicates ROAs help their automated systems announce quickly.
  • Multi-site planning: if you deploy across multiple NovoServe data centers, plan subnet allocation per provider guidance (do not assume a subnet can span multiple sites; allocate at least one /24 per location).
  • Abuse/rDNS readiness: have an internal process for abuse desk handling and PTR/rDNS workflows before you migrate sensitive services (mail, ads, VPN, etc.).

Example (generic) BGP prefix policy logic: advertise only your authorized prefixes; reject everything else. Adapt to your routing stack as needed.

# PSEUDOCODE (generic idea)
# OUTBOUND: allow only your BYOIP prefixes, then deny all
permit OUT 203.0.113.0/24
permit OUT 2001:db8:1234::/48
deny   OUT any

# INBOUND: accept only what you intend to learn (typically default or full-table per contract),
# and apply max-prefix / dampening policies as required.

Operations & Monitoring

After cutover, treat the BYOIP environment as production routing infrastructure:

  • Validate reachability: use looking glass / traceroute views to confirm Internet pathing toward your prefixes from multiple regions.
  • Track route hygiene: continuously monitor ROA validity and IRR consistency (route leaks and RPKI-invalid announcements can cause reachability issues with strict networks).
  • DDoS posture: NovoServe states dedicated servers include always-on DDoS protection; confirm expectations and escalation path for larger threat models.
  • Change control: manage prefix adds/removals as formal changes (update ROAs/route objects first, then request routing changes), and document rollback steps.

Deprovisioning / Offboarding

When retiring BYOIP from NovoServe (or migrating to another provider), plan a clean withdrawal to avoid prolonged blackholing or reputation harm:

  1. Migration window: establish a dual-run window if possible (DNS TTL reductions, controlled cutover, and traffic validation).
  2. Withdraw announcements: coordinate with NovoServe networking to remove the BGP announcements (or shut down the session) at the agreed time.
  3. Update ROAs/route objects: change origin authorization to the new provider ASN or your new routing design; remove stale objects that could confuse validators.
  4. Post-cutover validation: confirm route propagation matches the new state across route collectors and looking glass tools.

FAQ

Does NovoServe support BYOIP for IPv6?
Yes—NovoServe’s published BYOIP materials explicitly mention BYOIP support for both IPv4 and IPv6.

Is BYOIP self-service and fully automated?
NovoServe’s published guidance describes a network-team-led process where they provision the virtual router and BGP session. They also note that having ROAs in place helps their automation announce routes more quickly; however, the overall onboarding is best treated as a manual/assisted workflow.

What do I need to provide to start?
Expect to provide at minimum your ASN and the prefix(es) you want announced, plus routing authorization artifacts (ROA/route objects) and/or LoA as applicable per NovoServe guidance.

Can I stretch one subnet across multiple NovoServe data centers?
Provider guidance indicates that a subnet is tied to a single data center location; plan separate subnets per site if you deploy multi-region.

Official NovoServe Resources

Last reviewed: 2026-01-12

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.