bgpreport

Network · data from 2026-11-12

AS153391 MINIUMNETLLC-AS-AP - MINIUM NET LLC

Registry name: MINIUMNETLLC-AS-AP - MINIUM NET LLC, VN · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS153391, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153391, 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.
23.128.180.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
23.129.148.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
23.129.172.0/24 Valid RIR databaseARIN 672 100% 67
23.129.204.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
23.141.116.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
23.145.60.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
160.191.156.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
2602:f791::/36 Valid RIR databaseARIN 636 100% 69
2401:d320::/32 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS153391 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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