bgpreport

Network · data from 2026-11-12

AS140504 Digicel Nauru

Registry name: DIGICELNAURU-AS-AP - Digicel Nauru Corporation, NR · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS140504, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140504, 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.
203.98.227.0/24 Invalid: origin Other origin only 37 5%low visibility 25
43.230.6.0/24 Valid RIR databaseALTDB, APNIC, RADB 671 100% 68
103.20.124.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.49.173.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.49.174.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
203.190.216.0/24 Valid RIR databaseALTDB, APNIC 670 100% 68
2403:ae80::/32 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

AS140504'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: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin203.98.227.0/24ROAs covering it name AS55722, AS141368, not AS140504. If AS140504 should announce it, add a ROA for AS140504.37 of 673
Route object: none203.98.227.0/24Route objects for it name AS141368. Add a route object with origin AS140504 in the RIR database for the space.37 of 673

Route objects not announced

Every route object with origin AS140504 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.