bgpreport

Network · data from 2026-11-12

AS328426 Zonke Wifi

Registry name: Zonke Wifi Private Company - Zonke Wifi Private Company, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328426, 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.130.240.0/21 No ROA RIR databaseAFRINIC 673 100% 67
102.130.240.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.241.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.242.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.243.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.244.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.245.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.246.0/24 No ROA RIR databaseAFRINIC 126 19% 40
102.130.247.0/24 No ROA RIR databaseAFRINIC 126 19% 40

AS-SET

PeeringDB's irr_as_set for AS328426: AFRINIC::AS-ZONKEWIFI. 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 (AS328426 isn't in the set, or no route object for AS328426 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 objectsAS328426 in itNot covered
AFRINIC::AS-ZONKEWIFI AFRINIC 5170 Yes 0

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

  • ROA: none9
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none102.130.240.0/21No ROA covers it. Add a ROA for AS328426, maxLength 21.673 of 673
ROA: none102.130.240.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.241.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.242.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.243.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.244.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.245.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.246.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673
ROA: none102.130.247.0/24No ROA covers it. Add a ROA for AS328426, maxLength 24.126 of 673

Route objects not announced

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

2c0f:1780::/32AFRINICNo ROA
2c0f:1780:1000::/36AFRINICNo ROA
2c0f:1780:2000::/36AFRINICNo ROA
2c0f:1780:3000::/36AFRINICNo ROA
2c0f:1780:4000::/36AFRINICNo ROA
2c0f:1780:5000::/36AFRINICNo 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.