Network · data from 2026-11-12
AS50071 SRDV-AS MTS PJSC
Registry name: SRDV-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50071, 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.93.110.0/23 | No ROA | None | 671 100% |
| 37.72.80.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 77.93.112.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 94.199.74.0/23 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS50071 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: none4
- Route object: none1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.93.110.0/23 | No ROA covers it. Add a ROA for AS50071, maxLength 23. |
| Route object: none | 77.93.110.0/23 | No route object for it. Add a route object with origin AS50071 in the RIR database for the space. |
| ROA: none | 37.72.80.0/20 | No ROA covers it. Add a ROA for AS50071, maxLength 20. |
| ROA: none | 77.93.112.0/21 | No ROA covers it. Add a ROA for AS50071, maxLength 21. |
| ROA: none | 94.199.74.0/23 | No ROA covers it. Add a ROA for AS50071, maxLength 23. |
Route objects not announced
Route objects with origin AS50071 whose prefix no peer sees AS50071 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.72.92.0/23 | RIPE | No ROA |
| 77.93.110.0/24 | RIPE | No ROA |
| 77.93.111.0/24 | RIPE | No ROA |
| 77.93.112.0/23 | RIPE | No ROA |
| 77.93.114.0/23 | RIPE | No ROA |
| 77.93.116.0/23 | RIPE | No ROA |
| 77.93.118.0/23 | RIPE | No ROA |
| 213.176.236.0/22 | RIPE | No ROA |
| 213.176.236.0/23 | RIPE | No ROA |
| 213.176.238.0/23 | RIPE | No ROA |
| 2a00:13f8:ffff::/48 | 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.