OuiHeberg BYOIP Integration Overview

Company	OuiHeberg
Homepage	https://www.ouiheberg.com
BYOIP Product	BGP VPS
Own ASN	AS208226 (registered with RIPE, listed on PeeringDB with an open peering policy)
Locations	Marseille, Frankfurt, Amsterdam, New York

Minimum IPv4 prefix	/24 ("A prefix must be at least a /24 in IPv4 or a /48 in IPv6 to be routable on the Internet.")
Minimum IPv6 prefix	/48 ("A prefix must be at least a /24 in IPv4 or a /48 in IPv6 to be routable on the Internet.")
ASN requirement	Customer must own an ASN assigned by their RIR (RIPE, ARIN, etc.); OuiHeberg offers assistance obtaining one
IP ownership verification	Customer must be the legitimate holder of the IP addresses with an RIR
LOA support	Not publicly documented
ROA support	OuiHeberg recommends creating matching ROAs with the customer's RIR for announced prefixes

Step 1

Confirm you hold a /24 (IPv4) or /48 (IPv6) minimum prefix registered to you at an RIR, and your own ASN.

Step 2

Use OuiHeberg's public Looking Glass (lg.as208226.net) to verify routes before ordering.

Step 3

Contact OuiHeberg support to validate your setup.

Step 4

Order a BGP VPS plan and configure BGP sessions (eBGP/iBGP) using OuiHeberg's FRRouting configuration guide.

Step 5

Create matching ROAs with your RIR for the announced prefixes.

BYOIP pricing	No separate fee documented; included with BGP VPS plans starting from $7.00/month
Prefix size limitation	Prefixes smaller than /24 (IPv4) or /48 (IPv6) are filtered by most operators and will not propagate globally
DDoS protection	Anti-DDoS protection covers announced prefixes (3 Tbps mentioned on the BGP VPS page)

Announcements without valid ROAs face increasing rejection from operators enforcing route origin validation.
Prefixes more specific than /24 (IPv4) or /48 (IPv6) will not propagate globally on the Internet, per Internet-wide routing norms cited by the provider.

Published 9 September 2026

More BYOIP supporters