bgpreport

Network · data from 2026-11-12

AS140024 IDNIC-PELINDO3-AS-ID - PT Pelabuhan Indonesia III (Persero)

Registry name: IDNIC-PELINDO3-AS-ID - PT Pelabuhan Indonesia III (Persero), ID · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS140024, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140024, 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.149.155.0/24 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 70

AS-SET

AS140024 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none103.149.155.0/24No ROA covers it. Add a ROA for AS140024, maxLength 24.673 of 673
Route object: RIR103.149.155.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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