Network · data from 2026-11-12

AS152029 PT Andromega Data Nusantara

Registry name: IDNIC-ANDROMEGA-AS-ID - PT Andromega Data Nusantara, ID · PeeringDB

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

0IPv6 routes

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

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

Announced routes

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


36.50.56.0/23	Valid	Other IRR onlyRADB	673 100%	69
36.50.56.0/24	Valid	Other IRR onlyRADB	673 100%	69
36.50.57.0/24	Valid	Other IRR onlyRADB	673 100%	69

AS-SET

PeeringDB's irr_as_set for AS152029: AS152029:AS-ANDROMEGA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS152029 isn't in the set, or no route object for AS152029 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS152029 in it	Not covered
AS152029:AS-ANDROMEGA	RADB	11	1	33	No	3
	APNIC (also)	4	1	8	No	3

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

Route object: RIR3
AS-SET: own ASN1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	36.50.56.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	36.50.56.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	36.50.57.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
AS-SET: own ASN	AS152029:AS-ANDROMEGA	AS152029 isn't in AS152029:AS-ANDROMEGA (RADB) once expanded. Add AS152029 to it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

36.50.56.0/23

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

673 of 673

Route object: RIR

36.50.56.0/24

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

673 of 673

Route object: RIR

36.50.57.0/24

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

673 of 673

AS-SET: own ASN

AS152029:AS-ANDROMEGA

AS152029 isn't in AS152029:AS-ANDROMEGA (RADB) once expanded. Add AS152029 to it.

Route objects not announced

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