SFN-ACCESS

BGP inherited
Cluster stats
Netblocks6 · 1,530 IPv4 addresses
All fragments 10 blocks across 5 clusters
Cluster ID210615630
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
195.226.20.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low
195.226.21.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low
195.226.23.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low
195.226.24.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low
195.226.25.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low
195.226.26.0/24 SFN-ACCESS RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SFN ACCESS” — 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

CYBERLINK-MNT DUMY-RIPE DUMY-RIPE