bgpreport

Network · data from 2026-11-12

AS3363 Hong Kong University of Science and Technology

Registry name: HKUST-AS-HK - Hong Kong University of Science and Technology, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3363, 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.
143.89.0.0/16 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
175.159.96.0/19 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
202.125.227.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.188.104.0/21 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
175.159.240.0/22 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.14.80.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.40.138.0/24 No ROA Other IRR onlyRADB 670 100% 68
202.40.139.0/24 No ROA Other IRR onlyRADB 670 100% 68
202.125.224.0/24 No ROA Other IRR onlyRADB 670 100% 68
202.125.225.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.125.226.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.125.228.0/22 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
2001:ce0:7::/48 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70

AS-SET

AS3363's PeeringDB record names no 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 29 are in fix.csv.

  • ROA: none13
  • Route object: RIR13
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none143.89.0.0/16No ROA covers it. Add a ROA for AS3363, maxLength 16.672 of 673
Route object: RIR143.89.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none175.159.96.0/19No ROA covers it. Add a ROA for AS3363, maxLength 19.672 of 673
Route object: RIR175.159.96.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.125.227.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.672 of 673
Route object: RIR202.125.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.188.104.0/21No ROA covers it. Add a ROA for AS3363, maxLength 21.672 of 673
Route object: RIR203.188.104.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none175.159.240.0/22No ROA covers it. Add a ROA for AS3363, maxLength 22.670 of 673
Route object: RIR175.159.240.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.14.80.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.14.80.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.40.138.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.40.138.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.40.139.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.40.139.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.125.224.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.125.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.125.225.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.125.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.125.226.0/24No ROA covers it. Add a ROA for AS3363, maxLength 24.670 of 673
Route object: RIR202.125.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.125.228.0/22No ROA covers it. Add a ROA for AS3363, maxLength 22.670 of 673
Route object: RIR202.125.228.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:ce0:7::/48No ROA covers it. Add a ROA for AS3363, maxLength 48.636 of 636
Route object: RIR2001:ce0:7::/48Route 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 AS3363 whose prefix no peer sees AS3363 announce. Many are kept on purpose (backup routes, space announced only in some places).

143.89.0.0/24RADBNo ROA
202.40.138.0/23NTTCOMNo ROA
202.125.224.0/23NTTCOM, RADBNo 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.