Network · data from 2026-11-12
AS29069 TLK-AS PJSC Rostelecom
Registry name: TLK-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29069, 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.
| 178.216.160.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 77.87.112.0/21 | Valid | Other origin only | 672 100% |
| 77.87.112.0/24 | Valid | Other origin only | 672 100% |
| 95.215.96.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.13.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.128.56.0/21 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS29069 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 4 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.216.160.0/21 | No ROA covers it. Add a ROA for AS29069, maxLength 21. |
| Route object: none | 77.87.112.0/21 | Route objects for it name AS51281. Add a route object with origin AS29069 in the RIR database for the space. |
| Route object: none | 77.87.112.0/24 | Route objects for it name AS51281. Add a route object with origin AS29069 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29069 whose prefix no peer sees AS29069 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a03:a040::/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.