Network · data from 2026-11-12
AS45986 KISANET-KR - Korea Internet Security Agency
Registry name: KISANET-KR - Korea Internet Security Agency, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45986, 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.
| 121.147.42.0/25 | No ROA | None | 16 2%low visibility |
| 121.147.42.128/25 | No ROA | None | 16 2%low visibility |
AS-SET
AS45986 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 9 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 121.147.42.0/25 | No ROA covers it. Add a ROA for AS45986, maxLength 25. |
| Route object: none | 121.147.42.0/25 | No route object for it. Add a route object with origin AS45986 in the RIR database for the space. |
| ROA: none | 121.147.42.128/25 | No ROA covers it. Add a ROA for AS45986, maxLength 25. |
| Route object: none | 121.147.42.128/25 | No route object for it. Add a route object with origin AS45986 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45986 whose prefix no peer sees AS45986 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.33.164.0/24 | NTTCOM | No ROA |
| 211.190.190.0/29 | RADB | No ROA |
| 211.190.192.0/19 | RADB | No ROA |
| 211.233.96.0/19 | RADB | No ROA |
| 211.235.0.0/19 | RADB | No 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.