Network · data from 2026-11-12
AS41771 MTS-BB-OMSK MTS PJSC
Registry name: MTS-BB-OMSK MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41771, 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.
| 77.87.80.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 91.90.32.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 193.34.184.0/23 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS41771 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: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.87.80.0/21 | No ROA covers it. Add a ROA for AS41771, maxLength 21. |
| ROA: none | 91.90.32.0/21 | No ROA covers it. Add a ROA for AS41771, maxLength 21. |
| ROA: none | 193.34.184.0/23 | No ROA covers it. Add a ROA for AS41771, maxLength 23. |
Route objects not announced
Route objects with origin AS41771 whose prefix no peer sees AS41771 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.87.80.0/22 | RIPE | No ROA |
| 77.87.84.0/22 | RIPE | No ROA |
| 91.90.36.0/22 | RIPE | No ROA |
| 178.216.216.0/22 | RIPE | No ROA |
| 178.216.220.0/22 | RIPE | No ROA |
| 188.75.210.0/23 | 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.