PRO ISP AS PRO ISP AS

BGP inherited
Cluster stats
Netblocks7
All fragments 27 blocks across 2 clusters
Cluster ID210480871
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
46.105.138.96/28 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
94.23.98.112/29 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
137.74.52.48/29 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
149.202.19.176/28 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
178.33.4.232/29 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
178.33.133.136/29 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high
188.165.10.0/29 PRO ISP AS PRO ISP AS RIPE ASSIGNED PA ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PRO ISP AS” — 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)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-PIAP3-RIPE OVH-MNT