Network · data from 2026-11-12
AS38709 NICEVAN03-AS-KR-KR - NICE Information Telecommunication, Inc
Registry name: NICEVAN03-AS-KR-KR - NICE Information Telecommunication, Inc, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38709, 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.
| 211.48.96.0/26 | No ROA | Other IRR onlyRADB | 14 2%low visibility |
| 211.48.96.96/27 | No ROA | Other IRR onlyRADB | 14 2%low visibility |
AS-SET
AS38709 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 5 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.48.96.0/26 | No ROA covers it. Add a ROA for AS38709, maxLength 26. |
| Route object: RIR | 211.48.96.0/26 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.48.96.96/27 | No ROA covers it. Add a ROA for AS38709, maxLength 27. |
| Route object: RIR | 211.48.96.96/27 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38709 whose prefix no peer sees AS38709 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 211.48.96.0/25 | 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.