AZIMUT

BGP inherited
Cluster stats
Netblocks6 · 570 IPv4 addresses
Registered in Israel (2) · Italy (2) · Russia (2)
All fragments 80 blocks across 26 clusters
Cluster ID208864344
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.118.144.32/27 AZIMUT-SPA RIPE ASSIGNED PA ● low
82.208.67.112/29 Azimut-NET RIPE ASSIGNED PA ● low
185.95.232.0/23 AZIMUT-NET RIPE ASSIGNED PA ● low
192.116.225.224/28 AZIMUT RIPE ASSIGNED PA ● low
212.23.86.236/30 AZIMUT-NET RIPE ASSIGNED PA ● low
213.8.57.8/30 AZIMUT RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “AZIMUT” — 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 26 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: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS3253-MNT AS5486-MNT AZIMUT-MNT DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT TIG-MNT