Network · data from 2026-11-12
AS49291 RTCOMM-AS JSC RTComm.RU
Registry name: RTCOMM-AS JSC RTComm.RU, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49291, 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.
| 188.112.214.0/24 | No ROA | Nonecovered by 188.112.214.0/23 | 672 100% |
| 188.112.219.0/24 | No ROA | Nonecovered by 188.112.216.0/22 | 672 100% |
| 188.112.192.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.203.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.204.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.205.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.213.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.220.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.221.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.250.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.251.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.112.252.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS49291 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 67 are in fix.csv.
- ROA: none12
- Route object: none2
- Route object: not announced53
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.112.214.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| Route object: none | 188.112.214.0/24 | No route object for it. A route object for 188.112.214.0/23 with origin AS49291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49291 in the RIR database for the space. |
| ROA: none | 188.112.219.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| Route object: none | 188.112.219.0/24 | No route object for it. A route object for 188.112.216.0/22 with origin AS49291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49291 in the RIR database for the space. |
| ROA: none | 188.112.192.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.203.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.204.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.205.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.213.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.220.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.221.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.250.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.251.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
| ROA: none | 188.112.252.0/24 | No ROA covers it. Add a ROA for AS49291, maxLength 24. |
Route objects not announced
Route objects with origin AS49291 whose prefix no peer sees AS49291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.112.193.0/24 | RIPE | No ROA |
| 188.112.194.0/24 | RIPE | No ROA |
| 188.112.195.0/24 | RIPE | No ROA |
| 188.112.196.0/24 | RIPE | No ROA |
| 188.112.197.0/24 | RIPE | No ROA |
| 188.112.198.0/24 | RIPE | No ROA |
| 188.112.199.0/24 | RIPE | No ROA |
| 188.112.200.0/24 | RIPE | No ROA |
| 188.112.201.0/24 | RIPE | No ROA |
| 188.112.202.0/24 | RIPE | No ROA |
| 188.112.206.0/24 | RIPE | No ROA |
| 188.112.207.0/24 | RIPE | No ROA |
| 188.112.208.0/24 | RIPE | No ROA |
| 188.112.209.0/24 | RIPE | No ROA |
| 188.112.210.0/24 | RIPE | No ROA |
| 188.112.211.0/24 | RIPE | No ROA |
| 188.112.212.0/24 | RIPE | No ROA |
| 188.112.214.0/23 | RIPE | No ROA |
| 188.112.216.0/22 | RIPE | No ROA |
| 188.112.222.0/24 | RIPE | No ROA |
| 188.112.223.0/24 | RIPE | No ROA |
| 188.112.224.0/20 | RIPE | No ROA |
| 188.112.224.0/24 | RIPE | No ROA |
| 188.112.225.0/24 | RIPE | No ROA |
| 188.112.226.0/24 | RIPE | No ROA |
| 188.112.227.0/24 | RIPE | No ROA |
| 188.112.228.0/24 | RIPE | No ROA |
| 188.112.229.0/24 | RIPE | No ROA |
| 188.112.230.0/24 | RIPE | No ROA |
| 188.112.231.0/24 | RIPE | No ROA |
| 188.112.232.0/24 | RIPE | No ROA |
| 188.112.233.0/24 | RIPE | No ROA |
| 188.112.234.0/24 | RIPE | No ROA |
| 188.112.235.0/24 | RIPE | No ROA |
| 188.112.236.0/24 | RIPE | No ROA |
| 188.112.237.0/24 | RIPE | No ROA |
| 188.112.238.0/24 | RIPE | No ROA |
| 188.112.239.0/24 | RIPE | No ROA |
| 188.112.240.0/22 | RIPE | No ROA |
| 188.112.240.0/24 | RIPE | No ROA |
| 188.112.241.0/24 | RIPE | No ROA |
| 188.112.242.0/24 | RIPE | No ROA |
| 188.112.243.0/24 | RIPE | No ROA |
| 188.112.244.0/24 | RIPE | No ROA |
| 188.112.245.0/24 | RIPE | No ROA |
| 188.112.246.0/24 | RIPE | No ROA |
| 188.112.247.0/24 | RIPE | No ROA |
| 188.112.248.0/21 | RIPE | No ROA |
| 188.112.248.0/24 | RIPE | No ROA |
| 188.112.249.0/24 | RIPE | No ROA |
| 188.112.253.0/24 | RIPE | No ROA |
| 188.112.254.0/24 | RIPE | No ROA |
| 188.112.255.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.