SC14126

BGP inherited
Cluster stats
Netblocks9
All fragments 13 blocks across 5 clusters
Cluster ID209393234
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
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
81.171.176.67/32 SC14126 RIPE ASSIGNED PA ● low
81.171.187.240/29 SC14126 RIPE ASSIGNED PA ● low
81.171.240.111/32 SC14126 RIPE ASSIGNED PA ● low
81.171.244.195/32 SC14126 RIPE ASSIGNED PA ● low
89.206.189.12/30 SC14126 RIPE ASSIGNED PA ● low
89.206.190.96/30 SC14126 RIPE ASSIGNED PA ● low
89.206.236.72/29 SC14126 RIPE ASSIGNED PA ● low
89.206.236.160/30 SC14126 RIPE ASSIGNED PA ● low
89.206.244.64/26 SC14126 RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

AS8426-MNT DUMY-RIPE DUMY-RIPE