BIM
Cluster stats
Netblocks11
All fragments 46 blocks across 28 clusters
Cluster ID192097944
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.244.195.92/30 BIM-NET RIPE ASSIGNED PA ● low
78.38.219.0/24 BIM RIPE ASSIGNED PA ● low
82.150.89.16/29 BIM-NET RIPE ASSIGNED PA ● low
83.70.137.0/27 BIM RIPE ASSIGNED PA ● low
88.255.230.16/29 BIM RIPE ASSIGNED PA ● low
95.0.84.40/29 Bim RIPE ASSIGNED PA ● low
212.98.241.168/29 BIM-NET RIPE ASSIGNED PA ● low
212.174.153.0/29 BIM RIPE ASSIGNED PA ● low
212.174.194.64/26 BIM RIPE ASSIGNED PA ● low
212.175.46.0/24 BIM RIPE ASSIGNED PA ● low
213.211.239.216/29 BIM-NET RIPE ASSIGNED PA ● low

Network trust

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

These blocks are registered to BIM 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.

212.175.46.0/24 /24 authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi
78.38.219.0/24 /24 authorized for AS58224 — Iran Telecommunication Company PJS

NIC Handles

AS12880-MNT AS9121-MNT DUMY-RIPE DUMY-RIPE MDlink-MNT MNT-BORUSAN TE-MNT as9121-mnt de-mdcc-1-mnt