Network · data from 2026-11-12
AS44677 MTS-NGCLOUD-AS MTS PJSC
Registry name: MTS-NGCLOUD-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44677, 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.
| 2.59.80.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 62.113.70.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 62.113.75.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 111.88.128.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 171.22.72.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 178.236.26.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 178.236.27.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.93.52.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.93.54.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.93.55.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 80.251.159.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a02:5501:8000::/43 | No ROA | RIR databaseRIPE | 636 100% |
| 2a02:5501:8020::/43 | No ROA | RIR databaseRIPE | 635 100% |
| 188.93.52.0/22 | No ROA | RIR databaseRIPE | 9 1%low visibility |
AS-SET
AS44677 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: none14
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2.59.80.0/22 | No ROA covers it. Add a ROA for AS44677, maxLength 22. |
| ROA: none | 62.113.70.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 62.113.75.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 111.88.128.0/22 | No ROA covers it. Add a ROA for AS44677, maxLength 22. |
| ROA: none | 171.22.72.0/22 | No ROA covers it. Add a ROA for AS44677, maxLength 22. |
| ROA: none | 178.236.26.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 178.236.27.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 188.93.52.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 188.93.54.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 188.93.55.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 80.251.159.0/24 | No ROA covers it. Add a ROA for AS44677, maxLength 24. |
| ROA: none | 2a02:5501:8000::/43 | No ROA covers it. Add a ROA for AS44677, maxLength 43. |
| ROA: none | 2a02:5501:8020::/43 | No ROA covers it. Add a ROA for AS44677, maxLength 43. |
| ROA: none | 188.93.52.0/22 | No ROA covers it. Add a ROA for AS44677, maxLength 22. |
Route objects not announced
Route objects with origin AS44677 whose prefix no peer sees AS44677 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.93.53.0/24 | RIPE | No ROA |
| 2a02:5501::/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.