How to Bring Your Own IP Range (BYOIP) to Cherry Servers

Cherry Servers understands that flexibility and control over your server and its operations are crucial for smooth project management. That is why we allow customers to bring their own IP address ranges for use with Cherry Servers deployments.

We permit you to bring IP subnets ranging from /24 (256 IP addresses) to /20 (4,096 IP addresses) for use with your servers at Cherry Servers, giving you the flexibility to manage your project. Customers may bring up to six prefixes per request, so we strongly recommend aggregating your IP space whenever possible by using larger prefix sizes, such as /23, /22, /21, or /20, rather than multiple smaller subnets. If your deployment requires more than six prefixes, please contact Cherry Servers support to discuss the available options.

#Fees

Because BYOIP requests require manual verification and configuration by our network administrators, a one-time setup fee of €200/ $229 applies to each BYOIP request submitted to Cherry Servers. The process may take up to 24 hours for the worldwide ISPs to recognize the newly added IP range.

The fee is charged on a per request basis, not per subnet. Therefore, we recommend including all subnets you may require in a single request to avoid additional setup fees.

Any additional custom requests regarding setup process may add additional fees determined by the request complexity. This includes changing configured subnets or asking for a custom routing solution. Request complexity and what constitutes a "custom solution" is determined by Cherry Servers.

#Anycast Announcements

If you intend to announce your subnet from multiple locations (Anycast) or announce the same subnet from a different ASN (commonly referred to as a Multi-Origin AS announcement), there are several important considerations.

Anycast routing can be unpredictable because Internet routing decisions are made independently by upstream networks and transit providers. While Cherry Servers allows Anycast deployments, we cannot guarantee that traffic will always follow your desired routing path or produce the expected results.

A common example occurs when a customer announces the same ASN from multiple locations and attempts to communicate between those locations using IP addresses belonging to that ASN. Many BGP implementations reject routes that contain the same ASN multiple times within the AS path to prevent routing loops.

For example: AS65001 → AS65010 → AS65030 → AS65001

In this case, AS65001 appears at both the beginning and end of the AS path. Some routers may interpret this as an AS-path loop and reject the route.

Customers planning Anycast or Multi-Origin ASN deployments should ensure they fully understand the routing implications and limitations associated with these configurations.

#Support for Custom Routing Requirements

Cherry Servers will announce your subnets to the Internet and make the IP addresses routable to your servers using one of the supported configuration methods, such as Static Route or Gateway mode.

If you experience routing issues, you must provide detailed diagnostic information, including:

• Source and destination IP addresses
• Ping results
• Traceroute results from both sides
• MTR reports from both sides
• A clear description of the observed behavior

Our network administrators will review the provided information and investigate whether improvements can be made within the Cherry Servers network.

If our investigation determines that no improvement can be made from the Cherry Servers network side, Cherry Servers cannot guarantee resolution of routing behavior caused by external networks, transit providers, Internet routing policies, or third-party infrastructure.

By proceeding with the BYOIP process, the customer acknowledges and accepts these limitations. For larger deployments involving multiple servers, we strongly recommend testing with a small subset of servers before expanding to production-scale deployment. This allows you to validate routing behavior and ensure the solution meets your requirements.

#Processing Time

Depending on the complexity of the request and the information provided, the BYOIP provisioning process may take several business days to complete.

BYOIP requests are handled by our network administrators during standard business hours in Lithuania. Customers located in significantly different time zones should be aware that communications sent outside these hours may not be reviewed until the next business day.

For example:

• Requests submitted near the end of the business day may not be reviewed until the following business day.
• Requests submitted close to or after business hours on Friday will generally begin to be processed on the next business day, typically Monday.

It is important to distinguish between network operations and service provisioning activities.

Our network administrators monitor and maintain the Cherry Servers network infrastructure 24/7 to ensure service availability and network quality. However, customer service requests such as BYOIP provisioning, configuration changes, and similar administrative tasks are processed during regular business hours.

#Gateway Subnet Limitations

If you plan to use your BYOIP allocation as a gateway subnet for virtual machines, there are several important limitations to consider.

By default, BYOIP ranges are configured using the Static Route method. This provides maximum flexibility and is suitable when the subnet will be used directly on the host server.

However, when the subnet is intended for use by virtual machines, network segmentation within the Cherry Servers data center may introduce limitations.

Servers located in different network segments may not be able to participate in the same Layer 2 broadcast domain (VLAN) required for Gateway-mode operation. As a result, virtual machines hosted on different network segments may be unable to share the same gateway subnet.

To mitigate these limitations, you may consider the following options:

• Ask your sales representative to place all required servers within the same network segment whenever possible.
• Request that your BYOIP allocation be divided into smaller subnet blocks (for example, four /26 subnets) that can be assigned across different network segments.

While the servers may not share the same broadcast domain (VLAN), this approach allows IP addresses from your BYOIP allocation to be distributed across multiple network segments while maintaining address availability where needed.

#Instructions to Bring Your IP Range to Cherry Servers AS

For a smooth integration, we recommend that you first ensure that your IP prefixes are not blocked in public IP databases for suspected botnets or spamming. Blocked prefixes may be filtered by ISPs, leading to reachability issues.

To get started, please contact our dedicated support engineer team to inform them that you intend to bring your own IP range, and provide them with the required information according to the instructions below. This will help us assist you in expediently completing the process.

#1. Select a Cherry Servers Location

Choose the Cherry Servers data center you would like to bring your own IP range to, based on where your servers are deployed. You will need the related Autonomous System Number (ASN) to create a new route object, as well as a Route Origin Authorization (ROA). Cherry Servers region ASN are listed in the table below.

#2. Create Route Object and ROA Record

To establish routing with Cherry Servers, update your IP prefix through the Regional Internet Registry (RIR) or Internet Routing Registry (IRR) where it is registered. When creating an ROA for the intended IP prefix, use the Cherry Servers AS for the region you selected, and generate an ROA record.

If your IP range is provisioned through an IP renting service, they may offer the option to create a route object and ROA on your behalf through an easy-to-use panel.

#3. Create LOA Documentation

To authorize Cherry Servers to announce your IP range, we require a Letter of Authorization (LOA). This document confirms that we have your express permission, and acts as a safeguard for your IP against hijacking.

If you own the subnet, you will need to create the LOA with the following information:

• Date - the date that the LOA was signed and issued;
• Provider Information - the full legal name of the Internet Service Provider (ISP) or carrier being granted the authority to announce the IP space;
• Cherry Servers ASN - the Autonomous System Number (ASN) for the Cherry Servers region that will originate the routes;
• IP Information - The specific IP address range that the provider is authorized to announce;
• Authorization Statement - A clear statement that the owner of the IP range authorizes Cherry Servers to announce the specified IP range on their behalf;
• Owner’s Name - the full name of the individual or organization that owns the IP space;
• Owner’s address - These details must match the information registered with the relevant Regional Internet Registry (RIR);
• Signature.

If your IP range is provisioned through an IP renting service, you may have the ability to download an LOA for the subnet as a PDF file.

#4. Submit Your IP Prefix for Validation

Cherry Servers will need to verify the validity of your IP prefix to ensure compliance with security policies and network integrity. Please provide our dedicated support engineer team with the following information:

• The IP prefixes you wish to bring,
• ROA records for the IP prefixes,
• LOA documentation.

#5. Wait for Global Propagation

After submitting information to our engineer support team, please allow up to 24 hours for your IP range to become available. ISPs worldwide may take up to 24 hours to recognize the new subnet.

You can monitor the propagation of your announced prefix using tools such as:

• Hurricane Electric's BGP Toolkit – Provides visibility into your BGP routes across the internet;
• RIPEstat – Analyzes routing and ASN details for your prefix;

Once complete, your IP prefix will be fully operational and available for use under the server announcing it.

If you have any further questions, issues, or concerns, please don’t hesitate to email our support team at: support@cherryservers.com