bgpreport

Network · data from 2026-11-12

AS328350 Network & Computing Consultants

Registry name: Network & Computing Consultants (Pty) Ltd - Network & Computing Consultants (Pty) Ltd, ZA · PeeringDB

17IPv4 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
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS328350, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328350, 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.132.0.0/20 Valid RIR databaseAFRINIC 672 100% 66
102.132.0.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.1.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.2.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.3.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.4.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.5.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.6.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.7.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.8.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.10.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.11.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.12.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.13.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.14.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.15.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.132.9.0/24 Valid RIR databaseAFRINIC 668 99% 66
2c0f:1980::/32 Valid RIR databaseAFRINIC 39 6%low visibility 17

AS-SET

PeeringDB's irr_as_set for AS328350: AS-NCC. 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 (AS328350 isn't in the set, or no route object for AS328350 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 objectsAS328350 in itNot covered
AS-NCC AFRINIC 1118 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 AS328350 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.