bgpreport

Network · data from 2026-11-12

AS3661 The Chinese University of Hong Kong AS 3661

Registry name: ERX-CUHKNET - The Chinese University of Hong Kong, HK · PeeringDB

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

Announced routes

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

137.189.196.0/24 No ROA Other origin onlycovered by 137.189.0.0/16 672 100% 68
203.188.64.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
175.159.224.0/22 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.40.216.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
2001:ce0:3::/48 No ROA Other IRR onlyNTTCOM, RADB 636 100% 70
123.255.64.0/21 No ROA RIR databaseAPNIC, RADB 672 100% 68
137.189.0.0/16 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.49.160.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
2405:3000::/32 No ROA RIR databaseAPNIC, NTTCOM, RADB 636 100% 70

AS-SET

AS3661'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 22 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none137.189.196.0/24No ROA covers it. Add a ROA for AS3661, maxLength 24.672 of 673
Route object: none137.189.196.0/24Route objects for it name AS3662, AS4641, AS45474. A route object for 137.189.0.0/16 with origin AS3661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3661 in the RIR database for the space.672 of 673
ROA: none203.188.64.0/20No ROA covers it. Add a ROA for AS3661, maxLength 20.672 of 673
Route object: RIR203.188.64.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none175.159.224.0/22No ROA covers it. Add a ROA for AS3661, maxLength 22.670 of 673
Route object: RIR175.159.224.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.40.216.0/24No ROA covers it. Add a ROA for AS3661, maxLength 24.670 of 673
Route object: RIR202.40.216.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:ce0:3::/48No ROA covers it. Add a ROA for AS3661, maxLength 48.636 of 636
Route object: RIR2001:ce0:3::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none123.255.64.0/21No ROA covers it. Add a ROA for AS3661, maxLength 21.672 of 673
ROA: none137.189.0.0/16No ROA covers it. Add a ROA for AS3661, maxLength 16.672 of 673
ROA: none103.49.160.0/22No ROA covers it. Add a ROA for AS3661, maxLength 22.670 of 673
ROA: none2405:3000::/32No ROA covers it. Add a ROA for AS3661, maxLength 32.636 of 636

Route objects not announced

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

43.230.116.0/22APNIC, RADBValid
43.252.200.0/22APNIC, RADBNo ROA
103.29.12.0/22APNIC, RADBNo ROA
123.255.64.0/19RADBNo ROA
123.255.64.0/20APNIC, NTTCOM, RADBNo ROA
123.255.72.0/21APNICNo ROA
123.255.80.0/21APNIC, NTTCOM, RADBNo ROA
137.189.0.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.