Network · data from 2026-11-12
AS21135 MTT-AS JSC Multiregional Transittelecom
Registry name: MTT-AS JSC Multiregional Transittelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21135, 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.
| 95.169.96.0/19 | No ROA | Other origin only | 1 0%low visibility |
| 80.75.128.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.214.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS21135 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: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 95.169.96.0/19 | No ROA covers it. Add a ROA for AS21135, maxLength 19. |
| Route object: none | 95.169.96.0/19 | Route objects for it name AS49476. Add a route object with origin AS21135 in the RIR database for the space. |
| ROA: none | 80.75.128.0/20 | No ROA covers it. Add a ROA for AS21135, maxLength 20. |
| ROA: none | 185.214.60.0/22 | No ROA covers it. Add a ROA for AS21135, maxLength 22. |
Route objects not announced
Route objects with origin AS21135 whose prefix no peer sees AS21135 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.75.128.0/23 | RIPE | No ROA |
| 80.75.130.0/24 | RIPE | No ROA |
| 80.75.131.0/24 | RIPE | No ROA |
| 80.75.139.0/24 | RIPE | No ROA |
| 2a02:5840::/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.