bgpreport

Network · data from 2026-11-12

AS328220 Altech Radio Holdings

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

6IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 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
3Route objects not announced registered with origin AS328220, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328220, 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.

156.0.224.0/21 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
156.0.226.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
156.0.227.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
156.0.228.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
156.0.229.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
156.0.231.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
2c0f:f158::/32 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 635 100% 69

AS-SET

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

  • ROA: none7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none156.0.224.0/21No ROA covers it. Add a ROA for AS328220, maxLength 21.673 of 673
ROA: none156.0.226.0/24No ROA covers it. Add a ROA for AS328220, maxLength 24.673 of 673
ROA: none156.0.227.0/24No ROA covers it. Add a ROA for AS328220, maxLength 24.673 of 673
ROA: none156.0.228.0/24No ROA covers it. Add a ROA for AS328220, maxLength 24.673 of 673
ROA: none156.0.229.0/24No ROA covers it. Add a ROA for AS328220, maxLength 24.673 of 673
ROA: none156.0.231.0/24No ROA covers it. Add a ROA for AS328220, maxLength 24.673 of 673
ROA: none2c0f:f158::/32No ROA covers it. Add a ROA for AS328220, maxLength 32.635 of 636

Route objects not announced

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

156.0.224.0/24AFRINIC, RIPE-NONAUTHNo ROA
156.0.225.0/24AFRINIC, RIPE-NONAUTHNo ROA
156.0.230.0/24AFRINIC, RIPE-NONAUTHNo 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.