bgpreport

Network · data from 2026-11-12

AS17863 YONHAPNEWS-AS-KR-KR - Yonhap News Agency

Registry name: YONHAPNEWS-AS-KR-KR - Yonhap News Agency, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17863, 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.
210.92.55.0/25 No ROA None 16 2%low visibility 13
125.128.45.64/26 No ROA None 14 2%low visibility 13
61.40.248.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.234.152.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.92.60.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.113.28.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.113.29.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS17863 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none210.92.55.0/25No ROA covers it. Add a ROA for AS17863, maxLength 25.16 of 673
Route object: none210.92.55.0/25No route object for it. Add a route object with origin AS17863 in the RIR database for the space.16 of 673
ROA: none125.128.45.64/26No ROA covers it. Add a ROA for AS17863, maxLength 26.14 of 673
Route object: none125.128.45.64/26No route object for it. Add a route object with origin AS17863 in the RIR database for the space.14 of 673
ROA: none61.40.248.0/24No ROA covers it. Add a ROA for AS17863, maxLength 24.673 of 673
Route object: RIR61.40.248.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.234.152.0/24No ROA covers it. Add a ROA for AS17863, maxLength 24.673 of 673
Route object: RIR203.234.152.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.92.60.0/24No ROA covers it. Add a ROA for AS17863, maxLength 24.673 of 673
Route object: RIR210.92.60.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.113.28.0/24No ROA covers it. Add a ROA for AS17863, maxLength 24.673 of 673
Route object: RIR210.113.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.113.29.0/24No ROA covers it. Add a ROA for AS17863, maxLength 24.673 of 673
Route object: RIR210.113.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS17863 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.