bgpreport

Network · data from 2026-11-12

AS24144 Wuhan LSHIY Network Technology Co., Ltd.

Registry name: LSHIY-AS-AP - Wuhan LSHIY Network Technology Co., Ltd., CN · PeeringDB

0IPv4 routes
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 AS24144, seen from no peer

Announced routes

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

2404:f4c0::/32 Valid RIR databaseAPNIC, RADB 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS24144: AS-LSHIY. 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 (AS24144 isn't in the set, or no route object for AS24144 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 objectsAS24144 in itNot covered
AS-LSHIY RADBlists itself further down17 member sets in no database: AS-AIRSPROJECT, AS-ANILLC, AS-EOIX, AS-IPV6GO, AS-JHL … 1,34232386,796 Yes 0
ARIN (also)1 member set in no database: AS-LSHIY-CUSTOMERS 313,186 Yes 0
RIPE (also)1 member set in no database: AS-LSHIY-CUSTOMERS 313,186 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 18 are in fix.csv.

  • AS-SET: missing member17
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-AIRSPROJECT; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-ANILLC; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-EOIX; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-IPV6GO; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-JHL; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-SHIZUKUGLOBAL-EUROPE; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-SVINE; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-TUNNELBROKERIO; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS-ZH-NET; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS199605:AS-JSMSR-NETWORK; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS200105:AS-HK; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS200372:AS-DORFHOSTER-SET; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS211665:AS-SRNET; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS211747:AS-HYPR-NET; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS215304:AS-SET-CUST-LAIN; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS215364:AS-KKC-NETWORK; no IRR database read has it.
AS-SET: missing memberAS-LSHIYAS-LSHIY (RADB) lists AS216324:AS-HN-NET; no IRR database read has it.

Route objects not announced

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

2404:f4c0:7000::/36APNICValid

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.