Network · data from 2026-11-12

AS329272 Servercore Africa Ltd - Servercore Africa Ltd

Registry name: Servercore Africa Ltd - Servercore Africa Ltd, KE · not in PeeringDB

19IPv4 routes 84.2% 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

3No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS329272, seen from no peer

Announced routes

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


213.148.16.0/23	No ROA	RIR databaseRADB, RIPE	673 100%	66
213.148.16.0/24	No ROA	RIR databaseRADB, RIPE	671 100%	68
213.148.17.0/24	No ROA	RIR databaseRADB, RIPE	671 100%	68
102.214.68.0/22	Valid	RIR databaseAFRINIC, RADB	673 100%	66
45.150.188.0/22	Valid	RIR databaseRIPE	671 100%	68
45.150.188.0/24	Valid	RIR databaseRIPE	671 100%	68
45.150.189.0/24	Valid	RIR databaseRIPE	671 100%	68
45.150.190.0/24	Valid	RIR databaseRIPE	671 100%	68
45.150.191.0/24	Valid	RIR databaseRIPE	671 100%	68
102.214.68.0/24	Valid	RIR databaseAFRINIC, RADB	671 100%	68
102.214.69.0/24	Valid	RIR databaseAFRINIC, RADB	671 100%	68
102.214.70.0/24	Valid	RIR databaseAFRINIC, RADB	671 100%	68
102.214.71.0/24	Valid	RIR databaseAFRINIC, RADB	671 100%	68
153.80.208.0/22	Valid	RIR databaseRIPE	671 100%	68
185.240.48.0/22	Valid	RIR databaseRIPE	671 100%	68
185.240.48.0/24	Valid	RIR databaseRIPE	671 100%	68
185.240.49.0/24	Valid	RIR databaseRIPE	671 100%	68
185.240.50.0/24	Valid	RIR databaseRIPE	671 100%	68
185.240.51.0/24	Valid	RIR databaseRIPE	671 100%	68
2c0f:4b40::/32	Valid	RIR databaseAFRINIC, RADB	636 100%	69

AS-SET

AS329272 isn't in PeeringDB, where networks name their AS-SET.

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: none3
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: none	213.148.16.0/23	No ROA covers it. Add a ROA for AS329272, maxLength 23.	673 of 673
ROA: none	213.148.16.0/24	No ROA covers it. Add a ROA for AS329272, maxLength 24.	671 of 673
ROA: none	213.148.17.0/24	No ROA covers it. Add a ROA for AS329272, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

213.148.16.0/23

No ROA covers it. Add a ROA for AS329272, maxLength 23.

673 of 673

ROA: none

213.148.16.0/24

No ROA covers it. Add a ROA for AS329272, maxLength 24.

671 of 673

ROA: none

213.148.17.0/24

No ROA covers it. Add a ROA for AS329272, maxLength 24.

671 of 673

Route objects not announced

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


153.80.208.0/24	RIPE	Valid
153.80.209.0/24	RIPE	Valid
153.80.210.0/24	RIPE	Valid
153.80.211.0/24	RIPE	Valid

153.80.208.0/24

RIPE

Valid

153.80.209.0/24

RIPE

Valid

153.80.210.0/24

RIPE

Valid

153.80.211.0/24

RIPE

Valid

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.