Network · data from 2026-11-12

AS139363 IDNIC-AIO-AS-ID - PT Amerta Indah Otsuka

Registry name: IDNIC-AIO-AS-ID - PT Amerta Indah Otsuka, ID · not in PeeringDB

3IPv4 routes 33.3% RPKI valid · 33.3% with a route object

0IPv6 routes

2RPKI invalid 0 origin · 2 maxLength

0No ROA 2 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS139363, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139363, 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.141.222.0/24	Invalid: maxLength	Nonecovered by 103.141.222.0/23	45 7%low visibility	30
103.141.223.0/24	Invalid: maxLength	Nonecovered by 103.141.222.0/23	45 7%low visibility	30
103.141.222.0/23	Valid	Other IRR onlyRADB	673 100%	69

103.141.222.0/24

Invalid: maxLength

Nonecovered by 103.141.222.0/23

45 7%low visibility

103.141.223.0/24

Invalid: maxLength

Nonecovered by 103.141.222.0/23

45 7%low visibility

103.141.222.0/23

Valid

Other IRR onlyRADB

673 100%

AS-SET

AS139363 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 5 are in fix.csv.

ROA: maxLength2
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	103.141.222.0/24	ROA 103.141.222.0/23 AS139363 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.141.222.0/24.	45 of 673
Route object: none	103.141.222.0/24	No route object for it. A route object for 103.141.222.0/23 with origin AS139363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139363 in the RIR database for the space.	45 of 673
ROA: maxLength	103.141.223.0/24	ROA 103.141.222.0/23 AS139363 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.141.223.0/24.	45 of 673
Route object: none	103.141.223.0/24	No route object for it. A route object for 103.141.222.0/23 with origin AS139363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139363 in the RIR database for the space.	45 of 673
Route object: RIR	103.141.222.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

103.141.222.0/24

ROA 103.141.222.0/23 AS139363 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.141.222.0/24.

45 of 673

Route object: none

103.141.222.0/24

No route object for it. A route object for 103.141.222.0/23 with origin AS139363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139363 in the RIR database for the space.

45 of 673

ROA: maxLength

103.141.223.0/24

ROA 103.141.222.0/23 AS139363 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.141.223.0/24.

45 of 673

Route object: none

103.141.223.0/24

45 of 673

Route object: RIR

103.141.222.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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