Network · data from 2026-11-12
AS9695 KOEXP-AS-KR-KR - KISTI
Registry name: KOEXP-AS-KR-KR - KISTI, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9695, 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.110.200.0/23 | No ROA | None | 673 100% |
| 210.110.199.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 210.110.202.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 210.110.203.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS9695 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 11 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 210.110.200.0/23 | No ROA covers it. Add a ROA for AS9695, maxLength 23. |
| Route object: none | 210.110.200.0/23 | No route object for it. Add a route object with origin AS9695 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9695 whose prefix no peer sees AS9695 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.106.128.0/18 | RADB | No ROA |
| 61.251.64.0/20 | RADB | No ROA |
| 210.110.200.0/24 | APNIC | Valid |
| 210.110.201.0/24 | APNIC | Valid |
| 211.41.0.0/18 | RADB | No ROA |
| 211.41.0.0/19 | RADB | No ROA |
| 211.41.32.0/19 | RADB | No ROA |
| 211.62.103.0/24 | RADB | No ROA |
| 211.238.55.0/24 | 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.