K-SUP2-SUPERNOVASRL

BGP inherited
Cluster stats
Netblocks6
All fragments 9 blocks across 2 clusters
Cluster ID209861354
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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.150.143.180/30 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low
109.168.101.176/28 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low
109.168.101.192/29 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low
109.168.102.48/28 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low
109.168.117.224/29 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low
109.168.117.232/29 K-SUP2-SUPERNOVASRL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “K SUP2” — 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.
  • Adam via ADAMANT, Ltd. sub-allocation

Network trust

what's this?
RPKI hygiene: F how networks compare →
16.7% of checked blocks have valid RPKI ROA coverage (1 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS5602-MNT DUMY-RIPE DUMY-RIPE