bgpreport

Network · data from 2026-11-12

AS328453 Web Africa Networks (Pty) Ltd

Registry name: Web Africa Networks (Pty) Ltd - Web Africa Networks (Pty) Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328453, 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.65.11.0/24 Valid Nonecovered by 102.65.0.0/18 672 100% 67
102.65.12.0/24 Valid Nonecovered by 102.65.0.0/18 672 100% 67
102.65.16.0/20 Valid Nonecovered by 102.65.0.0/18 672 100% 67
102.65.0.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.65.1.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.65.5.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.65.10.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.65.37.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
2c0f:ed28::/32 Valid RIR databaseAFRINIC, RADB 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS328453: AS-WA-NETWORK AS-SET-WA-DD. 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 (AS328453 isn't in the set, or no route object for AS328453 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 objectsAS328453 in itNot covered
AS-WA-NETWORK RADB 2135 Yes 0
AFRINIC (also) 2135 Yes 0
AS-SET-WA-DD RADB 21108 Yes 0
AFRINIC (also) 21108 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.

  • Route object: none3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none102.65.11.0/24No route object for it. A route object for 102.65.0.0/18 with origin AS328453 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328453 in the RIR database for the space.672 of 673
Route object: none102.65.12.0/24No route object for it. A route object for 102.65.0.0/18 with origin AS328453 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328453 in the RIR database for the space.672 of 673
Route object: none102.65.16.0/20No route object for it. A route object for 102.65.0.0/18 with origin AS328453 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328453 in the RIR database for the space.672 of 673

Route objects not announced

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

102.65.0.0/16AFRINIC, RADBValid
102.65.0.0/18AFRINIC, RADBValid
102.65.64.0/18AFRINIC, RADBValid
102.65.64.0/19AFRINIC, RADBValid
102.65.96.0/20AFRINIC, RADBValid
102.65.112.0/21AFRINIC, RADBValid
102.65.120.0/21AFRINIC, RADBValid
102.65.128.0/17AFRINIC, RADBValid
102.222.180.0/22AFRINIC, RADBValid
2c0f:ed28:1000::/36AFRINIC, RADBValid
2c0f:ed28:5000::/36AFRINIC, RADBValid
2c0f:ed28:9000::/36AFRINIC, RADBValid

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.