VAAN

BGP inherited
Cluster stats
Netblocks10 · 159,735 IPv4 addresses
Cluster ID210295230
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.181.0.0/18 VAAN APNIC ASSIGNED PORTABLE ● low
112.136.128.0/17 VAAN APNIC ASSIGNED PORTABLE ● low
122.199.128.0/17 VAAN APNIC ASSIGNED PORTABLE ● low
211.45.96.0/19 VAAN APNIC ASSIGNED PORTABLE ● low
211.47.224.0/20 VAAN APNIC ASSIGNED PORTABLE ● low
211.56.224.0/19 VAAN APNIC ASSIGNED PORTABLE ● low
211.232.0.0/17 VAAN APNIC ALLOCATED PORTABLE ● low
211.232.128.0/18 VAAN APNIC ALLOCATED PORTABLE ● low
221.132.64.0/19 VAAN APNIC ASSIGNED PORTABLE ● low
2402:5800::/32 VAAN APNIC ASSIGNED PORTABLE ● low

Possibly related to this organisation

what's this?
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

IM707-AP IM707-AP MNT-KRNIC-AP