Cherry Servers BYOIP Integration Overview

Location
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
Field | Information |
---|---|
Provider Name | Cherry Servers |
Website | Bring 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 Supported | LT–Šiauliai, NL–Amsterdam, DE–Frankfurt, SE–Stockholm, US–Chicago, SG–Singapore (per Local BGP docs) |
Support Contact | 24/7 Support (chat/ticket/email) | Contact methods |
Tech Article & Date | Bring Your Own IP Range (provider‑announced) & Bring your own ASN with IP prefix (customer‑ASN). |
BYOIP Scope | Provider‑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 Versions | IPv4 & IPv6 (platform IPv6 supported; BYO‑IPv6 via customer‑ASN BGP). IPv6 product doc |
Supported Services | Dedicated Servers, Cloud VDS/VPS, Storage VPS; works with Floating IPs and Public IP Subnets; Local BGP for HA and control. |
Technical Requirements
Requirement | Details |
---|---|
Prefix Size | Provider‑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 Required | No (provider‑announced flow). Yes (customer‑ASN BGP flow). |
IRR / Route Objects | Provider‑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 LOA | ROAs required for customer‑ASN; LOA recommended. For provider‑announced: LOA not stated as required; Cherry validates ownership and creates route objects (ROA recommended). |
RIR Limitations | Not 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+)
B) Customer‑ASN + Prefixes via Local BGP (you originate)
References: BYO IP Range, Bring your own ASN, Local BGP.
Cost and Limitations
Item | Details |
---|---|
Fees | No 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 Restrictions | Prefixes must not be blocklisted and must maintain good reputation; adhere to Cherry’s IP usage and acceptable‑use policies. |
Other Limitations | Local 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
Abuse & Reputation Management
Related Resources
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