bgpreport

Network · data from 2026-11-12

AS329014 Vilcom Networks Limited

Registry name: Vilcom Networks Limited - Vilcom Networks Limited, KE · PeeringDB

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

Announced routes

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

102.200.240.0/24 No ROA None 673 100% 67
102.200.241.0/24 No ROA None 673 100% 67
102.200.242.0/24 No ROA None 673 100% 67
102.210.28.0/24 Valid RIR databaseAFRINIC 671 100% 69
102.210.30.0/24 Valid RIR databaseAFRINIC 671 100% 69
102.216.154.0/23 Valid RIR databaseAFRINIC 671 100% 69
2c0f:5740::/33 Valid RIR databaseAFRINIC 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS329014: AS-VNL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS329014 isn't in the set, or no route object for AS329014 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS329014 in itNot covered
AS-VNL AFRINIC 3111 Yes 3

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: none3
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none102.200.240.0/24No ROA covers it. Add a ROA for AS329014, maxLength 24.673 of 673
Route object: none102.200.240.0/24No route object for it. Add a route object with origin AS329014 in the RIR database for the space.673 of 673
ROA: none102.200.241.0/24No ROA covers it. Add a ROA for AS329014, maxLength 24.673 of 673
Route object: none102.200.241.0/24No route object for it. Add a route object with origin AS329014 in the RIR database for the space.673 of 673
ROA: none102.200.242.0/24No ROA covers it. Add a ROA for AS329014, maxLength 24.673 of 673
Route object: none102.200.242.0/24No route object for it. Add a route object with origin AS329014 in the RIR database for the space.673 of 673

Route objects not announced

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

102.210.28.0/22AFRINICValid
2c0f:5740::/32AFRINICValid

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.