bgpreport

Network · data from 2026-11-12

AS152144 LIGHTSTORM ASIA

Registry name: LAPL-AS-AP - LIGHTSTORM ASIA PTE. LTD., SG · PeeringDB

4IPv4 routes 50.0% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS152144, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS152144, 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.
185.1.226.0/23 Invalid: origin None 5 1%low visibility 4
223.31.200.0/24 No ROA None 280 42% 58
210.87.106.0/24 Valid RIR databaseAPNIC 669 99% 66
2401:5760::/32 Valid RIR databaseAPNIC 632 99% 69
210.87.107.0/24 Valid RIR databaseAPNIC 107 16% 40

AS-SET

PeeringDB's irr_as_set for AS152144: AS152144:AS-CUSTOMERS. 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 (AS152144 isn't in the set, or no route object for AS152144 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 objectsAS152144 in itNot covered
AS152144:AS-CUSTOMERS APNIClists itself further down3 member sets in no database: AS-FIRSTLINK-DOWN, AS135327:AS-CUSTOMERS, AS55915:AS-CUSTOMERS 2252819,137 No 5

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.

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • AS-SET: own ASN1
  • AS-SET: missing member3
ChangePrefix or setDetailFull-table peers
ROA: origin185.1.226.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS152144 should announce it, add a ROA for AS152144.5 of 673
Route object: none185.1.226.0/23No route object for it. Add a route object with origin AS152144 in the RIR database for the space.5 of 673
ROA: none223.31.200.0/24No ROA covers it. Add a ROA for AS152144, maxLength 24.280 of 673
Route object: none223.31.200.0/24No route object for it. Add a route object with origin AS152144 in the RIR database for the space.280 of 673
AS-SET: own ASNAS152144:AS-CUSTOMERSAS152144 isn't in AS152144:AS-CUSTOMERS (APNIC) once expanded. Add AS152144 to it.
AS-SET: missing memberAS152144:AS-CUSTOMERSAS152144:AS-CUSTOMERS (APNIC) lists AS-FIRSTLINK-DOWN; no IRR database read has it.
AS-SET: missing memberAS152144:AS-CUSTOMERSAS152144:AS-CUSTOMERS (APNIC) lists AS135327:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS152144:AS-CUSTOMERSAS152144:AS-CUSTOMERS (APNIC) lists AS55915:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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