bgpreport

Network · data from 2026-11-12

AS328638 Letaba Networks (Pty) Ltd

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

21IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS328638, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328638, 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.141.64.0/19 Valid RIR databaseAFRINIC 672 100% 67
102.207.180.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.216.104.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.221.220.0/22 Valid RIR databaseAFRINIC 672 100% 67
154.65.112.0/20 Valid RIR databaseAFRINIC 672 100% 67
160.226.160.0/20 Valid RIR databaseAFRINIC 672 100% 67
196.6.112.0/21 Valid RIR databaseAFRINIC 672 100% 67
2c0f:f0a0::/32 Valid RIR databaseAFRINIC 634 100% 67
102.141.80.0/20 Valid RIR databaseAFRINIC 379 56% 64
102.207.180.0/23 Valid RIR databaseAFRINIC 379 56% 64
102.207.182.0/23 Valid RIR databaseAFRINIC 379 56% 64
102.216.104.0/23 Valid RIR databaseAFRINIC 379 56% 64
102.216.106.0/23 Valid RIR databaseAFRINIC 379 56% 64
102.221.222.0/23 Valid RIR databaseAFRINIC 379 56% 64
154.65.112.0/21 Valid RIR databaseAFRINIC 379 56% 64
154.65.120.0/21 Valid RIR databaseAFRINIC 379 56% 64
160.226.160.0/21 Valid RIR databaseAFRINIC 379 56% 64
160.226.168.0/21 Valid RIR databaseAFRINIC 379 56% 64
196.6.112.0/22 Valid RIR databaseAFRINIC 379 56% 64
196.6.116.0/22 Valid RIR databaseAFRINIC 379 56% 64
102.141.64.0/20 Valid RIR databaseAFRINIC 376 56% 64
102.221.220.0/23 Valid RIR databaseAFRINIC 376 56% 64

AS-SET

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

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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