Network · data from 2026-11-12
AS49301 Transtelecom-DV Joint Stock Company TransTeleCom
Registry name: Transtelecom-DV Joint Stock Company TransTeleCom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49301, 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.
| 62.249.128.0/24 | No ROA | Nonecovered by 62.249.128.0/21 | 673 100% |
| 62.249.129.0/24 | No ROA | Nonecovered by 62.249.128.0/21 | 673 100% |
| 5.8.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.8.196.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 46.38.0.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.38.4.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.38.28.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 62.249.152.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.93.132.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 5.8.198.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS49301 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 40 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 62.249.128.0/24 | No ROA covers it. Add a ROA for AS49301, maxLength 24. |
| Route object: none | 62.249.128.0/24 | No route object for it. A route object for 62.249.128.0/21 with origin AS49301 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49301 in the RIR database for the space. |
| ROA: none | 62.249.129.0/24 | No ROA covers it. Add a ROA for AS49301, maxLength 24. |
| Route object: none | 62.249.129.0/24 | No route object for it. A route object for 62.249.128.0/21 with origin AS49301 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49301 in the RIR database for the space. |
| ROA: none | 5.8.192.0/22 | No ROA covers it. Add a ROA for AS49301, maxLength 22. |
| ROA: none | 5.8.196.0/23 | No ROA covers it. Add a ROA for AS49301, maxLength 23. |
| ROA: none | 46.38.0.0/22 | No ROA covers it. Add a ROA for AS49301, maxLength 22. |
| ROA: none | 46.38.4.0/22 | No ROA covers it. Add a ROA for AS49301, maxLength 22. |
| ROA: none | 46.38.28.0/22 | No ROA covers it. Add a ROA for AS49301, maxLength 22. |
| ROA: none | 62.249.152.0/24 | No ROA covers it. Add a ROA for AS49301, maxLength 24. |
| ROA: none | 188.93.132.0/24 | No ROA covers it. Add a ROA for AS49301, maxLength 24. |
| ROA: none | 5.8.198.0/24 | No ROA covers it. Add a ROA for AS49301, maxLength 24. |
Route objects not announced
Route objects with origin AS49301 whose prefix no peer sees AS49301 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.8.199.0/24 | RIPE | No ROA |
| 5.8.200.0/21 | RIPE | No ROA |
| 5.8.208.0/20 | RIPE | No ROA |
| 46.38.8.0/22 | RIPE | No ROA |
| 46.38.12.0/22 | RIPE | No ROA |
| 46.38.16.0/21 | RIPE | No ROA |
| 46.38.24.0/22 | RIPE | No ROA |
| 62.249.128.0/21 | RIPE | No ROA |
| 62.249.136.0/22 | RIPE | No ROA |
| 62.249.140.0/22 | RIPE | No ROA |
| 62.249.144.0/23 | RIPE | No ROA |
| 62.249.146.0/24 | RIPE | No ROA |
| 62.249.147.0/24 | RIPE | No ROA |
| 62.249.148.0/23 | RIPE | No ROA |
| 62.249.150.0/23 | RIPE | No ROA |
| 62.249.153.0/24 | RIPE | No ROA |
| 62.249.154.0/24 | RIPE | No ROA |
| 62.249.155.0/24 | RIPE | No ROA |
| 62.249.156.0/23 | RADB, RIPE | No ROA |
| 62.249.158.0/23 | RIPE | No ROA |
| 145.255.136.0/22 | RIPE | Invalid: origin |
| 145.255.140.0/23 | RIPE | Invalid: origin |
| 145.255.142.0/23 | RIPE | Invalid: origin |
| 188.93.128.0/22 | RIPE | No ROA |
| 188.93.133.0/24 | RIPE | No ROA |
| 188.93.134.0/24 | RIPE | No ROA |
| 188.93.135.0/24 | RIPE | No ROA |
| 2a03:3a80:100::/40 | 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.