Network · data from 2026-11-12
AS16256 ReCom-AS MTS PJSC
Registry name: ReCom-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16256, 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.
| 84.17.228.0/24 | No ROA | Nonecovered by 84.17.224.0/20 | 671 100% |
| 84.17.229.0/24 | No ROA | Nonecovered by 84.17.224.0/20 | 671 100% |
| 84.17.248.0/24 | No ROA | Nonecovered by 84.17.240.0/20 | 671 100% |
| 84.17.249.0/24 | No ROA | Nonecovered by 84.17.240.0/20 | 671 100% |
| 84.17.224.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 91.135.208.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 95.139.75.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 81.23.172.0/24 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS16256 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 14 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 84.17.228.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
| Route object: none | 84.17.228.0/24 | No route object for it. A route object for 84.17.224.0/20 with origin AS16256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16256 in the RIR database for the space. |
| ROA: none | 84.17.229.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
| Route object: none | 84.17.229.0/24 | No route object for it. A route object for 84.17.224.0/20 with origin AS16256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16256 in the RIR database for the space. |
| ROA: none | 84.17.248.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
| Route object: none | 84.17.248.0/24 | No route object for it. A route object for 84.17.240.0/20 with origin AS16256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16256 in the RIR database for the space. |
| ROA: none | 84.17.249.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
| Route object: none | 84.17.249.0/24 | No route object for it. A route object for 84.17.240.0/20 with origin AS16256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16256 in the RIR database for the space. |
| ROA: none | 84.17.224.0/19 | No ROA covers it. Add a ROA for AS16256, maxLength 19. |
| ROA: none | 91.135.208.0/20 | No ROA covers it. Add a ROA for AS16256, maxLength 20. |
| ROA: none | 95.139.75.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
| ROA: none | 81.23.172.0/24 | No ROA covers it. Add a ROA for AS16256, maxLength 24. |
Route objects not announced
Route objects with origin AS16256 whose prefix no peer sees AS16256 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.17.224.0/20 | RIPE | No ROA |
| 84.17.240.0/20 | 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.