Network · data from 2026-11-12
AS49665 MKS-KISLOVODSK-AS MTS PJSC
Registry name: MKS-KISLOVODSK-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49665, 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.
| 91.224.208.0/23 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS49665 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 8 are in fix.csv.
- ROA: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.224.208.0/23 | No ROA covers it. Add a ROA for AS49665, maxLength 23. |
Route objects not announced
Route objects with origin AS49665 whose prefix no peer sees AS49665 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.189.215.0/24 | RIPE | Valid |
| 85.140.95.0/24 | RIPE | Valid |
| 178.155.52.0/24 | RIPE | Valid |
| 188.191.240.0/21 | RIPE | No ROA |
| 193.169.118.0/23 | RIPE | Invalid: origin |
| 193.169.118.0/24 | RIPE | Invalid: origin |
| 193.169.119.0/24 | RIPE | Invalid: origin |
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.