SAFE
Cluster stats
Netblocks10
All fragments 148 blocks across 54 clusters
Cluster ID191926311
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.17.235.136/29 SAFE RIPE ASSIGNED PA ● low
176.94.3.64/29 SAFE-NET RIPE ASSIGNED PA ● low
212.179.20.128/26 SAFE RIPE ASSIGNED PA ● low
212.179.33.128/32 SAFE RIPE ASSIGNED PA ● low
212.179.45.0/26 SAFE RIPE ASSIGNED PA ● low
212.179.48.192/26 SAFE RIPE ASSIGNED PA ● low
212.179.118.0/23 SAFE RIPE ASSIGNED PA ● low
212.179.200.0/24 SAFE RIPE ASSIGNED PA ● low
212.179.252.0/24 SAFE RIPE ASSIGNED PA ● low
2a00:2381:2dfd::/48 SAFE-AS RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
90.0% of checked blocks have valid RPKI ROA coverage (9 of 10)
Possible discrepancies (4)

These blocks are registered to SAFE but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:2381:2dfd::/48 /48 authorized for AS2856 — British Telecommunications PLC
212.179.118.0/23 /23 authorized for AS8551 — Bezeq International Ltd.
212.179.200.0/24 /24 authorized for AS8551 — Bezeq International Ltd.
212.179.252.0/24 /24 authorized for AS8551 — Bezeq International Ltd.

NIC Handles

ARCOR-MNT AS8551-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE INTERB-MNT