Network · data from 2026-11-12
AS28884 MR-SIB-MTSAS MTS PJSC
Registry name: MR-SIB-MTSAS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28884, 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.
| 109.174.112.0/24 | No ROA | None | 671 100% |
| 109.174.113.0/24 | No ROA | None | 671 100% |
| 185.52.140.0/24 | No ROA | None | 671 100% |
| 185.52.141.0/24 | No ROA | None | 671 100% |
| 212.74.200.0/24 | No ROA | None | 671 100% |
| 212.74.201.0/24 | No ROA | None | 671 100% |
| 212.109.200.0/21 | No ROA | RIR databaseRIPE | 670 100% |
| 2a00:ea20::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 85.140.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 85.140.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 85.140.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 213.87.116.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 213.87.124.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a00:1fa2:8000::/33 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS28884 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 48 are in fix.csv.
- ROA: none8
- Route object: none6
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.174.112.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 109.174.112.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 109.174.113.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 109.174.113.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 185.52.140.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 185.52.140.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 185.52.141.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 185.52.141.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 212.74.200.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 212.74.200.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 212.74.201.0/24 | No ROA covers it. Add a ROA for AS28884, maxLength 24. |
| Route object: none | 212.74.201.0/24 | No route object for it. Add a route object with origin AS28884 in the RIR database for the space. |
| ROA: none | 212.109.200.0/21 | No ROA covers it. Add a ROA for AS28884, maxLength 21. |
| ROA: none | 2a00:ea20::/29 | No ROA covers it. Add a ROA for AS28884, maxLength 29. |
Route objects not announced
Route objects with origin AS28884 whose prefix no peer sees AS28884 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.105.60.0/23 | RIPE | No ROA |
| 81.195.238.0/24 | RIPE | Invalid: origin |
| 95.104.184.0/21 | RIPE | No ROA |
| 95.104.184.0/23 | RIPE | No ROA |
| 95.104.186.0/23 | RIPE | No ROA |
| 95.104.188.0/23 | RIPE | No ROA |
| 95.104.190.0/23 | RIPE | No ROA |
| 213.87.112.0/23 | RIPE | Valid |
| 213.87.112.0/24 | RIPE | Invalid: maxLength |
| 213.87.113.0/24 | RIPE | Invalid: maxLength |
| 213.87.114.0/23 | RIPE | Valid |
| 213.87.114.0/24 | RIPE | Invalid: maxLength |
| 213.87.115.0/24 | RIPE | Invalid: maxLength |
| 213.87.116.0/24 | RIPE | Invalid: maxLength |
| 213.87.117.0/24 | RIPE | Invalid: maxLength |
| 213.87.118.0/23 | RIPE | Valid |
| 213.87.120.0/23 | RIPE | Valid |
| 213.87.122.0/23 | RIPE | Valid |
| 213.87.126.0/23 | RIPE | Valid |
| 213.87.224.0/23 | RIPE | Valid |
| 217.8.224.0/20 | RIPE | No ROA |
| 217.8.224.0/21 | RIPE | No ROA |
| 217.8.224.0/24 | RIPE | No ROA |
| 217.8.225.0/24 | RIPE | No ROA |
| 217.8.226.0/23 | RIPE | No ROA |
| 217.8.228.0/22 | RIPE | No ROA |
| 217.8.232.0/21 | RIPE | No ROA |
| 217.8.232.0/23 | RIPE | No ROA |
| 217.8.234.0/24 | RIPE | No ROA |
| 217.8.235.0/24 | RIPE | No ROA |
| 217.8.236.0/24 | RIPE | No ROA |
| 217.8.237.0/24 | RIPE | No ROA |
| 217.8.238.0/24 | RIPE | No ROA |
| 217.8.239.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.