bgpreport

Network · data from 2026-11-12

AS328223 VOIPTECH

Registry name: VOIPTECH LIMITADA - VOIPTECH LIMITADA, MZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328223, 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.208.16.0/22 No ROA RIR databaseAFRINIC 669 99% 68
160.119.156.0/22 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 668 99% 68
2c0f:5d80::/32 No ROA RIR databaseAFRINIC, RADB 633 100% 69
102.208.16.0/24 Valid RIR databaseAFRINIC 670 100% 68
102.208.18.0/24 Valid RIR databaseAFRINIC 670 100% 68
160.119.156.0/24 Valid RIR databaseAFRINIC 670 100% 68
160.119.157.0/24 Valid RIR databaseAFRINIC 670 100% 68
160.119.158.0/24 Valid RIR databaseAFRINIC 670 100% 68
160.119.159.0/24 Valid RIR databaseAFRINIC 670 100% 68
102.208.17.0/24 Valid RIR databaseAFRINIC 669 99% 67
102.208.19.0/24 Valid RIR databaseAFRINIC 667 99% 68

AS-SET

AS328223'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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none102.208.16.0/22No ROA covers it. Add a ROA for AS328223, maxLength 22.669 of 673
ROA: none160.119.156.0/22No ROA covers it. Add a ROA for AS328223, maxLength 22.668 of 673
ROA: none2c0f:5d80::/32No ROA covers it. Add a ROA for AS328223, maxLength 32.633 of 636

Route objects not announced

Every route object with origin AS328223 is announced.

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.