bgpreport

Network · data from 2026-11-12

AS150279 Lintas Network Solusi

Registry name: IDNIC-LNS-AS-ID - PT Lintas Network Solusi, ID · PeeringDB

6IPv4 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
1Route objects not announced registered with origin AS150279, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS150279, 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.
154.19.39.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
154.19.38.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 69
142.111.205.0/24 Valid RIR databaseARIN, RADB 673 100% 69
154.19.38.0/23 Valid RIR databaseARIN 673 100% 69
103.99.27.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
157.20.144.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
2001:df1:fcc0::/48 Valid RIR databaseALTDB, APNIC, RADB 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS150279: ALTDB::AS150279:AS-LNSNET. 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 (AS150279 isn't in the set, or no route object for AS150279 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.

NameDatabaseASNsSets Route objectsAS150279 in itNot covered
ALTDB::AS150279:AS-LNSNET ALTDB6 member sets in no database: AS137331:AS-CLOUDTEKNOLOGI, AS139378:AS-NEXNETWORK, AS142373:AS-CUST-MNI, AS142393:AS-MEDIASOLUSISUKSES, AS149736:AS-SATRIANET … 821348 Yes 0

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

  • Route object: RIR2
  • AS-SET: missing member6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR154.19.39.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR154.19.38.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS137331:AS-CLOUDTEKNOLOGI; no IRR database read has it.
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS139378:AS-NEXNETWORK; no IRR database read has it.
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS142373:AS-CUST-MNI; no IRR database read has it.
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS142393:AS-MEDIASOLUSISUKSES; no IRR database read has it.
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS149736:AS-SATRIANET; no IRR database read has it.
AS-SET: missing memberALTDB::AS150279:AS-LNSNETAS150279:AS-LNSNET (ALTDB) lists AS150279:AS-LNS; no IRR database read has it.

Route objects not announced

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

217.217.27.0/24RIPEInvalid: origin

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.