bgpreport

Network · data from 2026-11-12

AS20597 ELTEL-AS PJSC "Vimpelcom"

Registry name: ELTEL-AS PJSC "Vimpelcom", RU · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS20597, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20597, 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.
81.9.0.0/20 No ROA RIR databaseRIPE 673 100% 67
81.9.32.0/20 No ROA RIR databaseRIPE 673 100% 67
81.9.96.0/20 No ROA RIR databaseRIPE 673 100% 67
81.222.128.0/20 No ROA RIR databaseRIPE 673 100% 67
81.222.160.0/20 No ROA RIR databaseRIPE 673 100% 67
81.222.192.0/18 No ROA RIR databaseRIPE 673 100% 67
85.249.8.0/21 No ROA RIR databaseRIPE 673 100% 67
85.249.224.0/19 No ROA RIR databaseRIPE 673 100% 67
89.112.0.0/17 No ROA RIR databaseRIPE 673 100% 67
217.170.64.0/19 No ROA RIR databaseRIPE 673 100% 67
2001:1b00::/32 No ROA RIR databaseRIPE 636 100% 67

AS-SET

AS20597 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 11 are in fix.csv.

  • ROA: none11
ChangePrefix or setDetailFull-table peers
ROA: none81.9.0.0/20No ROA covers it. Add a ROA for AS20597, maxLength 20.673 of 673
ROA: none81.9.32.0/20No ROA covers it. Add a ROA for AS20597, maxLength 20.673 of 673
ROA: none81.9.96.0/20No ROA covers it. Add a ROA for AS20597, maxLength 20.673 of 673
ROA: none81.222.128.0/20No ROA covers it. Add a ROA for AS20597, maxLength 20.673 of 673
ROA: none81.222.160.0/20No ROA covers it. Add a ROA for AS20597, maxLength 20.673 of 673
ROA: none81.222.192.0/18No ROA covers it. Add a ROA for AS20597, maxLength 18.673 of 673
ROA: none85.249.8.0/21No ROA covers it. Add a ROA for AS20597, maxLength 21.673 of 673
ROA: none85.249.224.0/19No ROA covers it. Add a ROA for AS20597, maxLength 19.673 of 673
ROA: none89.112.0.0/17No ROA covers it. Add a ROA for AS20597, maxLength 17.673 of 673
ROA: none217.170.64.0/19No ROA covers it. Add a ROA for AS20597, maxLength 19.673 of 673
ROA: none2001:1b00::/32No ROA covers it. Add a ROA for AS20597, maxLength 32.636 of 636

Route objects not announced

Every route object with origin AS20597 is announced.

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.