bgpreport

Network · data from 2026-11-12

AS36917 Angola Comunicacoes & Systems LDA

Registry name: Angola Comunicacoes & Systems LDA - Angola Comunicacoes & Systems LDA, AO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36917, 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.
41.223.42.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
41.223.101.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
41.223.102.0/24 No ROA RIR databaseAFRINIC 672 100% 67

AS-SET

AS36917'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 13 are in fix.csv.

  • ROA: none3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none41.223.42.0/24No ROA covers it. Add a ROA for AS36917, maxLength 24.672 of 673
ROA: none41.223.101.0/24No ROA covers it. Add a ROA for AS36917, maxLength 24.672 of 673
ROA: none41.223.102.0/24No ROA covers it. Add a ROA for AS36917, maxLength 24.672 of 673

Route objects not announced

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

41.223.40.0/23RADBNo ROA
41.223.40.0/24AFRINICNo ROA
41.223.41.0/24AFRINICNo ROA
41.223.43.0/24AFRINIC, RADBNo ROA
41.223.100.0/24AFRINIC, RADBNo ROA
41.223.102.0/23AFRINIC, RADBNo ROA
41.223.103.0/24AFRINICNo ROA
169.239.76.0/22RADBNo ROA
196.223.13.0/24RADBNo ROA
2c0f:fa60::/32AFRINICNo 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.