bgpreport

Network · data from 2026-11-12

AS328523 Enterprise Outsourcing Operations

Registry name: Enterprise Outsourcing Operations (Pty) Ltd - Enterprise Outsourcing Operations (Pty) Ltd, ZA · PeeringDB

3IPv4 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
7No 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 AS328523, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328523, 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.68.156.0/23 No ROA RIR databaseAFRINIC, RADB 670 100% 68
102.68.158.0/24 No ROA RIR databaseAFRINIC, RADB 670 100% 68
102.68.159.0/24 No ROA RIR databaseAFRINIC, RADB 670 100% 68
2c0f:ecc0::/48 No ROA RIR databaseAFRINIC, RADB 636 100% 67
2c0f:ecc0:1::/48 No ROA RIR databaseAFRINIC 635 100% 67
2c0f:ecc0:2::/48 No ROA RIR databaseAFRINIC 635 100% 67
2c0f:ecc0:3::/48 No ROA RIR databaseAFRINIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS328523: AFRINIC::AS328523. 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 (AS328523 isn't in the set, or no route object for AS328523 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 objectsAS328523 in itNot covered
AFRINIC::AS328523 A single AS number, not a set: AS328523 (this network), 7 route objects.

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.

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none102.68.156.0/23No ROA covers it. Add a ROA for AS328523, maxLength 23.670 of 673
ROA: none102.68.158.0/24No ROA covers it. Add a ROA for AS328523, maxLength 24.670 of 673
ROA: none102.68.159.0/24No ROA covers it. Add a ROA for AS328523, maxLength 24.670 of 673
ROA: none2c0f:ecc0::/48No ROA covers it. Add a ROA for AS328523, maxLength 48.636 of 636
ROA: none2c0f:ecc0:1::/48No ROA covers it. Add a ROA for AS328523, maxLength 48.635 of 636
ROA: none2c0f:ecc0:2::/48No ROA covers it. Add a ROA for AS328523, maxLength 48.635 of 636
ROA: none2c0f:ecc0:3::/48No ROA covers it. Add a ROA for AS328523, maxLength 48.635 of 636

Route objects not announced

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