bgpreport

Network · data from 2026-11-12

AS34786 VNET-AS OOO NPO Intermet

Registry name: VNET-AS OOO NPO Intermet, UA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34786, 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.

194.145.216.14/32 No ROA Nonecovered by 194.145.216.0/24 5 1%low visibility 7
62.122.56.0/24 No ROA RIR databaseRIPE 673 100% 66
62.122.57.0/24 No ROA RIR databaseRIPE 673 100% 66
62.122.58.0/23 No ROA RIR databaseRIPE 673 100% 66
62.122.60.0/24 No ROA RIR databaseRIPE 673 100% 66
62.122.61.0/24 No ROA RIR databaseRIPE 673 100% 66
62.122.62.0/24 No ROA RIR databaseRIPE 673 100% 66
62.122.63.0/24 No ROA RIR databaseRIPE 673 100% 66
194.145.216.0/23 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS34786 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 16 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none194.145.216.14/32No ROA covers it. Add a ROA for AS34786, maxLength 32.5 of 673
Route object: none194.145.216.14/32No route object for it. A route object for 194.145.216.0/24 with origin AS34786 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34786 in the RIR database for the space.5 of 673
ROA: none62.122.56.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none62.122.57.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none62.122.58.0/23No ROA covers it. Add a ROA for AS34786, maxLength 23.673 of 673
ROA: none62.122.60.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none62.122.61.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none62.122.62.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none62.122.63.0/24No ROA covers it. Add a ROA for AS34786, maxLength 24.673 of 673
ROA: none194.145.216.0/23No ROA covers it. Add a ROA for AS34786, maxLength 23.673 of 673

Route objects not announced

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

62.122.56.0/21RIPENo ROA
62.122.56.0/23RIPENo ROA
62.122.60.0/23RIPENo ROA
62.122.62.0/23RIPENo ROA
194.145.216.0/24RIPENo ROA
194.145.217.0/24RIPENo 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.