miac

BGP inherited
Cluster stats
Netblocks7
Registered in Israel (3) · Russia (3) · KZ (1)
All fragments 9 blocks across 3 clusters
Cluster ID209340053
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.90.164.75/32 miac RIPE ASSIGNED PA ● low
62.90.245.48/30 miac RIPE ASSIGNED PA ● low
62.90.245.52/30 miac RIPE ASSIGNED PA ● low
82.208.97.160/28 MIAC-net RIPE ASSIGNED PA ● low
212.32.221.0/28 miac RIPE ASSIGNED PA ● low
212.154.253.184/30 MIAC RIPE ASSIGNED PA ● low
217.195.87.32/28 MIAC RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT NV-MNT-RIPE PSTAR-MNT ROSTELECOM-MNT SAMTEL-MNT