SAI-BE

BGP inherited
Cluster stats
Netblocks10
All fragments 101 blocks across 2 clusters
Cluster ID209893743
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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.117.100.128/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.136/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.144/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.152/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.160/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.168/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.176/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.184/29 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.192/30 SAI-BE RIPE ASSIGNED PA ● low
212.117.100.196 – 212.117.100.255 SAI-BE RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

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