Network · data from 2026-11-12
AS12846 PJSC Rostelecom
Registry name: PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12846, 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.
| 212.94.100.0/24 | Invalid: origin | None | 75 11% |
| 194.150.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.94.101.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS12846 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 6 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.94.100.0/24 | ROAs covering it name AS12389, not AS12846. If AS12846 should announce it, add a ROA for AS12846. |
| Route object: none | 212.94.100.0/24 | No route object for it. Add a route object with origin AS12846 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12846 whose prefix no peer sees AS12846 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 90.188.0.0/20 | RIPE | Valid |
| 90.188.0.0/23 | RIPE | Valid |
| 90.188.16.0/20 | RIPE | Valid |
| 212.94.126.0/24 | RIPE | Valid |
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.