bgpreport

Network · data from 2026-11-12

AS328191 Companhia Santomense de Telecomunicacoes

Registry name: Companhia Santomense de Telecomunicacoes - Companhia Santomense de Telecomunicacoes, ST · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328191, 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.201.20.0/22 No ROA RIR databaseAFRINIC 669 99% 68
102.201.23.0/24 No ROA RIR databaseAFRINIC 669 99% 68
102.201.20.0/24 No ROA RIR databaseAFRINIC 667 99% 68
102.201.21.0/24 No ROA RIR databaseAFRINIC 667 99% 68
2c0f:fa88::/32 No ROA RIR databaseAFRINIC 636 100% 69
102.202.92.0/22 Valid RIR databaseAFRINIC 671 100% 68
102.206.44.0/22 Valid RIR databaseAFRINIC 671 100% 68
197.159.160.0/19 Valid RIR databaseAFRINIC 671 100% 68
197.159.172.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.159.175.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.159.176.0/24 Valid RIR databaseAFRINIC 671 100% 68
102.202.93.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.202.94.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.206.44.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.206.45.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.206.46.0/24 Valid RIR databaseAFRINIC 669 99% 68
102.206.47.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.161.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.162.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.163.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.164.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.165.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.166.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.167.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.168.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.169.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.170.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.171.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.174.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.178.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.179.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.180.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.185.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.188.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.173.0/24 Valid RIR databaseAFRINIC 666 99% 68
197.159.177.0/24 Valid RIR databaseAFRINIC 666 99% 68

AS-SET

AS328191'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 17 are in fix.csv.

  • ROA: none5
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none102.201.20.0/22No ROA covers it. Add a ROA for AS328191, maxLength 22.669 of 673
ROA: none102.201.23.0/24No ROA covers it. Add a ROA for AS328191, maxLength 24.669 of 673
ROA: none102.201.20.0/24No ROA covers it. Add a ROA for AS328191, maxLength 24.667 of 673
ROA: none102.201.21.0/24No ROA covers it. Add a ROA for AS328191, maxLength 24.667 of 673
ROA: none2c0f:fa88::/32No ROA covers it. Add a ROA for AS328191, maxLength 32.636 of 636

Route objects not announced

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

102.201.22.0/24AFRINICNo ROA
102.202.92.0/24AFRINICValid
102.202.95.0/24AFRINICValid
197.159.160.0/24AFRINICValid
197.159.181.0/24AFRINICValid
197.159.182.0/24AFRINICValid
197.159.183.0/24AFRINICValid
197.159.184.0/24AFRINICValid
197.159.186.0/24AFRINICValid
197.159.189.0/24AFRINICValid
197.159.190.0/24AFRINICValid
197.159.191.0/24AFRINICValid

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.