systemc

Registry
Cluster stats
Netblocks9
Cluster ID210454794
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.69.19.96/27 systemc RIPE ASSIGNED PA ● low
80.69.27.96/29 systemc RIPE ASSIGNED PA ● low
80.69.27.160/27 systemc RIPE ASSIGNED PA ● low
89.187.107.84/30 systemc RIPE ASSIGNED PA ● low
89.187.107.88/30 systemc RIPE ASSIGNED PA ● low
89.187.115.16/30 systemc RIPE ASSIGNED PA ● low
89.187.118.192/27 systemc RIPE ASSIGNED PA ● low
89.187.120.128/27 systemc RIPE ASSIGNED PA ● low
89.187.120.192/27 systemc RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE HRW-NOC