SAI-SO

BGP inherited
Cluster stats
Netblocks11
All fragments 16 blocks across 2 clusters
Cluster ID209893726
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.110.133.0/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.8/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.16/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.24/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.32/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.40/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.48/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.56/29 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.64/30 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.72/30 SAI-SO RIPE ASSIGNED PA ● low
78.110.133.76 – 78.110.133.255 SAI-SO RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

CH-SECUREPOP-MNT CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE