bgpreport

Network · data from 2026-11-12

AS1704 KAIST-SEOUL-AS-KR-KR - Korea Advanced Institute of Science and Technology

Registry name: KAIST-SEOUL-AS-KR-KR - Korea Advanced Institute of Science and Technology, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1704, 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.68.64.0/18 No ROA Other IRR onlyRADB 673 100% 67
137.68.128.0/17 No ROA Other IRR onlyRADB 673 100% 67
210.107.145.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.107.147.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none137.68.64.0/18No ROA covers it. Add a ROA for AS1704, maxLength 18.673 of 673
Route object: RIR137.68.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none137.68.128.0/17No ROA covers it. Add a ROA for AS1704, maxLength 17.673 of 673
Route object: RIR137.68.128.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.107.145.0/24No ROA covers it. Add a ROA for AS1704, maxLength 24.673 of 673
Route object: RIR210.107.145.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.107.147.0/24No ROA covers it. Add a ROA for AS1704, maxLength 24.673 of 673
Route object: RIR210.107.147.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

59.5.77.0/24RADBNo ROA
137.68.0.0/16NTTCOMNo 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.