Network · data from 2026-11-12

AS147081 Pusat Net Media

Registry name: IDNIC-PUSATNET-AS-ID - PT Pusat Net Media, ID · PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

3Route objects not announced registered with origin AS147081, seen from no peer

Announced routes

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


2401:5be0:300::/48	Valid	Nonecovered by 2401:5be0::/32	3 0%low visibility	5
2401:5be0::/40	Valid	Nonecovered by 2401:5be0::/32	2 0%low visibility	2
2401:5be0:100::/40	Valid	Nonecovered by 2401:5be0::/32	2 0%low visibility	2
103.173.164.0/24	Valid	Other IRR onlyRADB	672 100%	68
103.173.165.0/24	Valid	Other IRR onlyRADB	3 0%low visibility	3

2401:5be0:300::/48

Valid

Nonecovered by 2401:5be0::/32

3 0%low visibility

2401:5be0::/40

Valid

Nonecovered by 2401:5be0::/32

2 0%low visibility

2401:5be0:100::/40

Valid

Nonecovered by 2401:5be0::/32

2 0%low visibility

103.173.164.0/24

Valid

Other IRR onlyRADB

672 100%

103.173.165.0/24

Valid

Other IRR onlyRADB

3 0%low visibility

AS-SET

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

Route object: none3
Route object: RIR2
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	2401:5be0:300::/48	No route object for it. A route object for 2401:5be0::/32 with origin AS147081 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147081 in the RIR database for the space.	3 of 636
Route object: none	2401:5be0::/40	No route object for it. A route object for 2401:5be0::/32 with origin AS147081 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147081 in the RIR database for the space.	2 of 636
Route object: none	2401:5be0:100::/40	No route object for it. A route object for 2401:5be0::/32 with origin AS147081 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147081 in the RIR database for the space.	2 of 636
Route object: RIR	103.173.164.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	103.173.165.0/24	Route object only in RADB. Add it in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2401:5be0:300::/48

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

3 of 636

Route object: none

2401:5be0::/40

2 of 636

Route object: none

2401:5be0:100::/40

2 of 636

Route object: RIR

103.173.164.0/24

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

672 of 673

Route object: RIR

103.173.165.0/24

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

3 of 673

Route objects not announced

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


103.173.164.0/23	RADB	Valid
2001:df2:55c0::/48	RADB	No ROA
2401:5be0::/32	RADB	Valid

103.173.164.0/23

RADB

Valid

2001:df2:55c0::/48

RADB

No ROA

2401:5be0::/32

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.