ZZ-MIKE-20220111

Handle
Cluster stats
Netblocks9
All fragments 18 blocks across 8 clusters
Cluster ID211662833
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a12:4940::/30 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low
2a12:4944::/30 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low
2a12:4946::/32 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low
2a12:4946::/34 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low
2a12:4946::/36 ZZ-MIKE-20220111 RIPE AGGREGATED-BY-LIR ● low
2a12:4946:1000::/36 ZZ-MIKE-20220111 RIPE AGGREGATED-BY-LIR ● low
2a12:4946:2000::/35 ZZ-MIKE-20220111 RIPE AGGREGATED-BY-LIR ● low
2a12:4946:4000::/34 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low
2a12:4946:8000::/33 ZZ-MIKE-20220111 RIPE ALLOCATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ZZ MIKE” — 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.

NIC Handles

DUMY-RIPE DUMY-RIPE MIKENETWORKS-MNT