bgpreport

Network · data from 2026-11-12

AS9735 HKDNR-AS-AP - Hong Kong Domain Name Registration Co. Ltd

Registry name: HKDNR-AS-AP - Hong Kong Domain Name Registration Co. Ltd, HK · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS9735, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9735, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
203.119.87.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 68
203.119.2.0/24 No ROA Other IRR onlyNTTCOM, RADB 668 99% 68
2001:dca:1000::/36 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70
2001:dca:2000::/36 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70
2001:dca:3000::/36 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70
2001:dca:4000::/36 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70

AS-SET

AS9735 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none203.119.87.0/24No ROA covers it. Add a ROA for AS9735, maxLength 24.671 of 673
Route object: RIR203.119.87.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.119.2.0/24No ROA covers it. Add a ROA for AS9735, maxLength 24.668 of 673
Route object: RIR203.119.2.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none2001:dca:1000::/36No ROA covers it. Add a ROA for AS9735, maxLength 36.636 of 636
Route object: RIR2001:dca:1000::/36Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none2001:dca:2000::/36No ROA covers it. Add a ROA for AS9735, maxLength 36.636 of 636
Route object: RIR2001:dca:2000::/36Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none2001:dca:3000::/36No ROA covers it. Add a ROA for AS9735, maxLength 36.636 of 636
Route object: RIR2001:dca:3000::/36Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none2001:dca:4000::/36No ROA covers it. Add a ROA for AS9735, maxLength 36.636 of 636
Route object: RIR2001:dca:4000::/36Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS9735 whose prefix no peer sees AS9735 announce. Many are kept on purpose (backup routes, space announced only in some places).

203.169.182.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.