bgpreport

Network · data from 2026-11-12

AS22572 Sentech SOC

Registry name: Sentech SOC Ltd - Sentech SOC Ltd, ZA · PeeringDB

5IPv4 routes 80.0% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS22572, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22572, 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.
66.18.94.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
66.18.64.0/20 Valid RIR databaseAFRINIC 673 100% 66
66.18.80.0/21 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
66.18.88.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
66.18.92.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
2c0f:e9e0::/32 Valid RIR databaseAFRINIC 636 100% 70

AS-SET

AS22572's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none66.18.94.0/24No ROA covers it. Add a ROA for AS22572, maxLength 24.673 of 673

Route objects not announced

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

66.18.64.0/19RIPE-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.