OVHcloud is a global cloud provider that specialises in delivering industry-leading performance and cost-effective solutions to better manage, secure, and scale data. OVHcloud provides a smarter alternative for web hosting, emails, bare metal servers, hosted private cloud, hybrid and public cloud solutions. The group manages 30 data centres across 12 sites in 4 continents, manufacturing its own servers, building its own data centres and deploying its own fibre-optic global network to achieve maximum efficiency. Through the OVHcloud spirit of challenging the status quo, the company brings freedom, security and innovation to solve data challenges – today and tomorrow. With a 20-year heritage and a solid European foundation, OVHcloud is committed to developing responsible technologies, as the group strives to be the driving force behind the next cloud evolution.
OVHcloud.com operates using the autonomous system AS16276.
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.
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 firstname.lastname@example.org with detailed information.
We may not reply immediately, so please be patient!
If you want a faster response, please configure your side first.
News about AS16276 Backbone Network can be found on Twitter, @as16276
Peering with AS16276 on Internet Exchanges
For low traffic levels, under 10Gbps peak, we recommend using 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 no longer do PNI under 4x10G or nx100G rate.
BGP sessions should be established in IPv4 and IPv6 if available
OVH provides IPv4 /31 and IPv6 /127 subnets 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
To ensure quality of operations, we reserve the following rights under our Peering Policy:
- To accept or decline a peering request at any time for any reason.
- To suspend, without notice, peering connectivity in the event of a severe quality of service issue such as high latency, packet loss, or jitter pattern is detected and to take appropriate traffic engineering steps to maintain service quality.
- To alter our peering policy and peering requirements at any time.
- To terminate any peering connection at any time without notice.
We have a Looking Glass available, lg.ovh.net
To track the latency from different locations, smokeping.ovh.net
We have speedtest servers aroundw our different datacenters, ovh.net
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|