Network · data from 2026-11-12
AS35728 MTS-PENZA-AS MTS PJSC
Registry name: MTS-PENZA-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35728, 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.108.192.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 82.209.64.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 92.246.160.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 95.83.64.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 85.234.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 85.140.44.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS35728 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: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.108.192.0/18 | No ROA covers it. Add a ROA for AS35728, maxLength 18. |
| ROA: none | 82.209.64.0/18 | No ROA covers it. Add a ROA for AS35728, maxLength 18. |
| ROA: none | 92.246.160.0/19 | No ROA covers it. Add a ROA for AS35728, maxLength 19. |
| ROA: none | 95.83.64.0/18 | No ROA covers it. Add a ROA for AS35728, maxLength 18. |
Route objects not announced
Route objects with origin AS35728 whose prefix no peer sees AS35728 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.148.253.0/24 | 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.