Network · data from 2026-11-12
AS9843 NACFFUTURES-AS-KR - NHINFORMATIONSYSTEM
Registry name: NACFFUTURES-AS-KR - NHINFORMATIONSYSTEM, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9843, 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.72.230.0/26 | No ROA | None | 14 2%low visibility |
| 58.72.230.64/26 | No ROA | None | 14 2%low visibility |
| 58.72.230.128/26 | No ROA | None | 14 2%low visibility |
| 58.72.230.192/26 | No ROA | None | 14 2%low visibility |
| 121.162.108.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 123.140.237.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.55.76.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 218.147.88.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS9843 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 23 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 58.72.230.0/26 | No ROA covers it. Add a ROA for AS9843, maxLength 26. |
| Route object: none | 58.72.230.0/26 | No route object for it. Add a route object with origin AS9843 in the RIR database for the space. |
| ROA: none | 58.72.230.64/26 | No ROA covers it. Add a ROA for AS9843, maxLength 26. |
| Route object: none | 58.72.230.64/26 | No route object for it. Add a route object with origin AS9843 in the RIR database for the space. |
| ROA: none | 58.72.230.128/26 | No ROA covers it. Add a ROA for AS9843, maxLength 26. |
| Route object: none | 58.72.230.128/26 | No route object for it. Add a route object with origin AS9843 in the RIR database for the space. |
| ROA: none | 58.72.230.192/26 | No ROA covers it. Add a ROA for AS9843, maxLength 26. |
| Route object: none | 58.72.230.192/26 | No route object for it. Add a route object with origin AS9843 in the RIR database for the space. |
| ROA: none | 121.162.108.0/24 | No ROA covers it. Add a ROA for AS9843, maxLength 24. |
| Route object: RIR | 121.162.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 123.140.237.0/24 | No ROA covers it. Add a ROA for AS9843, maxLength 24. |
| Route object: RIR | 123.140.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.55.76.0/24 | No ROA covers it. Add a ROA for AS9843, maxLength 24. |
| Route object: RIR | 211.55.76.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 218.147.88.0/24 | No ROA covers it. Add a ROA for AS9843, maxLength 24. |
| Route object: RIR | 218.147.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9843 whose prefix no peer sees AS9843 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.42.186.0/24 | NTTCOM | No ROA |
| 210.98.171.0/26 | RADB | No ROA |
| 210.109.255.0/24 | RADB | No ROA |
| 210.113.104.0/24 | RADB | No ROA |
| 210.124.12.0/24 | RADB | No ROA |
| 210.205.1.0/24 | NTTCOM | No ROA |
| 211.240.8.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.