Network · data from 2026-11-12
AS55588 NFCF-AS-KR-KR - Information Technology Center
Registry name: NFCF-AS-KR-KR - Information Technology Center, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55588, 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.
| 58.151.137.128/25 | No ROA | None | 16 2%low visibility |
| 61.40.15.128/25 | No ROA | Nonecovered by 61.40.15.0/24 | 16 2%low visibility |
| 211.35.151.128/26 | No ROA | None | 14 2%low visibility |
AS-SET
AS55588 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 7 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 58.151.137.128/25 | No ROA covers it. Add a ROA for AS55588, maxLength 25. |
| Route object: none | 58.151.137.128/25 | No route object for it. Add a route object with origin AS55588 in the RIR database for the space. |
| ROA: none | 61.40.15.128/25 | No ROA covers it. Add a ROA for AS55588, maxLength 25. |
| Route object: none | 61.40.15.128/25 | No route object for it. A route object for 61.40.15.0/24 with origin AS55588 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55588 in the RIR database for the space. |
| ROA: none | 211.35.151.128/26 | No ROA covers it. Add a ROA for AS55588, maxLength 26. |
| Route object: none | 211.35.151.128/26 | No route object for it. Add a route object with origin AS55588 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55588 whose prefix no peer sees AS55588 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.40.15.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.