bgpreport

Network · data from 2026-11-12

AS328278 WiberSolutions

Registry name: WiberSolutions (Pty) Ltd - WiberSolutions (Pty) Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328278, 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.165.90.0/24 No ROA Nonecovered by 102.165.88.0/21 671 100% 68
102.165.64.0/19 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
2c0f:ec98::/32 No ROA RIR databaseAFRINIC 636 100% 67
102.165.64.0/20 No ROA RIR databaseAFRINIC 41 6%low visibility 18
102.165.80.0/20 No ROA RIR databaseAFRINIC 41 6%low visibility 18
102.165.64.0/21 No ROA RIR databaseAFRINIC 27 4%low visibility 13
102.165.72.0/21 No ROA RIR databaseAFRINIC 27 4%low visibility 13
102.165.80.0/21 No ROA RIR databaseAFRINIC 27 4%low visibility 13
102.165.88.0/21 No ROA RIR databaseAFRINIC 27 4%low visibility 13

AS-SET

PeeringDB's irr_as_set for AS328278: AFRINIC::AS-SET-WIBERNET. 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 (AS328278 isn't in the set, or no route object for AS328278 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 objectsAS328278 in itNot covered
AFRINIC::AS-SET-WIBERNET AFRINIC 118 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 10 are in fix.csv.

  • ROA: none9
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none102.165.90.0/24No ROA covers it. Add a ROA for AS328278, maxLength 24.671 of 673
Route object: none102.165.90.0/24No route object for it. A route object for 102.165.88.0/21 with origin AS328278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328278 in the RIR database for the space.671 of 673
ROA: none102.165.64.0/19No ROA covers it. Add a ROA for AS328278, maxLength 19.673 of 673
ROA: none2c0f:ec98::/32No ROA covers it. Add a ROA for AS328278, maxLength 32.636 of 636
ROA: none102.165.64.0/20No ROA covers it. Add a ROA for AS328278, maxLength 20.41 of 673
ROA: none102.165.80.0/20No ROA covers it. Add a ROA for AS328278, maxLength 20.41 of 673
ROA: none102.165.64.0/21No ROA covers it. Add a ROA for AS328278, maxLength 21.27 of 673
ROA: none102.165.72.0/21No ROA covers it. Add a ROA for AS328278, maxLength 21.27 of 673
ROA: none102.165.80.0/21No ROA covers it. Add a ROA for AS328278, maxLength 21.27 of 673
ROA: none102.165.88.0/21No ROA covers it. Add a ROA for AS328278, maxLength 21.27 of 673

Route objects not announced

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