Network · data from 2026-11-12
AS49154 MTS-DOM-AS MTS PJSC
Registry name: MTS-DOM-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49154, 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.148.255.0/24 | No ROA | Nonecovered by 46.148.254.0/23 | 597 89% |
| 46.148.254.0/24 | No ROA | Nonecovered by 46.148.254.0/23 | 594 88% |
| 5.227.172.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 188.75.231.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 94.229.228.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 185.212.0.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 212.188.64.0/23 | Valid | Nonecovered by 212.188.64.0/22 | 670 100% |
| 212.188.66.0/23 | Valid | Nonecovered by 212.188.64.0/22 | 670 100% |
| 212.188.64.0/22 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS49154 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 16 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.148.255.0/24 | No ROA covers it. Add a ROA for AS49154, maxLength 24. |
| Route object: none | 46.148.255.0/24 | No route object for it. A route object for 46.148.254.0/23 with origin AS49154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49154 in the RIR database for the space. |
| ROA: none | 46.148.254.0/24 | No ROA covers it. Add a ROA for AS49154, maxLength 24. |
| Route object: none | 46.148.254.0/24 | No route object for it. A route object for 46.148.254.0/23 with origin AS49154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49154 in the RIR database for the space. |
| ROA: none | 5.227.172.0/22 | No ROA covers it. Add a ROA for AS49154, maxLength 22. |
| ROA: none | 188.75.231.0/24 | No ROA covers it. Add a ROA for AS49154, maxLength 24. |
| ROA: none | 94.229.228.0/22 | No ROA covers it. Add a ROA for AS49154, maxLength 22. |
| ROA: none | 185.212.0.0/22 | No ROA covers it. Add a ROA for AS49154, maxLength 22. |
| Route object: none | 212.188.64.0/23 | No route object for it. A route object for 212.188.64.0/22 with origin AS49154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49154 in the RIR database for the space. |
| Route object: none | 212.188.66.0/23 | No route object for it. A route object for 212.188.64.0/22 with origin AS49154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49154 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49154 whose prefix no peer sees AS49154 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.148.254.0/23 | RIPE | No ROA |
| 94.229.228.0/24 | RIPE | No ROA |
| 94.229.229.0/24 | RIPE | No ROA |
| 94.229.230.0/24 | RIPE | No ROA |
| 94.229.231.0/24 | RIPE | No ROA |
| 178.72.120.0/22 | 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.