PRO001

BGP inherited
Cluster stats
Netblocks7
All fragments 9 blocks across 2 clusters
Cluster ID210758069
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
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

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.101.139.88/29 PRO001 RIPE ASSIGNED PA ● low
31.132.2.48/28 PRO001 RIPE ASSIGNED PA ● low
37.9.59.224/27 PRO001 RIPE ASSIGNED PA ● low
78.110.163.120/29 PRO001 RIPE ASSIGNED PA ● low
78.110.175.168/29 PRO001 RIPE ASSIGNED PA ● low
94.229.73.192/28 PRO001 RIPE ASSIGNED PA ● low
2a01:a500:2094::/48 PRO001 RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PRO001” — 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (1)

These blocks are registered to PRO001 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.

2a01:a500:2094::/48 /48 authorized for AS42831 — UK Dedicated Servers Limited

NIC Handles

DUMY-RIPE DUMY-RIPE UKSERVERS-MNT