IOSYS Media Data
Cluster stats
Netblocks16
Cluster ID193388786
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.254.82.128/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
49.213.56.114/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
119.11.185.71/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
123.108.9.254/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
218.100.36.51/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
218.100.41.233/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
218.100.72.45/32 IOSYS Media Data PEERINGDB ASSIGNED ● high
2001:7fa:2:5::20e/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2001:7fa:f::1a3/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2001:de8:11:3:8060:0:1410:56/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2001:df0:b1:100::72:45/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2001:df5:7880:0:2:2700:0:1/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2401:91e0:31::1410:56:1/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:14:1056:1/128 IOSYS Media Data PEERINGDB ASSIGNED ● high
103.155.116.0/23 IOSYS-ID APNIC ALLOCATED PORTABLE ● low
2406:6d40::/32 IOSYS-ID APNIC ALLOCATED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
37.5% of checked blocks have valid RPKI ROA coverage (6 of 16)
Possible discrepancies (1)

These blocks are registered to IOSYS Media Data but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2406:6d40::/32 /32 authorized for AS139433 — PT Sakaeng Solata Infrastruktur

NIC Handles

AS141056 LKJ14-AP LKJ14-AP MNT-APJII-ID