Cherry Servers BYOIP Integration Overview
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 | JP - AS210162 |
| Regions Supported | LT-Šiauliai, NL - Amsterdam, DE - Frankfurt, SE - Stockholm, US - Chicago, SG - Singapore, JP - Tokyo (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 accepted from /24 (256 IPs) up to /20 (4,096 IPs), maximum six prefixes per request. 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 is now explicitly required to authorize Cherry Servers to announce the IP range, including date, provider information, the region's Cherry Servers ASN, IP information, an authorization statement, owner name and address, and signature (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+)
Step 1
Submit your exact IPv4 range(s) to Cherry (via account manager or support).
Step 2
Ensure your range is a separate INETNUM and set mnt-routes: DUOMENUCENTRAS-MNT.
Step 3
Cherry creates the required route objects and begins announcing the prefix from the region’s ASN.
Step 4
Propagation
allow up to 24 hours for full global reachability.
Step 5
Select the target location and corresponding Cherry ASN (LT AS16125, DE AS213896, NL AS59642, SE AS214159, SG AS216444, US AS204770, JP AS210162).
Step 6
Update your ASN object with proper import/export remarks toward that Cherry ASN.
Step 7
Submit your ASN, prefixes, ROA records (required), and LOA (recommended) for validation.
Step 8
After approval, enable Local BGP in the Client Portal and apply the provided BIRD/routing config on your servers.
Step 9
Announce your prefixes; monitor propagation (HE BGP Toolkit, RIPEstat, etc.).
Allow up to 24 hours for global acceptance.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | A one-time setup fee of EUR200/$229 applies per BYOIP request (not per subnet); standard service pricing otherwise applies. |
| 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, JP. 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.
Related Resources
Published 14 October 2025 · Updated 29 September 2026