SC10444

BGP inherited
Cluster stats
Netblocks6
All fragments 10 blocks across 3 clusters
Cluster ID204399557
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

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.231.149.72/29 SC10444 RIPE ASSIGNED PA ● low
81.171.142.160/29 SC10444 RIPE ASSIGNED PA ● low
81.171.224.168/30 SC10444 RIPE ASSIGNED PA ● low
89.206.181.240/28 SC10444 RIPE ASSIGNED PA ● low
89.206.231.32/28 SC10444 RIPE ASSIGNED PA ● low
89.206.235.128/29 SC10444 RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

AS8426-MNT DUMY-RIPE DUMY-RIPE