bgpreport

Network · data from 2026-11-12

AS58932 PMCI-AS-AP - Palau Mobile Communications Inc.

Registry name: PMCI-AS-AP - Palau Mobile Communications Inc., PW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58932, 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.

103.30.250.0/24 No ROA RIR databaseAPNIC, NTTCOM 672 100% 67
103.30.251.0/24 No ROA RIR databaseAPNIC, NTTCOM 672 100% 67
103.30.248.0/24 No ROA RIR databaseAPNIC, NTTCOM 671 100% 68
103.30.248.0/22 No ROA RIR databaseAPNIC, NTTCOM, RADB 670 100% 68

AS-SET

AS58932 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 8 are in fix.csv.

  • ROA: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.30.250.0/24No ROA covers it. Add a ROA for AS58932, maxLength 24.672 of 673
ROA: none103.30.251.0/24No ROA covers it. Add a ROA for AS58932, maxLength 24.672 of 673
ROA: none103.30.248.0/24No ROA covers it. Add a ROA for AS58932, maxLength 24.671 of 673
ROA: none103.30.248.0/22No ROA covers it. Add a ROA for AS58932, maxLength 22.670 of 673

Route objects not announced

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

103.30.248.0/23APNICNo ROA
103.30.249.0/24APNIC, NTTCOMNo ROA
103.30.250.0/23APNICNo ROA
2401:6e0::/32APNICNo 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.