bgpreport

Network · data from 2026-11-12

AS328521 Wiselink Broadband

Registry name: Wiselink Broadband - Wiselink Broadband, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328521, 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.36.197.0/24 Valid None 27 4%low visibility 10
102.36.196.0/24 Valid None 26 4%low visibility 10
102.36.196.0/23 Valid None 24 4%low visibility 10
102.36.198.0/24 Valid None 21 3%low visibility 8
102.36.199.0/24 Valid None 19 3%low visibility 9
102.36.198.0/23 Valid None 15 2%low visibility 8
102.36.196.0/22 Valid Other origin only 7 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS328521: AS-WISELINK. 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 (AS328521 isn't in the set, or no route object for AS328521 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 objectsAS328521 in itNot covered
AS-WISELINK AFRINIC 110 Yes 7

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

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none102.36.197.0/24No route object for it. Add a route object with origin AS328521 in the RIR database for the space.27 of 673
Route object: none102.36.196.0/24No route object for it. Add a route object with origin AS328521 in the RIR database for the space.26 of 673
Route object: none102.36.196.0/23No route object for it. Add a route object with origin AS328521 in the RIR database for the space.24 of 673
Route object: none102.36.198.0/24No route object for it. Add a route object with origin AS328521 in the RIR database for the space.21 of 673
Route object: none102.36.199.0/24No route object for it. Add a route object with origin AS328521 in the RIR database for the space.19 of 673
Route object: none102.36.198.0/23No route object for it. Add a route object with origin AS328521 in the RIR database for the space.15 of 673
Route object: none102.36.196.0/22Route objects for it name AS328583. Add a route object with origin AS328521 in the RIR database for the space.7 of 673

Route objects not announced

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