APNIC

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

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.127.172.3/32 APNIC PEERINGDB ASSIGNED ● high
103.26.70.9/32 APNIC PEERINGDB ASSIGNED ● high
103.136.103.23/32 APNIC PEERINGDB ASSIGNED ● high
218.100.76.36/32 APNIC PEERINGDB ASSIGNED ● high
2001:7fa:11:2:0:1200:0:1/128 APNIC PEERINGDB ASSIGNED ● high
2001:de8:6::4608:1/128 APNIC PEERINGDB ASSIGNED ● high
2001:dea:0:20::9/128 APNIC PEERINGDB ASSIGNED ● high
2001:df0:680:4::17/128 APNIC PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “APNIC” — 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.
Combined view of all 11 name-family clusters →
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: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS4608