bgpreport

Network · data from 2026-11-12

AS29694 VILLAGENET VILLAGENET Ltd.

Registry name: VILLAGENET VILLAGENET Ltd., BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29694, 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.
85.187.243.1/32 Invalid: maxLength Nonecovered by 85.187.243.0/24 3 0%low visibility 6
85.187.243.2/32 Invalid: maxLength Nonecovered by 85.187.243.0/24 3 0%low visibility 6
85.187.243.5/32 Invalid: maxLength Nonecovered by 85.187.243.0/24 3 0%low visibility 6
85.187.243.6/32 Invalid: maxLength Nonecovered by 85.187.243.0/24 3 0%low visibility 6
85.187.14.0/24 Valid RIR databaseRIPE 673 100% 66
85.187.243.0/24 Valid RIR databaseRIPE 673 100% 66
85.187.249.0/24 Valid RIR databaseRIPE 673 100% 66
46.254.132.0/24 Valid RIR databaseRIPE 672 100% 66
46.254.133.0/24 Valid RIR databaseRIPE 672 100% 66
46.254.134.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS29694 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 8 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength85.187.243.1/32ROA 85.187.243.0/24 AS29694 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 85.187.243.1/32.3 of 673
Route object: none85.187.243.1/32No route object for it. A route object for 85.187.243.0/24 with origin AS29694 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS29694 in the RIR database for the space.3 of 673
ROA: maxLength85.187.243.2/32ROA 85.187.243.0/24 AS29694 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 85.187.243.2/32.3 of 673
Route object: none85.187.243.2/32No route object for it. A route object for 85.187.243.0/24 with origin AS29694 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS29694 in the RIR database for the space.3 of 673
ROA: maxLength85.187.243.5/32ROA 85.187.243.0/24 AS29694 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 85.187.243.5/32.3 of 673
Route object: none85.187.243.5/32No route object for it. A route object for 85.187.243.0/24 with origin AS29694 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS29694 in the RIR database for the space.3 of 673
ROA: maxLength85.187.243.6/32ROA 85.187.243.0/24 AS29694 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 85.187.243.6/32.3 of 673
Route object: none85.187.243.6/32No route object for it. A route object for 85.187.243.0/24 with origin AS29694 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS29694 in the RIR database for the space.3 of 673

Route objects not announced

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