Network · data from 2026-11-12
AS49905 ELOPAK-CIS-AS Joint Stock Company "Primekartonpak"
Registry name: ELOPAK-CIS-AS Joint Stock Company "Primekartonpak", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49905, 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.
| 185.187.196.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 91.213.166.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS49905 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 8 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.187.196.0/24 | ROAs covering it name AS61324, not AS49905. If AS49905 should announce it, add a ROA for AS49905. |
| Route object: none | 185.187.196.0/24 | Route objects for it name AS61324. Add a route object with origin AS49905 in the RIR database for the space. |
| ROA: none | 91.213.166.0/24 | No ROA covers it. Add a ROA for AS49905, maxLength 24. |
Route objects not announced
Route objects with origin AS49905 whose prefix no peer sees AS49905 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.213.166.0/25 | RIPE | No ROA |
| 91.213.166.0/28 | RIPE | No ROA |
| 91.213.166.32/29 | RIPE | No ROA |
| 91.213.166.40/29 | RIPE | No ROA |
| 91.213.166.128/25 | 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.