bgpreport

Network · data from 2026-11-12

AS17575 CAUNET-AS-KR-KR - Chung-Ang University

Registry name: CAUNET-AS-KR-KR - Chung-Ang University, KR · not in PeeringDB

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

Announced routes

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

165.194.0.0/17 No ROA Other origin onlycovered by 165.194.0.0/16 673 100% 67
165.194.128.0/17 No ROA Other IRR onlyNTTCOM 673 100% 67
165.194.208.0/20 No ROA Other IRR onlyRADB 673 100% 67
165.194.224.0/20 No ROA Other IRR onlyRADB 673 100% 67
165.194.240.0/20 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none165.194.0.0/17No ROA covers it. Add a ROA for AS17575, maxLength 17.673 of 673
Route object: none165.194.0.0/17Route objects for it name AS9318, AS18302. A route object for 165.194.0.0/16 with origin AS17575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17575 in the RIR database for the space.673 of 673
ROA: none165.194.128.0/17No ROA covers it. Add a ROA for AS17575, maxLength 17.673 of 673
Route object: RIR165.194.128.0/17Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none165.194.208.0/20No ROA covers it. Add a ROA for AS17575, maxLength 20.673 of 673
Route object: RIR165.194.208.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none165.194.224.0/20No ROA covers it. Add a ROA for AS17575, maxLength 20.673 of 673
Route object: RIR165.194.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none165.194.240.0/20No ROA covers it. Add a ROA for AS17575, maxLength 20.673 of 673
Route object: RIR165.194.240.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

165.194.0.0/16NTTCOM, RADBNo ROA
165.194.2.0/24RADBNo ROA
165.194.8.0/24RADBNo ROA
165.194.17.0/24RADBNo ROA
165.194.18.0/24RADBNo ROA
165.194.19.0/24RADBNo ROA
165.194.21.0/24RADBNo ROA
165.194.23.0/24RADBNo ROA
165.194.25.0/24RADBNo ROA
165.194.27.0/24RADBNo ROA
165.194.28.0/24RADBNo ROA
165.194.29.0/24RADBNo ROA
165.194.31.0/24RADBNo ROA
165.194.35.0/24RADBNo ROA
165.194.39.0/24RADBNo ROA
165.194.41.0/24RADBNo ROA
165.194.42.0/24RADBNo ROA
165.194.45.0/24RADBNo ROA
165.194.46.0/24RADBNo ROA
165.194.49.0/24RADBNo ROA
165.194.50.0/24RADBNo ROA
165.194.64.0/18RADBNo ROA
165.194.89.0/24RADBNo ROA
165.194.104.0/24RADBNo ROA
165.194.127.0/24NTTCOMNo ROA
165.194.192.0/18RADBNo 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.