bgpreport

Network · data from 2026-11-12

AS23600 GDNSKR-KR-KR - Korea Internet Security Agency

Registry name: GDNSKR-KR-KR - Korea Internet Security Agency, KR · not in PeeringDB

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

Announced routes

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

39.125.192.0/24 No ROA None 46 7%low visibility 29
39.125.228.0/24 No ROA None 46 7%low visibility 29
39.125.244.0/24 No ROA None 46 7%low visibility 29
39.127.249.0/24 No ROA Other IRR onlyRADB 672 100% 67
58.235.102.0/24 No ROA Other IRR onlyRADB 672 100% 67
219.251.142.0/24 No ROA Other IRR onlyRADB 672 100% 67
219.251.156.0/24 No ROA Other IRR onlyRADB 672 100% 67
221.139.191.0/24 No ROA Other IRR onlyRADB 672 100% 67
1.18.132.0/24 No ROA RIR databaseAPNIC 673 100% 66
1.18.133.0/24 No ROA RIR databaseAPNIC, RIPE-NONAUTH 673 100% 66
1.18.134.0/24 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 673 100% 66
202.31.188.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.30.45.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 66
2001:dcc:1000::/48 No ROA RIR databaseAPNIC 636 100% 70
2001:dcc:700::/48 No ROA RIR databaseAPNIC, RIPE-NONAUTH 635 100% 70
2001:dcc:702::/48 No ROA RIR databaseAPNIC, RIPE-NONAUTH 635 100% 67
2001:dcc:703::/48 No ROA RIR databaseAPNIC, RADB 635 100% 67
2001:dc5:a::/48 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 631 99% 70
1.18.135.0/24 No ROA RIR databaseAPNIC, RIPE-NONAUTH 46 7%low visibility 29
202.31.190.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, RIPE-NONAUTH 673 100% 66
203.83.158.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66

AS-SET

AS23600 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 58 are in fix.csv.

  • ROA: none19
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none39.125.192.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.46 of 673
Route object: none39.125.192.0/24No route object for it. Add a route object with origin AS23600 in the RIR database for the space.46 of 673
ROA: none39.125.228.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.46 of 673
Route object: none39.125.228.0/24No route object for it. Add a route object with origin AS23600 in the RIR database for the space.46 of 673
ROA: none39.125.244.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.46 of 673
Route object: none39.125.244.0/24No route object for it. Add a route object with origin AS23600 in the RIR database for the space.46 of 673
ROA: none39.127.249.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.672 of 673
Route object: RIR39.127.249.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none58.235.102.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.672 of 673
Route object: RIR58.235.102.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none219.251.142.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.672 of 673
Route object: RIR219.251.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none219.251.156.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.672 of 673
Route object: RIR219.251.156.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none221.139.191.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.672 of 673
Route object: RIR221.139.191.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none1.18.132.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.673 of 673
ROA: none1.18.133.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.673 of 673
ROA: none1.18.134.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.673 of 673
ROA: none202.31.188.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.673 of 673
ROA: none202.30.45.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.671 of 673
ROA: none2001:dcc:1000::/48No ROA covers it. Add a ROA for AS23600, maxLength 48.636 of 636
ROA: none2001:dcc:700::/48No ROA covers it. Add a ROA for AS23600, maxLength 48.635 of 636
ROA: none2001:dcc:702::/48No ROA covers it. Add a ROA for AS23600, maxLength 48.635 of 636
ROA: none2001:dcc:703::/48No ROA covers it. Add a ROA for AS23600, maxLength 48.635 of 636
ROA: none2001:dc5:a::/48No ROA covers it. Add a ROA for AS23600, maxLength 48.631 of 636
ROA: none1.18.135.0/24No ROA covers it. Add a ROA for AS23600, maxLength 24.46 of 673

Route objects not announced

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

1.18.118.0/24RADBNo ROA
1.18.120.0/24RADBNo ROA
42.83.130.0/24RADBNo ROA
42.83.131.0/24RADBNo ROA
42.83.132.0/24RADBNo ROA
42.83.134.0/24RADBNo ROA
42.83.139.0/24RADBNo ROA
117.16.73.0/24RADBNo ROA
125.208.35.0/24RADBNo ROA
125.208.36.0/24RADBNo ROA
125.208.37.0/24RADBNo ROA
125.208.38.0/24RADBNo ROA
125.208.41.0/24RADBNo ROA
125.208.43.0/24RADBNo ROA
125.208.49.0/24RADBNo ROA
202.31.190.0/23RADBNo ROA
202.31.191.0/24NTTCOMNo ROA
203.119.26.0/24RADBNo ROA
203.119.29.0/24RADBNo ROA
203.119.31.0/24RADBNo ROA
210.101.60.0/24APNICNo ROA
210.101.61.0/24APNICNo ROA
210.101.62.0/24APNICNo ROA
210.101.63.0/24APNIC, RADBNo ROA
2001:dc7::/48RADBNo ROA
2001:dc7:1000::/48RADBNo ROA
2001:dc7:fffe::/48RADBNo ROA
2001:dc7:ffff::/48RADBNo ROA
2001:dcc:6::/48APNICNo ROA
2001:dcc:20::/48RADBNo ROA
2001:dcc:2000::/48RADBNo 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.