IP Address Announcement: A Complete Technical Guide to BYOIP with AlexHost

Bring Your Own IP (BYOIP) is the practice of announcing a block of IP addresses you own — registered under your organization in a Regional Internet Registry (RIR) such as RIPE NCC — through a third-party network provider's BGP infrastructure. AlexHost enables this on its own autonomous system, AS 200019, allowing you to use your IPv4 or IPv6 prefixes on a rented dedicated server while retaining full ownership and portability of your address space.

This service is particularly valuable for businesses that have accumulated legacy IP blocks, need consistent IP reputation across providers, or require provider-independent (PI) addressing for compliance, anti-spam, or multi-homing purposes.

What Is BGP Subnet Announcement and Why It Matters

When you own a block of IP addresses, those addresses are only reachable on the public internet if they are announced via the Border Gateway Protocol (BGP). BGP is the inter-domain routing protocol that governs how traffic is directed between autonomous systems (AS) across the global internet. Without an active BGP announcement, your IP block is invisible — it cannot receive or send traffic.

By contracting AlexHost to announce your prefix through AS 200019, your IP block becomes globally routable. Traffic destined for your addresses is directed to AlexHost's network, where it is forwarded to your dedicated server. This architecture gives you the best of both worlds: the infrastructure reliability of a managed hosting provider combined with the IP reputation, ownership, and portability of your own registered address space.

This is fundamentally different from using IP addresses assigned by a hosting provider. Provider-assigned IPs are tied to that provider's ASN and cannot be moved. Your own PI (Provider-Independent) block travels with you.

Core Use Cases for BYOIP Announcement

Understanding when BYOIP is the right architectural choice prevents costly mistakes. The following scenarios represent the most technically justified reasons to use this service:

• IP reputation preservation: Businesses running high-volume email, payment processing, or ad-tech infrastructure build reputation on specific IP ranges. Moving to a new provider without BYOIP would require rebuilding that reputation from scratch.
• Regulatory and compliance requirements: Certain industries require that IP addresses be registered to the operating entity, not a third-party hosting provider.
• Multi-homing and redundancy: Announcing the same prefix from multiple ASNs (AS 200019 and another provider simultaneously) enables traffic engineering and failover without DNS changes.
• Anti-abuse and blacklist control: When your IPs are listed in your own RIPE/ARIN/ARIN database record, abuse complaints and delisting requests go directly to you, giving you faster resolution control.
• Legacy IPv4 block monetization: Organizations holding large IPv4 allocations can put idle address space to work without selling it.

Technical Architecture: How AlexHost Announces Your Prefix

The announcement process follows a precise sequence of technical steps. Understanding this architecture helps you prepare correctly and avoid routing failures.

BGP Session Establishment

AlexHost's routers (operating under AS 200019) establish a BGP peering session. Your prefix is added to the BGP routing table and propagated to AlexHost's upstream transit providers and peering partners. From that point, the prefix is visible in the global routing table and reachable from any point on the internet.

ROA and RPKI: Mandatory Security Layer

Before or immediately after the announcement, you must configure a Route Origin Authorization (ROA) record in the RPKI (Resource Public Key Infrastructure) system. This is a cryptographically signed object stored in your RIR's RPKI repository (e.g., RIPE NCC's RPKI portal) that states:

• Which ASN is authorized to originate your prefix (in this case, AS 200019)
• The maximum prefix length that can be announced

This step is not optional. Without a valid ROA, your prefix will fail RPKI validation at many networks, resulting in route filtering. Major transit providers and IXPs increasingly enforce RPKI-valid-only routing policies. An invalid or missing ROA means your traffic will be silently dropped at a growing number of network boundaries.

The correct ROA entry for AlexHost announcement looks like this:

Origin ASN:    AS200019
Prefix:        your.prefix.here/24 (or your actual prefix)
Max Length:    /24 (for IPv4) or /48 (for IPv6)

RIPE Database Updates

In parallel, you must update the RIPE database (or your relevant RIR database) to reflect the routing policy. This includes:

• Creating or updating a route object that associates your prefix with AS 200019
• Ensuring your aut-num object includes an export policy permitting AS 200019 to originate your prefix
• Verifying your inetnum or inet6num object is current and correctly attributed

Failure to update the RIPE database does not prevent routing, but it creates inconsistencies that can trigger abuse reports and complicate future transfers or audits.

IPv4 Announcement: Pricing and Policy

AlexHost supports IPv4 prefix announcements with a minimum prefix size of /24 (256 addresses). This is the globally accepted minimum for IPv4 BGP announcements — prefixes smaller than /24 are filtered by the majority of internet routers and will not propagate reliably across the global routing table.

Pricing for larger blocks is calculated proportionally. A /22 block contains four /24 blocks, so the monthly fee would be €80 (4 x €20). The one-time setup fee applies per announcement event, not per /24 within the block.

The setup fee waiver when ordering a Dedicated Server for a minimum of three months represents a meaningful cost reduction for businesses planning a sustained deployment.

IPv6 Announcement: Pricing and Policy

IPv6 announcements follow a separate policy with a minimum prefix size of /48. A /48 provides 65,536 /64 subnets — more than sufficient address space for virtually any enterprise deployment.

IPv6 RPKI and ROA requirements are identical to IPv4. You must create a valid ROA in your RIR's RPKI system authorizing AS 200019 to originate your /48 (or larger) prefix before the announcement goes live.

Note that while IPv6 addresses are abundant, the routing table slot your prefix occupies is a shared global resource. AlexHost's minimum prefix policy (/48) aligns with RIPE NCC's recommendations and prevents unnecessary routing table inflation.

IPv4 vs. IPv6 Announcement: Side-by-Side Comparison

Eligibility and Service Constraints

This service is exclusively available for dedicated servers hosted at AlexHost. It is not available for VPS instances. This constraint exists for a technically sound reason: BGP announcement and prefix routing require dedicated, deterministic network resources. Shared or virtualized environments introduce routing complexity and potential instability that is incompatible with reliable BGP operation.

If you are currently on a VPS and need BYOIP capabilities, the correct path is to migrate to a Dedicated Server before initiating the announcement process.

Common Technical Pitfalls and How to Avoid Them

Experienced network engineers who have deployed BYOIP across multiple providers consistently encounter the same failure modes. Being aware of these before you start saves significant troubleshooting time.

Pitfall 1: ROA Created for Wrong Max-Length

A common error is setting the ROA max-length to a value more specific than the announced prefix. For example, if you own a /22 but plan to announce only a /24, your ROA max-length must be set to /24 or larger. If it is set to /22 only, the /24 announcement will be RPKI-invalid and filtered.

Pitfall 2: Stale Route Objects in RIPE

If your prefix was previously announced by a different ASN, an old route: object may still exist in the RIPE database pointing to that ASN. This creates a conflict. You must delete or update the old route object before creating a new one for AS 200019. Failing to do this can cause your announcement to be flagged as a potential BGP hijack by route security monitoring systems such as MANRS or BGPmon.

Pitfall 3: Prefix Not Registered in RIR

You cannot announce an IP block you do not legitimately hold in an RIR database. AlexHost will verify that the prefix is registered to your organization before completing the setup. Attempting to announce unregistered or third-party space is a BGP hijack — a serious violation with legal and operational consequences.

Pitfall 4: Forgetting Reverse DNS Delegation

After your prefix is announced, you should also delegate reverse DNS (rDNS) for your address block. Without rDNS, many mail servers will reject connections from your IPs, and various security tools will flag your addresses. Update the domain: attribute in your RIPE inetnum object and configure PTR records accordingly.

Pitfall 5: Assuming Instant Global Propagation

BGP route propagation is not instantaneous. After AlexHost activates your announcement, allow 15 to 60 minutes for the route to propagate across the global routing table. Use tools like bgp.he.net or RIPE's RIS Live to monitor propagation status before testing connectivity.

How to Order: Step-by-Step Process

1. Verify RIR ownership. Confirm your prefix is registered in RIPE NCC (or relevant RIR) under your organization's LIR or PI allocation.
2. Prepare your RIPE objects. Ensure your inetnum/inet6num, aut-num, and route/route6 objects are current or ready to be created.
3. Open a support ticket via the AlexHost client portal. Include your prefix, your organization's RIPE handle, and your dedicated server details. Response time is within 30 minutes.
4. Complete payment for the one-time setup fee and first monthly period.
5. Create your ROA in the RIPE NCC RPKI portal, authorizing AS 200019 as the origin ASN for your prefix.
6. Update RIPE route objects to reflect AS 200019 as the originating AS.
7. Verify propagation using BGP looking glass tools after AlexHost confirms the announcement is active.
8. Configure rDNS for your address block.

For ongoing questions, AlexHost support is accessible via the ticketing system or the Telegram live chat channel.

Integration with AlexHost Infrastructure

AlexHost operates its own network under AS 200019, with direct connectivity to major transit providers and internet exchange points. This means your announced prefix benefits from AlexHost's upstream peering relationships, reducing latency and improving reachability across different geographic regions.

For organizations running latency-sensitive workloads — such as real-time applications, financial trading infrastructure, or high-performance compute jobs — pairing BYOIP announcement with GPU Hosting or bare-metal Dedicated Servers gives you both the compute performance and the network identity control your architecture demands.

If your deployment includes web-facing services under your own IP block, pairing the announcement with properly issued SSL Certificates tied to your domain ensures end-to-end security that aligns with your IP ownership posture.

Organizations managing their own IP space often also control their own domain infrastructure. Domain Registration through AlexHost allows you to consolidate DNS, domain, and IP management under a single provider relationship, simplifying operational overhead.

Decision Matrix: Is BYOIP Announcement Right for You?

Use this matrix to determine whether this service fits your technical and business requirements before committing.

Technical Key-Takeaway Checklist

Before submitting your order ticket, verify the following:

• Your prefix is registered in RIPE NCC (or ARIN/APNIC) under your organization
• The minimum prefix size is /24 for IPv4 or /48 for IPv6
• You have access to your RIR portal to create and modify ROA records
• You have identified and resolved any stale route objects from previous ASN announcements
• You are ordering on a dedicated server — VPS instances are not eligible
• You understand that the monthly fee scales per /24 block (e.g., a /22 = 4 x €20 = €80/month)
• Reverse DNS delegation is planned as part of your post-announcement configuration
• You have allocated 15–60 minutes for global BGP propagation after announcement activation

Frequently Asked Questions

What is the minimum IPv4 prefix size AlexHost can announce?

The minimum is /24. Prefixes more specific than /24 (such as /25, /26, etc.) are filtered by the majority of internet routers and will not propagate reliably across the global routing table, making them non-functional for public internet use.

Can I use BYOIP announcement on a VPS?

No. This service is exclusively available for dedicated servers. BGP announcement requires dedicated network resources that are incompatible with shared or virtualized hosting environments.

What happens if I do not create an ROA before the announcement?

Your prefix will be RPKI-unknown or RPKI-invalid at networks enforcing route origin validation. An increasing number of major ISPs and transit providers filter RPKI-invalid routes, meaning your traffic will be silently dropped at those network boundaries. Creating a valid ROA authorizing AS 200019 before or immediately after announcement is essential.

How is the cost calculated for a /22 announcement?

A /22 contains four /24 blocks. The monthly fee is €20 per /24, so a /22 costs €80 per month in announcement fees, plus your dedicated server cost. The one-time setup fee applies once per announcement event.

Can I announce the same prefix from AlexHost and another provider simultaneously?

Yes. Announcing the same prefix from multiple ASNs is called multi-homing and is a legitimate, widely used traffic engineering technique. You would need a valid ROA that authorizes both ASNs, or separate ROA records for each. Coordinate with AlexHost support to ensure the announcement configuration supports your multi-homing topology correctly.