bgpreport

Network · data from 2026-11-12

AS329411 Quick Fiber Limited (Kenya)

Registry name: Yala Kenya Limited - Yala Kenya Limited, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329411, 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.209.136.0/22 Valid RIR databaseAFRINIC 673 100% 66
102.209.138.0/24 Valid RIR databaseAFRINIC 108 16% 40
102.209.136.0/24 Valid RIR databaseAFRINIC 106 16% 40
102.209.137.0/24 Valid RIR databaseAFRINIC 106 16% 40
102.209.139.0/24 Valid RIR databaseAFRINIC 106 16% 40
2c0f:3040::/32 Valid RIR databaseAFRINIC 2 0%low visibility 4
2c0f:3040::/36 Valid RIR databaseAFRINIC 2 0%low visibility 4
2c0f:3040::/40 Valid RIR databaseAFRINIC 2 0%low visibility 4
2c0f:3040::/44 Valid RIR databaseAFRINIC 2 0%low visibility 4
2c0f:3040::/48 Valid RIR databaseAFRINIC 2 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS329411: AS-QUICKFIBER. 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 (AS329411 isn't in the set, or no route object for AS329411 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 objectsAS329411 in itNot covered
AS-QUICKFIBER AFRINIC 117 No 10

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

  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS-QUICKFIBERAS329411 isn't in AS-QUICKFIBER (AFRINIC) once expanded. Add AS329411 to it.

Route objects not announced

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

102.209.136.0/23AFRINICValid
102.209.138.0/23AFRINICValid

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.