bgpreport

Network · data from 2026-11-12

AS23596 EDNSKR-KR-KR - Korea Internet Security Agency

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23596, 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.
1.18.127.0/24 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 673 100% 67
1.18.128.0/24 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 673 100% 67
1.18.130.0/24 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 673 100% 67
202.30.124.0/24 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 672 100% 67
1.18.129.0/24 No ROA RIR databaseAPNIC, RIPE-NONAUTH 669 99% 67
2001:dcc:5::/48 No ROA RIR databaseAPNIC, RADB, RIPE-NONAUTH 635 100% 68
2001:dcc:500::/48 No ROA RIR databaseAPNIC, RIPE-NONAUTH 635 100% 68
2001:dcc:502::/48 No ROA RIR databaseAPNIC, RIPE-NONAUTH 635 100% 67
2001:dcc:501::/48 No ROA RIR databaseAPNIC 606 95% 68

AS-SET

AS23596 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 13 are in fix.csv.

  • ROA: none9
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none1.18.127.0/24No ROA covers it. Add a ROA for AS23596, maxLength 24.673 of 673
ROA: none1.18.128.0/24No ROA covers it. Add a ROA for AS23596, maxLength 24.673 of 673
ROA: none1.18.130.0/24No ROA covers it. Add a ROA for AS23596, maxLength 24.673 of 673
ROA: none202.30.124.0/24No ROA covers it. Add a ROA for AS23596, maxLength 24.672 of 673
ROA: none1.18.129.0/24No ROA covers it. Add a ROA for AS23596, maxLength 24.669 of 673
ROA: none2001:dcc:5::/48No ROA covers it. Add a ROA for AS23596, maxLength 48.635 of 636
ROA: none2001:dcc:500::/48No ROA covers it. Add a ROA for AS23596, maxLength 48.635 of 636
ROA: none2001:dcc:502::/48No ROA covers it. Add a ROA for AS23596, maxLength 48.635 of 636
ROA: none2001:dcc:501::/48No ROA covers it. Add a ROA for AS23596, maxLength 48.606 of 636

Route objects not announced

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

1.18.124.0/24RADBNo ROA
1.18.132.0/24RADBNo ROA
202.30.120.0/21RADBNo ROA
2001:dcc::/32RADBNo 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.