bgpreport

Network · data from 2026-11-12

AS328855 NCW (Pty) Ltd

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328855, 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.203.16.0/22 No ROA RIR databaseAFRINIC 673 100% 66
102.219.232.0/22 No ROA RIR databaseAFRINIC 673 100% 66
2c0f:3600::/32 No ROA RIR databaseAFRINIC 635 100% 67
102.203.16.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.203.17.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.203.18.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.203.19.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.219.232.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.219.233.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.219.234.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
102.219.235.0/24 No ROA RIR databaseAFRINIC 20 3%low visibility 8
2c0f:3600:100::/40 No ROA RIR databaseAFRINIC 15 2%low visibility 8
2c0f:3600:200::/40 No ROA RIR databaseAFRINIC 15 2%low visibility 8
2c0f:3600:300::/40 No ROA RIR databaseAFRINIC 15 2%low visibility 8

AS-SET

PeeringDB's irr_as_set for AS328855: AS-NCW. 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 (AS328855 isn't in the set, or no route object for AS328855 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 objectsAS328855 in itNot covered
AS-NCW AFRINIC 1114 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 14 are in fix.csv.

  • ROA: none14
ChangePrefix or setDetailFull-table peers
ROA: none102.203.16.0/22No ROA covers it. Add a ROA for AS328855, maxLength 22.673 of 673
ROA: none102.219.232.0/22No ROA covers it. Add a ROA for AS328855, maxLength 22.673 of 673
ROA: none2c0f:3600::/32No ROA covers it. Add a ROA for AS328855, maxLength 32.635 of 636
ROA: none102.203.16.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.203.17.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.203.18.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.203.19.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.219.232.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.219.233.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.219.234.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none102.219.235.0/24No ROA covers it. Add a ROA for AS328855, maxLength 24.20 of 673
ROA: none2c0f:3600:100::/40No ROA covers it. Add a ROA for AS328855, maxLength 40.15 of 636
ROA: none2c0f:3600:200::/40No ROA covers it. Add a ROA for AS328855, maxLength 40.15 of 636
ROA: none2c0f:3600:300::/40No ROA covers it. Add a ROA for AS328855, maxLength 40.15 of 636

Route objects not announced

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