OV Hcloud
OVHcloud
Registry
Cluster stats
| Netblocks | 209 |
| Registered in | United States (30) · Netherlands (10) · France (9) · Poland (6) · Australia (4) · United Kingdom (4) |
| All fragments | 241 blocks across 8 clusters |
| Cluster ID | 208801212 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
208
+4 netblocks since 2026-07-05
2026-07-05
peak 208
2026-07-19
IP Ranges (209)
showing 50 of 209 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.57.82.210/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 27.111.228.106/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 37.49.232.27/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 37.49.236.100/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 37.49.236.144/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 43.243.22.89/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 45.127.172.217/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 62.69.146.111/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 80.81.192.209/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 80.81.193.209/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.231/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.245/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 91.206.52.57/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 91.210.16.129/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 101.203.74.26/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 101.203.74.80/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 101.203.88.210/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.16.102.120/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.26.68.60/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.27.170.194/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.41.12.26/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.77.108.86/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.156.182.197/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.203.158.119/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 103.231.152.119/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.252/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 178.18.230.65/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 178.18.234.10/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.104/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.0.20.119/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.0.27.48/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.0.42.90/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.14.76/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.14.77/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.14.78/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.62.233/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.90.107/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.114.108/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.127.25/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.161.25/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.192.65/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.152/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.226.163/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.1.240.176/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.6.36.189/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 185.79.175.208/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 193.34.197.142/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 193.149.1.81/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 193.169.199.138/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
| 193.188.137.162/32 | OVHcloud | PEERINGDB | ASSIGNED | ● high |
Customer-delegated space
how is this classified?
Operator infrastructure (named)
208 (99.5%)
Unclassified
1 (0.5%)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
71.3%
of checked blocks have valid RPKI ROA coverage
(149 of 209)
Possible discrepancies (1)
These blocks are registered to OVHcloud but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 217.147.2.0/24 /24 | authorized for AS210116 — Quintiez Alfa General Trading Co. |
NIC Handles
AS16276
DUMY-RIPE
DUMY-RIPE
mnt-ps-quintiez-1