Skip to content

Casbay BYOIP Integration Overview

BYOIP SUPPORTER
ASN AS142148
IPv4 support
IPv6 support
LOA support
ROA support
Process Manual
Locations supported
Other: Malaysia, Singapore

This page outlines the technical and procedural information required for integrating Bring Your Own IP (BYOIP) with Casbay infrastructure. Casbay supports a provider-announced BYOIP model for IPv4: your address ranges are imported into Casbay as “Additional IP” blocks and announced from Casbay’s network in the selected region. An optional Bring Your Own AS (BYOAS) feature allows you to use your own Autonomous System (AS) BGP number for routing policy, while still consuming the IP space on Casbay Cloud, VPS, and Dedicated Servers.

Provider Details

FieldInformation
Provider NameCasbay
WebsiteBring Your Own IP (BYOIP)   |   Public Cloud / Cloud Servers   |   Data Centers (Malaysia & Singapore)
ASN(s)Casbay-operated ASNs include:
AS132841 – Casbay Sdn. Bhd. (Malaysia)
AS142148 – Casbay LLC (Asia / global)
BYOIP prefixes are announced from a Casbay ASN in the target region. With BYOAS, Casbay can use your own AS BGP number for routing policy (exact origin/peering details are arranged during onboarding).
Regions SupportedCasbay operates Tier III facilities in:
Malaysia (Casbay Data Center Malaysia)
Singapore (Casbay Data Center Singapore)
BYOIP ranges are deployed into these data centers and assigned on a per-region basis: each imported block can only be attached to one region at a time (no simultaneous multi-region use).
Support ContactSupport Portal & Tickets   |   Contact Us   |   General sales / BYOIP requests via the Casbay client portal and account team.
Tech Article & DateBYOIP (Bring Your Own IP) – product page with feature list and FAQ (minimum /24, maximum /19, ARIN/APNIC/RIPE support, BYOAS, IPv4-only, timelines and SLA notes). Live as of late 2025.
BYOIP ScopeProvider-announced: You import public IPv4 ranges (min /24, max /19) registered in ARIN/APNIC/RIPE. Casbay validates and onboards the ranges as “Additional IP” blocks, then announces them from Casbay’s ASN in the chosen region. You assign these blocks to eligible services via the Casbay Control Panel or API.
BYOAS option: “Bring Your Own AS (BYOAS)” lets you use your own Autonomous System BGP number (pre-registered with a RIR) to maintain control over routing policy, while still consuming the IPs as Casbay Additional IP blocks.
Supported VersionsIPv4 only for BYOIP. FAQ explicitly states that the BYOIP service currently does not support IPv6 addresses.
Supported ServicesImported ranges can be used with Casbay “Additional IP eligible” services, specifically:
Cloud Servers / Public Cloud
Linux & Windows VPS
Dedicated Servers / High Performance Servers
IP blocks are segmented into /24s and then attached to individual services at the region level.

Technical Requirements

RequirementDetails
Prefix SizeMinimum: IPv4 /24
Maximum: IPv4 /19
Imported ranges are automatically split into /24 “Additional IP” blocks. Within a Casbay campus, you can further divide usage down to /30 or /32 assignments when mapping addresses onto individual services.
ASN Ownership RequiredNo ASN is required for basic BYOIP when Casbay announces your ranges from a Casbay ASN.
Yes if you use BYOAS: your AS number must be pre-registered with a Regional Internet Registry (ARIN, APNIC, RIPE) and eligible for BGP use.
IRR / Route ObjectsThe BYOIP page does not spell out IRR requirements or route object syntax. At minimum, your ranges must be properly registered with ARIN/APNIC/RIPE, and your AS (for BYOAS) must be recorded with the RIR. In practice, you should expect Casbay to require standard proof of IP control and up-to-date IRR data; details are handled during onboarding via the sales/support team.
ROA or LOANot explicitly documented. Industry-standard practice is to provide a signed Letter of Authorization (LOA) and maintain correct RPKI/ROA records for any advertised prefixes. Casbay’s FAQ emphasises ownership and reputation responsibilities but does not publish a formal LOA/RPKI checklist; treat LOA/ROA as expected inputs and confirm exact requirements with Casbay during setup.
RIR LimitationsBYOIP is documented as supporting IPv4 ranges registered in ARIN, APNIC, and RIPE. Other RIRs are not mentioned; if your space is held elsewhere, you should validate feasibility with Casbay first.

Step-by-Step BYOIP Process

Estimated Setup Time: Once you request BYOIP and complete verification, Casbay’s FAQ states that addresses are typically available within one business day when using a Casbay ASN, and may take a few additional business days for custom AS (BYOAS). Normal Internet BGP propagation is usually < 24 hours after the range is fully announced.

Tested By Us: Not yet

A) Standard BYOIP (Casbay announces your IPv4 ranges as Additional IP)

  • Verify that your IPv4 range is between /24 and /19, unicast, and registered to your organisation in ARIN, APNIC, or RIPE with a clean reputation (not widely blacklisted).
  • Log into the Casbay client portal and open the BYOIP request flow (via sales/client portal request) indicating the prefix(es), RIR details, and desired deployment region (Malaysia or Singapore data center).
  • Casbay validates ownership and eligibility of your ranges (RIR registration, reputation, technical suitability). Expect the team to ask for proof of control and any required LOA/RPKI/IRR details during this step.
  • After approval, Casbay imports your range as an “Additional IP” pool. The range is segmented into /24 blocks that can be assigned to eligible services in the selected region via the Casbay Control Panel (Network/IP section) or the Casbay API.
  • Attach one or more /24 blocks to your Cloud Servers, VPS, or Dedicated Servers in that region. Remember that each imported block can only be active in a single region at a time.
  • Update DNS, reverse DNS (optionally managed by Casbay), and any third-party allowlists or firewall rules to reference the new routing path through Casbay. Test reachability and latency from your key user locations.

B) BYOAS (use your own Autonomous System number)

  • Ensure that your Autonomous System Number (ASN) is pre-registered with ARIN, APNIC, or RIPE and eligible for BGP use with the imported prefixes.
  • Include your ASN details when submitting the BYOIP request, indicating that you wish to use Casbay’s BYOAS feature so your own AS number can be used for routing policy and announcements where supported.
  • Casbay coordinates the BGP configuration and any required RIR/IRR/RPKI changes so that your prefixes are imported as Additional IP blocks and announced in conjunction with your ASN according to Casbay’s BYOAS design.
  • Once implemented, manage your IP allocations as with standard BYOIP, but with routing behaviour reflecting your BYOAS configuration. Ongoing adjustments (e.g., more prefixes, new regions) are handled via Casbay support and the client portal.

References: BYOIP Product Page & FAQ, Casbay Data Centers (MY/SG), Casbay Knowledge Base.

Cost and Limitations

ItemDetails
FeesThe BYOIP product page does not list specific onboarding or recurring BYOIP surcharges. Pricing is tied to the underlying Casbay services (Cloud, VPS, Dedicated) and Additional IP usage. Any one-time setup fees, per-block charges, or BYOAS surcharges should be confirmed directly with Casbay Sales.
Bundled or StandaloneBYOIP is integrated with Casbay’s hosting portfolio as an “Additional IP” feature. It is not advertised as a standalone transit or pure network product; imported ranges are consumed by Cloud Servers, VPS, and Dedicated Servers in Casbay data centers.
Traffic/Peering RestrictionsFAQ explicitly states that a given IP block can only be assigned to one region at a time. Casbay’s own BGP peering and upstream mix are managed by Casbay and are not directly tunable via BYOIP. All usage is subject to Casbay’s Terms of Service, Acceptable Use Policy, and IP Address policy (including anti-abuse expectations).
Other Limitations
  • BYOIP currently supports IPv4 only; IPv6 is not supported in this product.
  • No dedicated SLA is attached to BYOIP itself; only the underlying service (Cloud/VPS/Dedicated) may carry an SLA.
  • IP ranges must be registered with ARIN/APNIC/RIPE and be technically suitable for global routing (generally not widely blacklisted and properly maintained).
  • Operational details such as maximum number of prefixes and per-customer limits are not published and should be checked with Casbay for larger deployments.

Automation & Developer Access

  • API Access: Yes — the BYOIP FAQ notes that imported IP blocks can be “dynamically assigned … through the Casbay Control Panel (Network/IP section) or Casbay API.” Casbay Cloud Panel exposes an API used by their WHMCS modules and automation tooling.
  • Control Panel: Casbay client portal provides UI workflows for requesting BYOIP, viewing Additional IP pools, and assigning /24 blocks to services on a per-region basis.
  • WHMCS / Integrations: Casbay publishes WHMCS modules for resellers that integrate with the Casbay Cloud Panel API (API key and password from the Cloud Panel’s “API Credentials” section). BYOIP-backed services can be exposed via these integrations once IPs are imported.
  • Terraform / SDKs: No official Terraform provider or language-specific SDK is documented for Casbay as of now; infrastructure-as-code is typically built on top of the Cloud Panel API and reseller modules.

Abuse & Reputation Management

  • Casbay’s BYOIP description emphasises that you retain responsibility for the “credibility of your IP addresses” and that bringing your own range is mainly to preserve reputation (email deliverability, anti-spam posture, allowlists).
  • You are expected to maintain clean IP reputation, handle abuse reports, and remediate any listings on blocklists/RBLs. Casbay provides the infrastructure and DDoS protection but does not assume ownership of historical reputation issues on your prefixes.
  • Ranges with severe or unresolved abuse or blacklist status may be refused for BYOIP onboarding or may require remediation before import. Ongoing monitoring and delisting efforts are the customer’s responsibility, in line with Casbay’s Acceptable Use Policy and IP Address policy.

Casbay Homepage
Bring Your Own IP (BYOIP)
Public Cloud / Cloud Servers
Data Centers (Malaysia & Singapore)
Casbay Knowledge Base
Support & Ticket Portal
Contact & Sales

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.