SAI-BE

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks10
Also registered under this name 101 netblocks across 2 separate records
Record ID241943060
RegistryRIPE
Customerssee who runs inside 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 · report an issue

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

Footprint over time

7 weekly snapshots · JSON
10 0 netblocks since 2026-07-26
2026-07-26 peak 10 2026-09-13

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