bgpreport

Network · data from 2026-11-12

AS25082 AS-VINER-TELECOM Viner Telecom LLC

Registry name: AS-VINER-TELECOM Viner Telecom LLC, UA · not in PeeringDB

20IPv4 routes 80.0% RPKI valid · 90.0% with a route object
0IPv6 routes
2RPKI invalid 0 origin · 2 maxLength
2No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS25082, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25082, 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.
91.203.140.0/23 Invalid: maxLength RIR databaseRIPE 23 3%low visibility 14
91.215.69.0/24 Invalid: maxLength RIR databaseRIPE 23 3%low visibility 14
80.70.78.0/24 No ROA RIR databaseRIPE 671 100% 68
80.70.79.0/24 No ROA RIR databaseRIPE 671 100% 68
45.91.216.0/23 Valid Nonecovered by 45.91.216.0/22 145 22% 49
45.91.218.0/23 Valid Nonecovered by 45.91.216.0/22 145 22% 49
195.64.244.0/22 Valid RIR databaseRIPE 673 100% 66
195.64.248.0/22 Valid RIR databaseRIPE 672 100% 66
45.91.216.0/22 Valid RIR databaseRIPE 671 100% 68
91.203.140.0/22 Valid RIR databaseRIPE 671 100% 68
91.203.140.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.141.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.142.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.143.0/24 Valid RIR databaseRIPE 671 100% 68
91.215.68.0/22 Valid RIR databaseRIPE 671 100% 68
91.215.68.0/24 Valid RIR databaseRIPE 671 100% 68
91.215.70.0/23 Valid RIR databaseRIPE 671 100% 68
91.215.70.0/24 Valid RIR databaseRIPE 671 100% 68
91.215.71.0/24 Valid RIR databaseRIPE 671 100% 68
91.215.68.0/23 Valid RIR databaseRIPE 145 22% 49

AS-SET

AS25082 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 9 are in fix.csv.

  • ROA: maxLength2
  • ROA: none2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.203.140.0/23ROA 91.203.140.0/22 AS25082 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 91.203.140.0/23.23 of 673
ROA: maxLength91.215.69.0/24ROA 91.215.68.0/22 AS25082 has maxLength 22; ROA 91.215.68.0/23 AS25082 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 91.215.69.0/24.23 of 673
ROA: none80.70.78.0/24No ROA covers it. Add a ROA for AS25082, maxLength 24.671 of 673
ROA: none80.70.79.0/24No ROA covers it. Add a ROA for AS25082, maxLength 24.671 of 673
Route object: none45.91.216.0/23No route object for it. A route object for 45.91.216.0/22 with origin AS25082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25082 in the RIR database for the space.145 of 673
Route object: none45.91.218.0/23No route object for it. A route object for 45.91.216.0/22 with origin AS25082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25082 in the RIR database for the space.145 of 673

Route objects not announced

Route objects with origin AS25082 whose prefix no peer sees AS25082 announce. Many are kept on purpose (backup routes, space announced only in some places).

80.70.78.0/23RIPENo ROA
91.203.142.0/23RIPEInvalid: maxLength
2001:67c:2e08::/48RIPENo 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.