bgpreport

Network · data from 2026-11-12

AS35005 VilTel LTD

Registry name: VILTEL-AS VilTel Ltd, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35005, 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.161.140.0/23 No ROA RIR databaseRIPE 671 100% 68
95.161.142.0/23 No ROA RIR databaseRIPE 671 100% 68
95.161.140.0/24 No ROA RIR databaseRIPE 64 10%low visibility 25
95.161.141.0/24 No ROA RIR databaseRIPE 64 10%low visibility 25
95.161.142.0/24 No ROA RIR databaseRIPE 64 10%low visibility 25
95.161.143.0/24 No ROA RIR databaseRIPE 64 10%low visibility 25

AS-SET

AS35005's PeeringDB record names no 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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none95.161.140.0/23No ROA covers it. Add a ROA for AS35005, maxLength 23.671 of 673
ROA: none95.161.142.0/23No ROA covers it. Add a ROA for AS35005, maxLength 23.671 of 673
ROA: none95.161.140.0/24No ROA covers it. Add a ROA for AS35005, maxLength 24.64 of 673
ROA: none95.161.141.0/24No ROA covers it. Add a ROA for AS35005, maxLength 24.64 of 673
ROA: none95.161.142.0/24No ROA covers it. Add a ROA for AS35005, maxLength 24.64 of 673
ROA: none95.161.143.0/24No ROA covers it. Add a ROA for AS35005, maxLength 24.64 of 673

Route objects not announced

Every route object with origin AS35005 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.