AS16276 is the network run by OVH.com.
We own datacenters in Europe (RBX, GRA, SBG, FRA, LON, WAW), North America (BHS, WAS, PDX) and APAC (SYD, SIN) and run a worldwide network.
We are running around Peering Requests: https://peering.ovh.net or send us an email to email@example.com Peering Operational Issues: Contact firstname.lastname@example.org (24x7) OVHcloud manages the following ASNs: AS16276 and AS35540
Our traffic ratio is heavy outbound and our policy is open.
We use a ticketing system to contact us for peering purposes.
Please send an email to email@example.com with detailed information.
We may not reply immediately, so please be patient !
If you want faster reply, please configure your side first.
If you want to see news about AS16276 Backbone Network, follow us on Twitter @as16276
Peering with AS16276 on Internet Exchanges
For small traffic level, under 10G peak, we recommend to use direct sessions on Internet Exchanges.
- BGP sessions should be established in IPv4 and IPv6 if available
- Technical information (IPv4/IPv6) about peer should be visible publicly on peeringdb.com
Peering with AS16276 on Private Peering
Our BGP peering policy is open, but for PNI, we start with 10GB-LR or 100GB-LR4 interfaces.
Traffic with the peer ASN should be at least around 10Gbps peak to start discussing about PNI.
We don't do anymore PNI under 4x10G or nx100G rate.
BGP sessions should be established in IPv4 and IPv6 if available
OVH provides IPv4 /31 and IPv6 /127 networks for the PNI
We announce around 119 IPv4 prefixes and 6 IPv6 prefixes.
As we are growing fast, we suggest to set the following maximum-prefixes :
- IPv4 : 1000 prefixes
- IPv6 : 200 prefixes
We have looking glass available here
AS16276 BGP Communities
Communities available (if send-community eBGP is enabled) are the following :
|16276:40000||Routes to North American Networks|
|16276:40001||Routes to European Networks|
|16276:40019||Routes to Asian Networks|
|16276:40020||Routes to Australian Networks|