bgpreport

Network · data from 2026-11-12

AS132429 Digicel Vanuatu

Registry name: DIGICELVANUATU-VU - Digicel Vanuatu LTD, VU · PeeringDB

4IPv4 routes 100.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
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 AS132429, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132429, 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.
2401:7a40::/32 No ROA RIR databaseAPNIC, RADB 636 100% 69
103.20.232.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
103.75.20.0/24 Valid RIR databaseAPNIC, NTTCOM 668 99% 67
103.75.21.0/24 Valid RIR databaseAPNIC, NTTCOM 668 99% 67
202.61.106.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67

AS-SET

AS132429'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: none2401:7a40::/32No ROA covers it. Add a ROA for AS132429, maxLength 32.636 of 636

Route objects not announced

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

103.75.20.0/23NTTCOM, RADBNo 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.