Network · data from 2026-11-12
AS13257 POLARCOM-AS PJSC "Vimpelcom"
Registry name: POLARCOM-AS PJSC "Vimpelcom", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13257, 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.
| 77.245.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 77.245.192.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 77.245.200.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 178.23.0.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 213.142.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 213.142.192.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 213.142.200.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 213.142.208.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 213.142.216.0/21 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS13257 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 19 are in fix.csv.
- ROA: none9
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.245.192.0/20 | No ROA covers it. Add a ROA for AS13257, maxLength 20. |
| ROA: none | 77.245.192.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 77.245.200.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 178.23.0.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 213.142.192.0/19 | No ROA covers it. Add a ROA for AS13257, maxLength 19. |
| ROA: none | 213.142.192.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 213.142.200.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 213.142.208.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
| ROA: none | 213.142.216.0/21 | No ROA covers it. Add a ROA for AS13257, maxLength 21. |
Route objects not announced
Route objects with origin AS13257 whose prefix no peer sees AS13257 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.142.192.0/22 | RIPE | No ROA |
| 213.142.196.0/22 | RIPE | No ROA |
| 213.142.200.0/22 | RIPE | No ROA |
| 213.142.200.0/24 | RIPE | No ROA |
| 213.142.204.0/23 | RIPE | No ROA |
| 213.142.206.0/23 | RIPE | No ROA |
| 213.142.210.0/23 | RIPE | No ROA |
| 213.142.212.0/23 | RIPE | No ROA |
| 213.142.216.0/22 | RIPE | No ROA |
| 213.142.220.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.