bgpreport

Network · data from 2026-11-12

AS63981 NOVA Technology Development (HK) Ltd

Registry name: NTDKL-HK - 43/F, AIA Tower, 183 Electric Road, North Point, Hong Kong, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63981, 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.

103.29.141.79/32 Invalid: maxLength Nonecovered by 103.29.141.0/24 0 0%low visibility 2
45.251.64.0/22 No ROA Other IRR onlyRADB 673 100% 67
154.19.46.0/24 No ROA Other IRR onlyRADB 673 100% 67
38.71.24.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.32.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.33.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.34.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.35.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.36.0/24 Valid Other IRR onlyRADB 671 100% 68
38.71.37.0/24 Valid Other IRR onlyRADB 671 100% 68
116.214.132.0/24 Valid Other IRR onlyNTTCOM, RADB 603 90% 67
103.29.140.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
103.29.142.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.29.143.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.117.76.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.167.140.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.167.141.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.197.28.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
103.206.90.0/24 Valid RIR databaseAPNIC 673 100% 66
103.220.8.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
103.220.8.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.166.220.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
45.117.96.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
45.117.97.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
45.117.98.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
45.117.99.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
45.251.66.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.29.140.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.29.141.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.117.79.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.214.192.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
38.71.22.0/24 Valid RIR databaseARIN, RADB 671 100% 68
38.71.26.0/23 Valid RIR databaseARIN, RADB 671 100% 68
45.117.96.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
66.160.164.0/24 Valid RIR databaseARIN, RADB 671 100% 68
72.52.111.0/24 Valid RIR databaseARIN 671 100% 68
103.214.195.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
2001:550:5c09::/48 Valid RIR databaseARIN, RADB 636 100% 67
2405:a480::/32 Valid RIR databaseAPNIC, RADB 636 100% 70
2407:6bc0::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2401:3e0::/32 Valid RIR databaseAPNIC, RADB 466 73% 66
45.251.67.0/24 Valid RIR databaseAPNIC, RADB 135 20% 48
103.206.88.0/22 Valid RIR databaseAPNIC, RADB 135 20% 48
199.166.24.0/21 Valid RIR databaseAPNIC, RADB 117 17% 45

AS-SET

PeeringDB's irr_as_set for AS63981: AS-NOVANET-63981. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS63981 isn't in the set, or no route object for AS63981 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS63981 in itNot covered
AS-NOVANET-63981 APNIC 31133 Yes 1

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 70 are in fix.csv.

  • ROA: maxLength1
  • ROA: none2
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced56
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.29.141.79/32ROA 103.29.140.0/22 AS63981 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.29.141.79/32.0 of 673
Route object: none103.29.141.79/32No route object for it. A route object for 103.29.141.0/24 with origin AS63981 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63981 in the RIR database for the space.0 of 673
ROA: none45.251.64.0/22No ROA covers it. Add a ROA for AS63981, maxLength 22.673 of 673
Route object: RIR45.251.64.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.19.46.0/24No ROA covers it. Add a ROA for AS63981, maxLength 24.673 of 673
Route object: RIR154.19.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.71.24.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.32.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.33.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.34.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.35.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.36.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.71.37.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR116.214.132.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.603 of 673

Route objects not announced

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

38.71.24.0/23ARINValid
38.71.32.0/21ARINValid
45.251.64.0/23APNICValid
45.251.64.0/24APNIC, RADBValid
45.251.65.0/24APNIC, RADBValid
103.29.140.0/23APNICValid
103.29.142.0/23APNICValid
103.117.76.0/23APNIC, NTTCOM, RADBValid
103.117.76.0/24APNIC, NTTCOM, RADBValid
103.117.77.0/24APNIC, NTTCOM, RADBValid
103.117.78.0/23APNIC, NTTCOM, RADBValid
103.117.78.0/24APNIC, NTTCOM, RADBValid
103.197.28.0/23APNICValid
103.197.28.0/24APNICValid
103.197.29.0/24APNICValid
103.197.30.0/23APNICValid
103.197.30.0/24APNICValid
103.197.31.0/24APNICValid
103.206.88.0/23APNICValid
103.206.88.0/24APNICValid
103.206.89.0/24APNICValid
103.206.90.0/23APNICValid
103.206.91.0/24APNICValid
103.214.192.0/23APNICValid
103.214.192.0/24APNICValid
103.214.193.0/24APNICValid
103.214.194.0/23APNICValid
103.214.194.0/24APNICValid
103.220.8.0/23APNICValid
103.220.9.0/24APNIC, RADBValid
103.220.10.0/23APNICValid
103.220.10.0/24APNIC, RADBValid
103.220.11.0/24APNIC, RADBValid
199.166.24.0/22APNICValid
199.166.24.0/23APNICValid
199.166.24.0/24APNICValid
199.166.25.0/24APNICValid
199.166.26.0/23APNICValid
199.166.26.0/24APNICValid
199.166.27.0/24APNICValid
199.166.28.0/22APNICValid
199.166.28.0/23APNICValid
199.166.28.0/24APNICValid
199.166.29.0/24APNICValid
199.166.30.0/23APNICValid
199.166.30.0/24APNICValid
199.166.31.0/24APNICValid
203.166.220.0/23APNICValid
203.166.220.0/24APNIC, NTTCOM, RADBValid
203.166.221.0/24APNIC, NTTCOM, RADBValid
203.166.222.0/23APNICValid
203.166.222.0/24APNIC, NTTCOM, RADBValid
203.166.223.0/24APNIC, NTTCOM, RADBValid
2001:470:2cd::/48ARINValid
2001:470:5e9::/48ARINValid
2001:470:5f3::/48ARINValid

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.