CATAMOUNT-NET

BGP inherited
Cluster stats
Netblocks7 · 457 IPv4 addresses
All fragments 9 blocks across 3 clusters
Cluster ID208862687
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
192.130.151.80/28 CATAMOUNT-NET RIPE ASSIGNED PA ● low
193.208.234.0/24 CATAMOUNT-NET RIPE ASSIGNED PA ● low
193.211.46.192/26 CATAMOUNT-NET RIPE ASSIGNED PA ● low
194.197.190.48/28 CATAMOUNT-NET RIPE ASSIGNED PA ● low
194.197.190.64/26 CATAMOUNT-NET RIPE ASSIGNED PA ● low
194.215.37.32/27 CATAMOUNT-NET RIPE ASSIGNED PA ● low
212.213.92.224/28 CATAMOUNT-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

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

DATANET-NOC DUMY-RIPE DUMY-RIPE