Clouvider Limited — IP ranges & network footprint

Footprint over time

3 weekly snapshots · JSON

6 0 netblocks since 2026-08-09

2026-08-09 peak 6 2026-08-23

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
91.199.118.174/32	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low
91.199.118.192/32	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low
91.199.118.200/32	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low
91.239.157.56/29	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low
91.239.157.72/29	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low
91.239.157.232/29	CLOUVIDER-HB-CLIENT-14992	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “CLOUVIDER HB CLIENT” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Combined view of all 443 name-family clusters →

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Client 15145 via Clouvider Limited sub-allocation
Client 5221 via Clouvider Limited sub-allocation
CLOUVIDER-HB-CLIENT-15166 sub-allocation
Client 15173 via Clouvider Limited sub-allocation
CLOUVIDER-HB-CLIENT-10883 sub-allocation
Client 10898 via Clouvider Limited sub-allocation
Client 9226 via Clouvider Limited sub-allocation
CLOUVIDER-HB-CLIENT-12251 sub-allocation

NIC Handles

CLOUVIDER-MNT DUMY-RIPE DUMY-RIPE

Netblocks	6
All fragments	4,076 blocks across 443 clusters
Cluster ID	226975154
Registry	RIPE
Customers	find customers using this network →

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue