Network · data from 2026-11-12
AS18333 ATNET-AS-KR-KR - at(Korea Argo-Fisheries Food Trade Corporation)
Registry name: ATNET-AS-KR-KR - at(Korea Argo-Fisheries Food Trade Corporation), KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18333, 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.124.170.0/24 | No ROA | Other origin only | 33 5%low visibility |
| 121.134.234.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.103.25.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS18333 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: none3
- Route object: none1
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 210.124.170.0/24 | No ROA covers it. Add a ROA for AS18333, maxLength 24. |
| Route object: none | 210.124.170.0/24 | Route objects for it name AS9862. Add a route object with origin AS18333 in the RIR database for the space. |
| ROA: none | 121.134.234.0/24 | No ROA covers it. Add a ROA for AS18333, maxLength 24. |
| Route object: RIR | 121.134.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.103.25.0/24 | No ROA covers it. Add a ROA for AS18333, maxLength 24. |
| Route object: RIR | 210.103.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18333 whose prefix no peer sees AS18333 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.108.108.0/24 | RADB | No ROA |
| 125.128.37.0/24 | RADB | No ROA |
| 210.98.141.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.