VANCO-HK

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks7
Record ID241617500
RegistryAPNIC
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
59.188.104.48/28 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
59.188.194.72/30 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
203.98.171.208/28 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
210.245.154.208/28 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
210.245.183.0/28 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
210.245.211.160/28 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low
210.245.245.48 – 210.245.245.143 VANCO-HK APNIC ASSIGNED NON-PORTABLE ● low

Footprint over time

7 weekly snapshots · JSON
7 0 netblocks since 2026-07-26
2026-07-26 peak 7 2026-09-13

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AH1343-AP MAINT-HK-HKBNESL MH1716-AP NC315-AP NC315-AP