AlexHost BYOIP Integration Overview

Before you commit
You cannot bring your own ASN - prefixes are announced under AS200019, registered to ALEXHOST SRL (RIPE, Moldova).

Searching for the best IP providers? AlexHost supports BYOIP: you bring an IPv4 or IPv6 prefix, and they announce it from their own ASN, AS200019 (registered to ALEXHOST SRL in the RIPE region, Moldova). Bringing your own ASN is not an option here, which keeps onboarding simple - no BGP session to run, just registry prep. What it costs, and which product lines it applies to, is not published by the vendor, so confirm both with AlexHost before you plan around it.

Provider Details

FieldInformation
Provider NameAlexHost
ASN(s)AS200019, registered to ALEXHOST SRL (RIPE, Moldova). Your prefix is announced under this ASN - customer ASNs are not supported.
BYOIP ScopeIPv4 and IPv6 prefix announcement under AlexHost's own ASN.
Supported VersionsIPv4: yes. IPv6: yes.

Caveats and Gotchas

  • No bring-your-own-ASN: everything is announced under AS200019. If you need your own ASN on the path, this is not the right home for your prefix.
  • Registry prep is on you: a route object in the RIPE database and a correct aut-num export policy are required before anything gets announced.
  • Pricing and product-line scope are not published - ask before you commit.

Technical Requirements

RequirementDetails
Prefix SizeIPv4: /24 minimum. IPv6: /48 minimum.
ASN Ownership RequiredNo. AlexHost announces under its own AS200019 and does not accept customer ASNs.
LOANot published by the vendor.
RPKI ROANot published by the vendor.
IRR Route ObjectRequired - a route object in the RIPE database, plus a correct aut-num export policy.
RIR LimitationsNot published by the vendor.
Ownership ProofNot published by the vendor.
Contract or CommitNot published by the vendor.

Step-by-Step BYOIP Process

Step 1
Check your prefix size

IPv4 must be /24 or larger, IPv6 must be /48 or larger.

Step 2
Create the RIPE route object

register a route or route6 object for your prefix in the RIPE database.

Step 3
Fix the aut-num export policy

make sure the export policy is correct, per AlexHost's documentation.

Step 4
Request the announcement

ask AlexHost to announce your prefix under AS200019 - customer ASNs are not accepted.

Step 5
Confirm the timeline

turnaround is not published, so agree on expectations when you submit the request.

Cost and Limitations

ItemDetails
FeesNot published by the vendor.
Bundled or StandaloneNot published by the vendor.
Other LimitationsMinimum prefix sizes are /24 for IPv4 and /48 for IPv6. Customer ASNs are not supported - everything is announced under AS200019.
What Is RPKI? ROAs, Origin Validation and Your BYOIP Prefix
What Is an ASN? The Number Behind Every BYOIP Announcement
Who Actually Owns an IP Address? (And Why It Matters for BYOIP)

Published 11 September 2026

More BYOIP supporters

All BYOIP supporters

FAQ