bgpreport

Network · data from 2026-11-12

AS150285 Long Mao Network

Registry name: LMHCC-AS-AP - Long Mao Home Center Co.ltd.,, MM · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
17IPv6 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
0Route objects not announced registered with origin AS150285, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS150285, 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.
103.38.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.250.76.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
2400:e160::/32 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:1000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:2000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:3000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:4000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:5000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:6000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:7000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:8000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:9000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:a000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:b000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:c000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:d000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:e000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69
2400:e160:f000::/36 Valid RIR databaseAPNIC, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS150285: AS150285:AS-LMHCC. 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 (AS150285 isn't in the set, or no route object for AS150285 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 objectsAS150285 in itNot covered
AS150285:AS-LMHCC APNIC 010 No 19

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.

  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS150285:AS-LMHCCAS150285 isn't in AS150285:AS-LMHCC (APNIC) once expanded. Add AS150285 to it.

Route objects not announced

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