Network · data from 2026-11-12
AS17606 SMLNET-AS-KR-KR - SM LINE CORPORATION
Registry name: SMLNET-AS-KR-KR - SM LINE CORPORATION, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17606, 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.
| 203.246.144.0/24 | No ROA | Other origin onlycovered by 203.246.128.0/19 | 673 100% |
AS-SET
AS17606 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 36 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.246.144.0/24 | No ROA covers it. Add a ROA for AS17606, maxLength 24. |
| Route object: none | 203.246.144.0/24 | Route objects for it name AS6619. A route object for 203.246.128.0/19 with origin AS17606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17606 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17606 whose prefix no peer sees AS17606 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 121.254.232.0/24 | RADB | No ROA |
| 121.254.233.0/24 | RADB | No ROA |
| 203.246.128.0/19 | RADB | No ROA |
| 203.246.128.0/24 | RADB | No ROA |
| 203.246.129.0/24 | RADB | No ROA |
| 203.246.130.0/24 | RADB | No ROA |
| 203.246.131.0/24 | RADB | No ROA |
| 203.246.132.0/24 | RADB | No ROA |
| 203.246.133.0/24 | RADB | No ROA |
| 203.246.134.0/24 | RADB | No ROA |
| 203.246.135.0/24 | RADB | No ROA |
| 203.246.136.0/24 | RADB | No ROA |
| 203.246.137.0/24 | RADB | No ROA |
| 203.246.138.0/24 | RADB | No ROA |
| 203.246.139.0/24 | RADB | No ROA |
| 203.246.140.0/24 | RADB | No ROA |
| 203.246.141.0/24 | RADB | No ROA |
| 203.246.142.0/24 | RADB | No ROA |
| 203.246.143.0/24 | RADB | No ROA |
| 203.246.145.0/24 | RADB | No ROA |
| 203.246.146.0/24 | RADB | No ROA |
| 203.246.148.0/24 | RADB | No ROA |
| 203.246.149.0/24 | RADB | No ROA |
| 203.246.150.0/24 | RADB | No ROA |
| 203.246.151.0/24 | RADB | No ROA |
| 203.246.152.0/24 | RADB | No ROA |
| 203.246.153.0/24 | RADB | No ROA |
| 203.246.154.0/24 | RADB | No ROA |
| 203.246.155.0/24 | RADB | No ROA |
| 203.246.156.0/24 | RADB | No ROA |
| 203.246.157.0/24 | RADB | No ROA |
| 203.246.158.0/24 | RADB | No ROA |
| 203.246.159.0/24 | RADB | No ROA |
| 218.38.40.0/24 | NTTCOM | 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.