ArvanCloud BYOIP Integration Overview
Location
This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Arvancloud Cloud Server infrastructure. Arvancloud currently supports a provider-announced BYOIP model: your IPv4 prefix is originated by Arvancloud’s backbone (AS202468) and attached to your Cloud Server private networks and instances. You do not run your own BGP sessions; instead, you authorise Arvancloud to advertise your range on your behalf.
Provider Details
| Field | Information |
|---|---|
| Provider Name | ArvanCloud |
| Website | BYOIP (Bring Your Own IP) | Cloud Server > Network docs | Arvancloud Homepage |
| ASN(s) | Primary announcing ASN: AS202468 (AbrArvan-AS – Noyan Abr Arvan Co.). The BYOIP LOA template explicitly authorizes Arvancloud with AS202468 to advertise your IP blocks. |
| Regions Supported | BYOIP is a feature of the Cloud Server product and is enabled per data center/region that supports Cloud Server. In the panel you first select the desired data center, then choose BYOIP under Network. Concrete region codes (e.g. ir-thr-c2) and locations are managed by Arvancloud; refer to Cloud Server and Network Maps for the current list of available regions where BYOIP can be requested. |
| Support Contact | Contact Us | Help Center | General support and BYOIP coordination via the Cloud Server user panel (tickets) and email. |
| Tech Article & Date | BYOIP – Cloud Server > Network documentation describing requirements, LOA template, RIPE route object creation, and implementation flow (accessed 2025-11). |
| BYOIP Scope | Provider-announced: You bring a dedicated IPv4 range, sign a Letter of Agency (LOA), and create a RIPE route object listing AS202468 as origin. Arvancloud then advertises the prefix on its backbone and makes the range available in your Cloud Server private network so you can create instances with your own IPs. There is no customer BGP session in the documented flow. |
| Supported Versions | IPv4 only for BYOIP. The BYOIP guide refers to “IP range” with a required /24 (256 IPv4 addresses) and RIPE route object configuration for AS202468. IPv6 support exists in Arvancloud networking generally, but BYO-IPv6 is not documented for BYOIP at this time. |
| Supported Services | Arvancloud Cloud Server instances and private networks. After onboarding, your dedicated range appears in the Private Network section of the Cloud Server panel and can be used to create instances that directly use your own IP range. BYOIP is specifically tied to Cloud Server networking, not CDN. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | The dedicated IP range must be: – Unicast type. – At least /24 (256 IPv4 addresses). Smaller prefixes are not accepted for BYOIP. The documentation does not specify support for IPv6 prefixes in this workflow. |
| ASN Ownership Required | No. You must own the IP range, but you are not required to operate your own ASN or BGP session. The RIPE route object is created with AS202468 (Arvancloud) as origin, and the LOA explicitly authorizes Arvancloud’s ASN to advertise your subnet(s). |
| IRR / Route Objects | You must create a RIPE “route” object for your prefix, setting the origin field to AS202468. This is done via the RIPE Database panel: create a Route object, fill in your IP range in the route field, and use AS202468 as origin, then submit. Arvancloud relies on this RIPE object when implementing BYOIP. |
| ROA or LOA | LOA: Required. After your request is approved, Arvancloud sends you a Letter of Agency (LOA) to sign, based on their template. It confirms you own the IP range and authorize Arvancloud (AS202468) to advertise it; it also states that you are responsible for handling abuse and legal issues related to that range. ROA (RPKI): The BYOIP guide does not explicitly mention ROAs. General best practice is to keep RPKI state consistent with the intended origin (AS202468) if you are using RPKI. |
| RIR Limitations | The documented procedure assumes the IP space is managed in the RIPE database (they reference the RIPE panel and RIPE Database UI). Practically, you must be able to create or update a route object that lists AS202468 as origin. For non-RIPE resources, coordination with Arvancloud support is required. |
Step-by-Step BYOIP Process
Estimated Setup Time: Arvancloud states that your BYOIP request is reviewed within 72 business hours, and once RIPE changes are applied, implementation in Arvancloud typically takes about 48 hours. Allow additional time for normal Internet BGP propagation (often < 24 hours after announcements start).
Tested By Us: Not yet
Provider-announced BYOIP (Arvancloud originates your /24+ on AS202468)
References: BYOIP, Cloud Server > Network, Cloud Server – Getting Started.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | The BYOIP documentation directs users to the Cloud Server pricing page for information about costs and charges. No specific public BYOIP surcharge is stated in the doc; BYOIP is treated as an advanced Cloud Server networking feature. Exact onboarding and recurring fees should be confirmed with Arvancloud Sales/Support. |
| Bundled or Standalone | BYOIP is integrated with Arvancloud Cloud Server networking and Private Network features. It is not advertised as a standalone network-only product; you consume your own range through Cloud Server instances and private networks once the range is onboarded. |
| Traffic/Peering Restrictions | The dedicated range must not be blacklisted by RIPE. You are responsible for resolving abuse reports and any legal issues related to the IP range, as explicitly stated in the BYOIP terms and LOA description. Arvancloud’s backbone and peering policies are managed internally and are not customer-tunable via BYOIP. |
| Other Limitations |
|
Automation & Developer Access
Abuse & Reputation Management
Related Resources
Arvancloud Homepage
BYOIP (Bring Your Own IP) – Cloud Server
Cloud Server > Network Documentation
Cloud Server – Getting Started
API Documentation
Developer Tools (API, CLI, SDK, Terraform)
Network Maps
IP Ranges
Cloud Server Pricing