I2K2

Handle
Cluster stats
Netblocks9 · 8,184 IPv4 addresses
All fragments 12 blocks across 3 clusters
Cluster ID210308651
RegistryAPNIC
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
43.224.136.0/22 I2K2 APNIC ASSIGNED PORTABLE ● low
45.249.132.0/22 I2K2 APNIC ALLOCATED PORTABLE ● low
103.25.128.0/22 I2K2 APNIC ASSIGNED PORTABLE ● low
103.66.0.0/22 I2K2 APNIC ALLOCATED PORTABLE ● low
103.194.8.0/22 I2K2 APNIC ALLOCATED PORTABLE ● low
103.218.124.0/22 I2K2 APNIC ASSIGNED PORTABLE ● low
103.234.184.0/22 I2K2 APNIC ASSIGNED PORTABLE ● low
115.166.136.0/22 I2K2 APNIC ALLOCATED PORTABLE ● low
2407:e9c0::/32 I2K2 APNIC ALLOCATED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
11.1% of checked blocks have valid RPKI ROA coverage (1 of 9)
RPKI-inferred operator TECHNO FAQ DIGITAL MEDIA
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

MAINT-IN-IRINN RA381-AP RA381-AP