bgpreport

Network · data from 2026-11-12

AS17869 REGISTRY-AS-KR-KR - Supreme Court of Korea

Registry name: REGISTRY-AS-KR-KR - Supreme Court of Korea, 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS17869, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17869, 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.
203.240.80.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.240.81.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.61.13.128/25 No ROA Other IRR onlyRADB 3 0%low visibility 3
220.65.213.160/27 No ROA Other IRR onlyRADB 3 0%low visibility 3

AS-SET

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

  • ROA: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none203.240.80.0/24No ROA covers it. Add a ROA for AS17869, maxLength 24.673 of 673
Route object: RIR203.240.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.240.81.0/24No ROA covers it. Add a ROA for AS17869, maxLength 24.673 of 673
Route object: RIR203.240.81.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.61.13.128/25No ROA covers it. Add a ROA for AS17869, maxLength 25.3 of 673
Route object: RIR211.61.13.128/25Route object only in RADB. Add it in the RIR database for the space.3 of 673
ROA: none220.65.213.160/27No ROA covers it. Add a ROA for AS17869, maxLength 27.3 of 673
Route object: RIR220.65.213.160/27Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

Every route object with origin AS17869 is announced.

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.