Network · data from 2026-11-12

AS138860 AYONET

Registry name: AYO-AS-ID - PT. JAYA LINTAS INDONESIA, ID · PeeringDB

6IPv4 routes 100.0% RPKI valid · 83.3% with a route object

7IPv6 routes 100.0% RPKI valid · 14.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 7 with no route object for this origin

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

2Route objects not announced registered with origin AS138860, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138860, 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.139.26.0/23	Valid	None	673 100%	68
2404:d8c0:460::/44	Valid	Nonecovered by 2404:d8c0::/32	636 100%	69
2404:d8c0:464::/48	Valid	Nonecovered by 2404:d8c0::/32	636 100%	70
2404:d8c0:3174::/48	Valid	Nonecovered by 2404:d8c0::/32	636 100%	69
2404:d8c0:3322::/48	Valid	Nonecovered by 2404:d8c0::/32	636 100%	69
2404:d8c0:fe00::/40	Valid	Nonecovered by 2404:d8c0::/32	635 100%	68
2407:72c0::/48	Valid	None	634 100%	70
103.139.26.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
103.139.27.0/24	Valid	Other IRR onlyRADB	673 100%	69
103.152.92.0/24	Valid	Other IRR onlyRADB	672 100%	69
103.152.93.0/24	Valid	Other IRR onlyRADB	672 100%	67
2404:d8c0::/32	Valid	Other IRR onlyRADB	636 100%	70
201.3.231.0/24	Valid	RIR databaseRIPE	673 100%	69

AS-SET

AS138860'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 14 are in fix.csv.

Route object: none7
Route object: RIR5
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	103.139.26.0/23	No route object for it. Add a route object with origin AS138860 in the RIR database for the space.	673 of 673
Route object: none	2404:d8c0:460::/44	No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.	636 of 636
Route object: none	2404:d8c0:464::/48	No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.	636 of 636
Route object: none	2404:d8c0:3174::/48	No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.	636 of 636
Route object: none	2404:d8c0:3322::/48	No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.	636 of 636
Route object: none	2404:d8c0:fe00::/40	No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.	635 of 636
Route object: none	2407:72c0::/48	No route object for it. Add a route object with origin AS138860 in the RIR database for the space.	634 of 636
Route object: RIR	103.139.26.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.139.27.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.152.92.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	103.152.93.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2404:d8c0::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

103.139.26.0/23

No route object for it. Add a route object with origin AS138860 in the RIR database for the space.

673 of 673

Route object: none

2404:d8c0:460::/44

No route object for it. A route object for 2404:d8c0::/32 with origin AS138860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138860 in the RIR database for the space.

636 of 636

Route object: none

2404:d8c0:464::/48

636 of 636

Route object: none

2404:d8c0:3174::/48

636 of 636

Route object: none

2404:d8c0:3322::/48

636 of 636

Route object: none

2404:d8c0:fe00::/40

635 of 636

Route object: none

2407:72c0::/48

No route object for it. Add a route object with origin AS138860 in the RIR database for the space.

634 of 636

Route object: RIR

103.139.26.0/24

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

673 of 673

Route object: RIR

103.139.27.0/24

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

673 of 673

Route object: RIR

103.152.92.0/24

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

672 of 673

Route object: RIR

103.152.93.0/24

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

672 of 673

Route object: RIR

2404:d8c0::/32

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

636 of 636

Route objects not announced

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


103.152.92.0/23	RADB	Valid
2404:d8c0:ff00::/40	RADB	Valid

103.152.92.0/23

RADB

Valid

2404:d8c0:ff00::/40

RADB

Valid

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.