bgpreport

Network · data from 2026-11-12

AS328154 NETSPACE -SERVICOS DE TELECOMUNICACOES, LDA - NETSPACE -SERVICOS DE TELECOMUNICACOES, LDA

Registry name: NETSPACE -SERVICOS DE TELECOMUNICACOES, LDA - NETSPACE -SERVICOS DE TELECOMUNICACOES, LDA, AO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328154, 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.213.32.0/22 No ROA RIR databaseAFRINIC 672 100% 67
160.119.240.0/22 No ROA RIR databaseAFRINIC, RADB 672 100% 67
2c0f:f060::/32 No ROA RIR databaseAFRINIC 633 100% 67
102.213.33.0/24 No ROA RIR databaseAFRINIC 3 0%low visibility 2
102.213.34.0/24 No ROA RIR databaseAFRINIC 3 0%low visibility 2
102.213.35.0/24 No ROA RIR databaseAFRINIC 3 0%low visibility 2
160.119.240.0/24 No ROA RIR databaseAFRINIC, RADB 3 0%low visibility 2
160.119.241.0/24 No ROA RIR databaseAFRINIC, RADB 3 0%low visibility 2
160.119.242.0/24 No ROA RIR databaseAFRINIC, RADB 3 0%low visibility 2
160.119.243.0/24 No ROA RIR databaseAFRINIC, RADB 3 0%low visibility 2

AS-SET

AS328154 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 11 are in fix.csv.

  • ROA: none10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none102.213.32.0/22No ROA covers it. Add a ROA for AS328154, maxLength 22.672 of 673
ROA: none160.119.240.0/22No ROA covers it. Add a ROA for AS328154, maxLength 22.672 of 673
ROA: none2c0f:f060::/32No ROA covers it. Add a ROA for AS328154, maxLength 32.633 of 636
ROA: none102.213.33.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none102.213.34.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none102.213.35.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none160.119.240.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none160.119.241.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none160.119.242.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673
ROA: none160.119.243.0/24No ROA covers it. Add a ROA for AS328154, maxLength 24.3 of 673

Route objects not announced

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

102.213.32.0/24AFRINICNo 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.