bgpreport

Network · data from 2026-11-12

AS328511 Shoprite Checkers

Registry name: Shoprite Checkers (PTY) Ltd - Shoprite Checkers (PTY) Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328511, 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.206.186.0/24 No ROA Nonecovered by 102.206.186.0/23 672 100% 66
102.68.68.0/24 No ROA RIR databaseAFRINIC 672 100% 66
102.68.69.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS328511: AS328511. 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 (AS328511 isn't in the set, or no route object for AS328511 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 objectsAS328511 in itNot covered
AS328511 A single AS number, not a set: AS328511 (this network), 3 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 5 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none102.206.186.0/24No ROA covers it. Add a ROA for AS328511, maxLength 24.672 of 673
Route object: none102.206.186.0/24No route object for it. A route object for 102.206.186.0/23 with origin AS328511 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328511 in the RIR database for the space.672 of 673
ROA: none102.68.68.0/24No ROA covers it. Add a ROA for AS328511, maxLength 24.672 of 673
ROA: none102.68.69.0/24No ROA covers it. Add a ROA for AS328511, maxLength 24.672 of 673

Route objects not announced

Route objects with origin AS328511 whose prefix no peer sees AS328511 announce. Many are kept on purpose (backup routes, space announced only in some places).

102.206.186.0/23AFRINICNo ROA

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.