Network · data from 2026-11-12

AS139408 Sanatel

Registry name: SANATEL-AS-ID - PT Sanatel, ID · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139408, 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.143.232.0/24	Valid	Other IRR onlyRADB	673 100%	69
103.143.233.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
160.22.68.0/24	Valid	Other IRR onlyRADB	673 100%	69
160.22.69.0/24	Valid	Other IRR onlyRADB	673 100%	69
2405:5e40::/32	Valid	Other IRR onlyRADB	635 100%	70
123.253.234.0/24	Valid	RIR databaseAPNIC	673 100%	69

AS-SET

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

Route object: RIR5
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	103.143.232.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.143.233.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	160.22.68.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	160.22.69.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	2405:5e40::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

103.143.232.0/24

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

673 of 673

Route object: RIR

103.143.233.0/24

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

673 of 673

Route object: RIR

160.22.68.0/24

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

673 of 673

Route object: RIR

160.22.69.0/24

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

673 of 673

Route object: RIR

2405:5e40::/32

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

635 of 636

Route objects not announced

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


103.143.232.0/23	RADB	Valid
160.22.68.0/23	RADB	Valid

103.143.232.0/23

RADB

Valid

160.22.68.0/23

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.