IIX-APJII Route Servers
Cluster stats
Netblocks12
All fragments 17 blocks across 6 clusters
Cluster ID193386384
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.19.76.2/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
103.19.76.3/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
103.110.223.1/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
103.247.126.254/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
218.100.30.3/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
218.100.33.1/32 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
2001:7fa:2:50ba::2:2/128 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
2001:7fa:2:50ba::2:3/128 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
2001:df3:4600:7597::1/128 IIX-APJII Route Servers PEERINGDB ASSIGNED ● high
103.23.201.32/29 IIX_Mdi APNIC ASSIGNED NON-PORTABLE ● low
182.255.16.0/22 IIX-ID APNIC ALLOCATED PORTABLE ● low
202.74.45.0/24 IIX-ID APNIC ASSIGNED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
8.3% of checked blocks have valid RPKI ROA coverage (1 of 12)
No discrepancies found among checked blocks.

NIC Handles

ADK3-AP AS7597 IA55-AP IH123-AP MAINT-ID-VARNION MNT-APJII-ID RW385-AP