Skip to content

ArvanCloud BYOIP Integration Overview

BYOIP SUPPORTER
ASN AS202468
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: China, India, Japan, Singapore, Germany, Netherlands, Poland, Spain, United States, Brazil, Australia

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

FieldInformation
Provider NameArvanCloud
WebsiteBYOIP (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 SupportedBYOIP 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 ContactContact Us   |   Help Center   |   General support and BYOIP coordination via the Cloud Server user panel (tickets) and email.
Tech Article & DateBYOIP – Cloud Server > Network documentation describing requirements, LOA template, RIPE route object creation, and implementation flow (accessed 2025-11).
BYOIP ScopeProvider-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 VersionsIPv4 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 ServicesArvancloud 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

RequirementDetails
Prefix SizeThe 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 RequiredNo. 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 ObjectsYou 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 LOALOA: 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 LimitationsThe 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)

  • In the Cloud Server user panel, choose the desired data center/region, go to the Network section, and select the “BYOIP” option to open the BYOIP request form.
  • Fill in your personal and company details, specify the IP subnet (/24 or larger, unicast, not blacklisted in RIPE), and add any additional notes. Read the guidance and submit the request.
  • Arvancloud reviews your request and contacts you within approximately 72 business hours. If approved, they send a Letter of Agency (LOA) template via email for you to complete and sign on company letterhead.
  • Sign the LOA (confirming that the IP range belongs to you and authorizing Arvancloud with AS202468 to advertise it) and return it as instructed. Arvancloud staff will guide you through this step if needed.
  • Log in to your RIPE Database account, create a new “route” object for your IP prefix, and set the origin field to AS202468 (Arvancloud’s AS number). Submit the route object so it becomes visible in RIPE.
  • After RIPE configuration is complete, Arvancloud implements BYOIP on their infrastructure (typically within ~48 hours). Your range then appears under the Private Network section in the user panel, where you can attach it to networks and create instances using your own IP range.
  • Note: If you delete the private network associated with your BYOIP range before deploying instances, the service must be redefined by Arvancloud, so avoid deleting that network unintentionally.

References: BYOIP, Cloud Server > Network, Cloud Server – Getting Started.

Cost and Limitations

ItemDetails
FeesThe 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 StandaloneBYOIP 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 RestrictionsThe 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
  • Unicast IPv4 only; minimum prefix size /24.
  • Documented for RIPE-managed space with a RIPE route object referencing AS202468.
  • If you remove the private network associated with your BYOIP range (without instances using it), the service must be redefined.
  • All usage remains subject to Arvancloud’s Terms of Service, Acceptable Use, and legal policies.

Automation & Developer Access

  • API Access: Yes — Arvancloud exposes REST APIs for Cloud Server and other products (instances, images, networks, etc.) via the <a href="https://www.arvancloud.ir/en/dev/api" target="_blank" rel="noreferrer noopener">API Documentation</a>. BYOIP onboarding itself is initiated via the user panel and support, but once configured, your infrastructure that uses the BYOIP range can be managed through APIs.
  • Terraform: Official <a href="https://docs.arvancloud.ir/en/developer-tools/terraform/" target="_blank" rel="noreferrer noopener">Arvancloud Terraform Provider</a> for managing cloud infrastructure as code. You can define Cloud Server instances, networks, and related resources that consume your BYOIP range via Terraform after onboarding.
  • CLI: Arvancloud currently provides a CLI primarily focused on the Cloud Container service; general resource management is still mostly via API and panel. BYOIP actions are not documented as CLI-driven and remain manual/support-driven.
  • SDKs: Arvancloud offers SDK resources (especially for Object Storage) and general developer tools. While there is no dedicated BYOIP SDK, you can integrate deployments that use your BYOIP-backed networks via the standard APIs and SDKs.

Abuse & Reputation Management

  • The BYOIP terms require that your dedicated IP range not be blacklisted in RIPE; Arvancloud may reject or request remediation for ranges with poor reputation.
  • The LOA text clarifies that you, as the IP holder, are responsible for following up on and resolving abuse reports or other legal matters related to the range. Arvancloud provides the infrastructure and advertisements but does not take over responsibility for abuse of your IPs.
  • Ongoing monitoring of blocklists, RBLs, and reputation services, plus any delisting efforts, remains the customer’s responsibility, in line with Arvancloud’s legal and acceptable-use policies.

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

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.