Network · data from 2026-11-12

AS45730 LINTASARTA-AS-ID - Aplikanusa Lintasarta, PT

Registry name: LINTASARTA-AS-ID - Aplikanusa Lintasarta, PT, ID · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

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

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

Announced routes

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


100.123.81.0/24 bogon	No ROA	None	8 1%low visibility	5

100.123.81.0/24 bogon

No ROA

None

8 1%low visibility

AS-SET

AS45730 isn't in PeeringDB, where networks name their 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 1 are in fix.csv.

Bogon prefix1

Change	Prefix or set	Detail	Full-table peers
Bogon prefix	100.123.81.0/24	In IANA's special-purpose registry: Shared Address Space (RFC 6598).	8 of 673

Change

Prefix or set

Detail

Full-table peers

Bogon prefix

100.123.81.0/24

In IANA's special-purpose registry: Shared Address Space (RFC 6598).

8 of 673

Route objects not announced

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