PUK-CABLE

BGP inherited
Cluster stats
Netblocks6
Registered in Poland (2) · Germany (1) · United Kingdom (1)
All fragments 11 blocks across 5 clusters
Cluster ID204681024
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.89.75.192/30 PUK RIPE ASSIGNED PA ● low
89.27.141.184/29 PUK-NET RIPE ASSIGNED PA ● low
89.171.117.168/30 PUK RIPE ASSIGNED PA ● low
194.72.152.32/29 PUK-CABLE RIPE ASSIGNED PA ● low
2a00:2381:1aae::/48 PUK-CABLE RIPE AGGREGATED-BY-LIR ● low
2a00:2381:1aae::/56 PUK-CABLE RIPE ASSIGNED ● low

Possibly related to this organisation

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

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE NETIA-MNT kielnet-mnt