Network · data from 2026-11-12
AS58238 MKS-AS MKS Telecom LLC
Registry name: MKS-AS MKS Telecom LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58238, 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.
| 46.8.54.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 46.8.146.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 89.188.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.33.48.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS58238 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: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.8.54.0/23 | No ROA covers it. Add a ROA for AS58238, maxLength 23. |
| ROA: none | 46.8.146.0/23 | No ROA covers it. Add a ROA for AS58238, maxLength 23. |
Route objects not announced
Route objects with origin AS58238 whose prefix no peer sees AS58238 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.33.48.0/24 | RIPE | Invalid: maxLength |
| 194.33.49.0/24 | RIPE | Invalid: maxLength |
| 2a04:9407::/32 | RIPE | 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.