Network · data from 2026-11-12
AS8371 Vimpelcom-NN PJSC "Vimpelcom"
Registry name: Vimpelcom-NN PJSC "Vimpelcom", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8371, 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.
| 95.31.120.0/21 | No ROA | Other origin only | 673 100% |
| 89.189.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 92.242.64.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 95.31.49.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 149.62.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 195.98.32.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 212.92.128.0/18 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS8371 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 27 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 95.31.120.0/21 | No ROA covers it. Add a ROA for AS8371, maxLength 21. |
| Route object: none | 95.31.120.0/21 | Route objects for it name AS8402. Add a route object with origin AS8371 in the RIR database for the space. |
| ROA: none | 89.189.0.0/19 | No ROA covers it. Add a ROA for AS8371, maxLength 19. |
| ROA: none | 92.242.64.0/19 | No ROA covers it. Add a ROA for AS8371, maxLength 19. |
| ROA: none | 95.31.49.0/24 | No ROA covers it. Add a ROA for AS8371, maxLength 24. |
| ROA: none | 149.62.0.0/19 | No ROA covers it. Add a ROA for AS8371, maxLength 19. |
| ROA: none | 195.98.32.0/19 | No ROA covers it. Add a ROA for AS8371, maxLength 19. |
| ROA: none | 212.92.128.0/18 | No ROA covers it. Add a ROA for AS8371, maxLength 18. |
Route objects not announced
Route objects with origin AS8371 whose prefix no peer sees AS8371 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.146.32.0/20 | RIPE | No ROA |
| 37.147.192.0/20 | RIPE | No ROA |
| 62.205.165.0/24 | RIPE | No ROA |
| 83.102.214.0/24 | RIPE | No ROA |
| 83.102.221.0/24 | RIPE | No ROA |
| 83.102.222.0/24 | RIPE | No ROA |
| 83.102.232.0/24 | RIPE | No ROA |
| 83.102.234.0/24 | RIPE | No ROA |
| 83.102.238.0/24 | RIPE | No ROA |
| 83.102.243.0/24 | RIPE | No ROA |
| 83.102.252.0/24 | RIPE | No ROA |
| 88.81.32.0/19 | RIPE | No ROA |
| 95.24.40.0/21 | RIPE | No ROA |
| 95.24.60.0/22 | RIPE | No ROA |
| 109.71.204.0/22 | RIPE | No ROA |
| 149.62.16.0/21 | RIPE | No ROA |
| 200.33.114.0/24 | RADB | No ROA |
| 213.234.233.0/24 | RIPE | No ROA |
| 2a03:8700::/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.