SATO-NET

BGP inherited
Cluster stats
Netblocks7 · 406 IPv4 addresses
Registered in Finland (3) · Germany (1) · France (1) · Poland (1)
All fragments 23 blocks across 13 clusters
Cluster ID209607450
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
109.2.203.128/30 SATO RIPE ASSIGNED PA ● low
193.210.13.176/28 SATO-NET RIPE ASSIGNED PA ● low
193.210.34.128/26 SATO-NET RIPE ASSIGNED PA ● low
194.181.45.0/24 SATO RIPE ASSIGNED PA ● low
195.82.34.56/29 Sato_GmbH RIPE ASSIGNED PA ● low
212.213.108.64/26 SATO-NET RIPE ASSIGNED PA ● low
2001:c18:dc00:201d::/64 SATO APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AN941-AP AS8375-MNT DATANET-NOC DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT MAINT-MY-NTT-MSC NASK2-MNT NT202-AP NT204-AP