bgpreport

Network · data from 2026-11-12

AS3608 KRC-AS-KR-KR - Korea Rural Community Corporation

Registry name: KRC-AS-KR-KR - Korea Rural Community Corporation, KR · not in PeeringDB

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

Announced routes

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

211.181.37.0/24 No ROA None 46 7%low visibility 29
203.231.18.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.241.9.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.241.10.0/23 No ROA Other IRR onlyRADB 673 100% 67
211.241.12.0/22 No ROA Other IRR onlyRADB 673 100% 67
211.241.64.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.241.72.0/22 No ROA Other IRR onlyRADB 673 100% 67
211.241.80.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.241.94.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.124.134.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS3608 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 27 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none211.181.37.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.46 of 673
Route object: none211.181.37.0/24No route object for it. Add a route object with origin AS3608 in the RIR database for the space.46 of 673
ROA: none203.231.18.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.673 of 673
Route object: RIR203.231.18.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.9.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.673 of 673
Route object: RIR211.241.9.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.10.0/23No ROA covers it. Add a ROA for AS3608, maxLength 23.673 of 673
Route object: RIR211.241.10.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.12.0/22No ROA covers it. Add a ROA for AS3608, maxLength 22.673 of 673
Route object: RIR211.241.12.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.64.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.673 of 673
Route object: RIR211.241.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.72.0/22No ROA covers it. Add a ROA for AS3608, maxLength 22.673 of 673
Route object: RIR211.241.72.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.80.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.673 of 673
Route object: RIR211.241.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.241.94.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.673 of 673
Route object: RIR211.241.94.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.124.134.0/24No ROA covers it. Add a ROA for AS3608, maxLength 24.670 of 673
Route object: RIR210.124.134.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

61.37.68.128/26RADBNo ROA
125.60.22.0/24RADBNo ROA
202.30.73.0/24RADBNo ROA
202.30.93.0/24RADBNo ROA
203.231.17.0/24RADBNo ROA
203.254.53.0/24RADBNo ROA
211.112.224.32/29RADBNo 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.