bgpreport

Network · data from 2026-11-12

AS43297 VDS-Telecom

Registry name: VDS-TELECOM VDS-Telecom LLC., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43297, 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.
193.3.185.0/24 Invalid: origin Other origin only 5 1%low visibility 5
178.57.69.0/24 No ROA RIR databaseRIPE 671 100% 68
5.133.111.0/24 No ROA RIR databaseRIPE 669 99% 66
178.57.64.0/24 No ROA RIR databaseRIPE 669 99% 66
178.57.70.0/24 No ROA RIR databaseRIPE 669 99% 66
194.32.231.0/24 No ROA RIR databaseRIPE 669 99% 66
46.17.252.0/24 No ROA RIR databaseRIPE 668 99% 66
95.85.86.0/24 Valid RIR databaseRIPE 671 100% 68
185.13.35.0/24 Valid RIR databaseRIPE 671 100% 68
79.133.98.0/24 Valid RIR databaseRIPE 670 100% 68
95.85.87.0/24 Valid RIR databaseRIPE 670 100% 66
185.13.32.0/24 Valid RIR databaseRIPE 670 100% 68
188.68.4.0/24 Valid RIR databaseRIPE 670 100% 68
45.145.1.0/24 Valid RIR databaseRIPE 669 99% 66

AS-SET

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

  • ROA: origin1
  • ROA: none6
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin193.3.185.0/24ROAs covering it name AS210553, not AS43297. If AS43297 should announce it, add a ROA for AS43297.5 of 673
Route object: none193.3.185.0/24Route objects for it name AS210553. Add a route object with origin AS43297 in the RIR database for the space.5 of 673
ROA: none178.57.69.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.671 of 673
ROA: none5.133.111.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.669 of 673
ROA: none178.57.64.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.669 of 673
ROA: none178.57.70.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.669 of 673
ROA: none194.32.231.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.669 of 673
ROA: none46.17.252.0/24No ROA covers it. Add a ROA for AS43297, maxLength 24.668 of 673

Route objects not announced

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

93.179.120.0/24RIPEInvalid: origin

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.