Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS9729 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS9729"
JSON Docs

Problem: AS9729 (IS-AP) announces 156 IPv4 and 1 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS9729
HolderIS-AP - iAdvantage Limited
AllocationAPNIC, Hong Kong SAR China (HK), allocated 1999-11-08
Prefixes (IPv4 / IPv6)156 / 1
RPKI valid99% (155 / 157)
Upstreams and peers13
Peering policyOpen

What to fix

  1. Problem

    1 of 157 announced prefixes are RPKI invalid: 210.184.103.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 157 announced prefixes have no ROA (RPKI not found): 203.194.128.0/17.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS9729 and a max length equal to the prefix length:

    203.194.128.0/17 AS9729 max-length /17

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 157 announced prefixes have no IRR route object: 210.184.103.0/24.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS9729 in your RIR’s IRR database (or RADB).

    route: 210.184.103.0/24
    origin: AS9729

    Open in ASN & BGP prefix lookup

  4. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 157 announced prefixes are RPKI invalid: 210.184.103.0/24.
  • Pass: AS9729 announces 156 IPv4 and 1 IPv6 prefixes.
  • Problem: 1 of 157 announced prefixes are RPKI invalid: 210.184.103.0/24.
  • Warning: 1 of 157 announced prefixes have no ROA (RPKI not found): 203.194.128.0/17.
  • Info: 155 of 157 announced prefixes are RPKI valid.
  • Warning: 1 of 157 announced prefixes have no IRR route object: 210.184.103.0/24.
  • Info: 13 upstreams and peers, 4 downstream networks seen.
HolderIS-AP - iAdvantage Limited
IPv4 prefixes156
IPv6 prefixes1
RPKI155 valid · 1 invalid · 1 not found
Without IRR route object1
Downstream networks4
Routes to fix
PrefixRPKI
210.184.103.0/24 RPKI invalid
203.194.128.0/17 No ROA

Announced prefixes 157

202.85.128.0/20 202.85.128.0/24 202.85.129.0/24 202.85.131.0/24 202.85.132.0/24 202.85.137.0/24 202.85.140.0/24 202.85.144.0/20 202.85.157.0/24 202.85.164.0/23 202.85.165.0/24 202.85.166.0/23 202.85.167.0/24 202.85.168.0/22 202.85.169.0/24 202.85.170.0/24 202.85.171.0/24 202.85.180.0/22 202.85.181.0/24 202.85.184.0/22 202.85.188.0/24 202.85.190.0/24 202.85.191.0/24 203.194.128.0/17 203.194.128.0/21 203.194.133.0/24 203.194.135.0/24 203.194.136.0/21 203.194.136.0/24 203.194.141.0/24 203.194.144.0/21 203.194.144.0/24 203.194.145.0/24 203.194.146.0/24 203.194.148.0/24 203.194.149.0/24 203.194.152.0/21 203.194.153.0/24 203.194.159.0/24 203.194.160.0/22 203.194.160.0/24 203.194.161.0/24 203.194.164.0/22 203.194.168.0/22 203.194.168.0/24 203.194.169.0/24 203.194.170.0/24 203.194.171.0/24 203.194.176.0/22 203.194.176.0/24 203.194.177.0/24 203.194.179.0/24 203.194.183.0/24 203.194.186.0/24 203.194.187.0/24 203.194.188.0/22 203.194.188.0/24 203.194.192.0/21 203.194.196.0/24 203.194.199.0/24 203.194.200.0/22 203.194.200.0/23 203.194.204.0/22 203.194.206.0/24 203.194.211.0/24 203.194.216.0/22 203.194.216.0/24 203.194.217.0/24 203.194.218.0/24 203.194.219.0/24 203.194.220.0/22 203.194.220.0/24 203.194.221.0/24 203.194.223.0/24 203.194.227.0/24 203.194.228.0/22 203.194.228.0/24 203.194.232.0/22 203.194.232.0/24 203.194.233.0/24 203.194.236.0/22 203.194.239.0/24 203.194.240.0/22 203.194.251.0/24 203.194.255.0/24 210.184.96.0/22 210.184.97.0/24 210.184.100.0/22 210.184.103.0/24 210.184.108.0/22 210.184.110.0/24 210.184.112.0/21 210.184.113.0/24 210.184.114.0/24 210.184.120.0/24 210.184.121.0/24 210.184.122.0/24 210.184.124.0/24 210.184.127.0/24 210.184.128.0/17

Showing the first 100.

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameIS-AP
HandleAS9729
RangeAS9729
CountryHK
Statusactive
Registered2008-09-04T06:40:32Z
Last changed2020-07-09T04:04:35Z
Abuse contactnetwork@iadvantage.net
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on1999-11-08
StatusAllocated
Delegated rangeAS9729

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
administrative Postmaster iAdvantage postmaster@iadvantage.net
registrant iAdvantage Limited td-eng@iadvantage.net
abuse IRT-IADVANTAGE-HK network@iadvantage.net
technical DNS IADVANTAGE dns@iadvantage.net

Source: https://rdap.apnic.net/autnum/9729. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS9729 is in PeeringDB as iAdvantage.
  • Info: Peering policy: Open.
  • Info: Present at 2 internet exchanges with 5 ports (52G in total).
  • Warning: No IRR as-set is listed.
NetworkiAdvantage (MEGA-i)
AS numberAS9729
TypeNSP, Asia Pacific
Websitehttp://www.iadvantage.net
Prefixes (IPv4 / IPv6)15000 / 3000
TrafficBalanced
Peering policyOpen
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2026-10-23
Contacts
Policyandrewlee@sunevision.com network@iadvantage.net

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup