Skip to content

Cherry Servers BYOIP Integration Overview

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

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Cherry Servers infrastructure. Cherry supports two models: (1) provider-announced BYOIP (Cherry originates your IPv4 /24+ under their ASN), and (2) customer‑ASN announcements via BGP (you originate your IPv4/IPv6 prefixes using your own ASN).

Provider Details

FieldInformation
Provider NameCherry Servers
WebsiteBring Your Own IP Range (BYOIP)  |  Bring your own ASN + prefixes  |  Local BGP
ASN(s)Location-specific ASNs:
LT – AS16125  |  DE – AS213896  |  NL – AS59642  |  SE – AS214159  |  SG – AS216444  |  US – AS204770
Regions SupportedLT–Šiauliai, NL–Amsterdam, DE–Frankfurt, SE–Stockholm, US–Chicago, SG–Singapore (per Local BGP docs)
Support Contact24/7 Support (chat/ticket/email)  |  Contact methods
Tech Article & DateBring Your Own IP Range (provider‑announced) & Bring your own ASN with IP prefix (customer‑ASN).
BYOIP ScopeProvider‑announced: IPv4 /24+ announced by Cherry’s ASN in the chosen region.
Customer‑ASN (BGP): Your ASN announces your IPv4/IPv6 prefixes via Local BGP.
Supported VersionsIPv4 & IPv6 (platform IPv6 supported; BYO‑IPv6 via customer‑ASN BGP). IPv6 product doc
Supported ServicesDedicated Servers, Cloud VDS/VPS, Storage VPS; works with Floating IPs and Public IP SubnetsLocal BGP for HA and control.

Technical Requirements

RequirementDetails
Prefix SizeProvider‑announced: IPv4 minimum /24 (256 IPs).
Customer‑ASN: IPv4 and IPv6 accepted with valid ROAs (v6 minimum size not specified by Cherry; commonly /48 for global routing).
Ref: “Bring Your Own IP Range” & “Bring your own ASN with IP prefix”.
ASN Ownership RequiredNo (provider‑announced flow).
Yes (customer‑ASN BGP flow).
IRR / Route ObjectsProvider‑announced: Your inetnum must be separate and have mnt-routes: DUOMENUCENTRAS-MNT so Cherry can create route objects.
Customer‑ASN: Add proper import/export remarks toward the location’s Cherry ASN in your ASN object.
ROA or LOAROAs required for customer‑ASN; LOA recommended.
For provider‑announced: LOA not stated as required; Cherry validates ownership and creates route objects (ROA recommended).
RIR LimitationsNot specified; prefixes must be registered in a RIR with IRR/RPKI data and pass Cherry’s validation.

Step-by-Step BYOIP Process

Estimated Setup Time: Typically < 24 hours after approval (allow up to 24h for global routing updates)

Tested By Us: Not yet

A) Provider‑announced BYOIP (Cherry originates your /24+)

  • Submit your exact IPv4 range(s) to Cherry (via account manager or support).
  • Ensure your range is a separate INETNUM and set mnt-routes: DUOMENUCENTRAS-MNT.
  • Cherry creates the required route objects and begins announcing the prefix from the region’s ASN.
  • Propagation: allow up to 24 hours for full global reachability.

B) Customer‑ASN + Prefixes via Local BGP (you originate)

  • Select the target location and corresponding Cherry ASN (LT AS16125, DE AS213896, NL AS59642, SE AS214159, SG AS216444, US AS204770).
  • Update your ASN object with proper import/export remarks toward that Cherry ASN.
  • Submit your ASN, prefixes, ROA records (required), and LOA (recommended) for validation.
  • After approval, enable Local BGP in the Client Portal and apply the provided BIRD/routing config on your servers.
  • Announce your prefixes; monitor propagation (HE BGP Toolkit, RIPEstat, etc.). Allow up to 24 hours for global acceptance.

References: BYO IP RangeBring your own ASNLocal BGP.

Cost and Limitations

ItemDetails
FeesNo public BYOIP onboarding surcharge documented; standard service pricing applies. (Confirm with Sales for any custom routing needs.)
Bundled or Standalone
Integrated with Cherry networking; customer‑ASN flow uses Local BGP.
Traffic/Peering RestrictionsPrefixes must not be blocklisted and must maintain good reputation; adhere to Cherry’s IP usage and acceptable‑use policies.
Other LimitationsLocal BGP works within a single region; supported across LT, NL, DE, SE, US, SG. Works with Floating IPs and Public IP Subnets. Windows examples not provided in docs (manual possible).

Automation & Developer Access

  • API Access: Yes — REST API (tokens via portal). BYOIP onboarding itself is initiated via support.
  • CLI: cherryctl
  • Terraform: Official provider — Terraform Registry
  • SDKs: Python SDK (plus Go library)

Abuse & Reputation Management

  • Cherry verifies prefix ownership and recommends ensuring ROAs and that IPs are not on public blocklists.
  • Ongoing reputation monitoring and delisting are the customer’s responsibility.

Cherry Servers Homepage
Bring Your Own IP Range (BYOIP)
Bring your own ASN with IP prefix
Local BGP (High Availability & control)
IPv6 Product Doc
Public IP Subnets
Support & Contact

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.