bgpreport

Network · data from 2026-11-12

AS151311 HMKJ - Shenzhen Humeng Technology Co., Ltd

Registry name: HMKJ - Shenzhen Humeng Technology Co., Ltd, CN · not in PeeringDB

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

Announced routes

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

2401:71c0:1::/48 Valid None 3 0%low visibility 3
2401:71c0:2::/48 Valid None 3 0%low visibility 3
2401:71c0:3::/48 Valid None 3 0%low visibility 3
2401:71c0:4::/48 Valid None 3 0%low visibility 3
2401:71c0:5::/48 Valid None 3 0%low visibility 3
2401:71c0:6::/48 Valid None 3 0%low visibility 3
2401:71c0:7::/48 Valid None 3 0%low visibility 3
2401:71c0:8::/48 Valid None 3 0%low visibility 3
2401:71c0:9::/48 Valid None 3 0%low visibility 3
2401:71c0:a::/48 Valid None 3 0%low visibility 3
2401:71c0:b::/48 Valid None 3 0%low visibility 3
2401:71c0:c::/48 Valid None 3 0%low visibility 3
2401:71c0:d::/48 Valid None 3 0%low visibility 3
2401:71c0:e::/48 Valid None 3 0%low visibility 3
2401:71c0:f::/48 Valid None 3 0%low visibility 3
2401:71c0:11::/48 Valid None 3 0%low visibility 3
2401:71c0:12::/48 Valid None 3 0%low visibility 3
2401:71c0:13::/48 Valid None 3 0%low visibility 3
2401:71c0:14::/48 Valid None 3 0%low visibility 3
123.58.32.0/24 Valid Other origin only 1 0%low visibility 3
123.58.33.0/24 Valid Other origin only 1 0%low visibility 3
123.58.34.0/24 Valid Other origin only 1 0%low visibility 3
123.58.36.0/24 Valid Other origin only 1 0%low visibility 3
123.58.44.0/24 Valid Other origin only 1 0%low visibility 3
123.58.64.0/24 Valid Other origin only 1 0%low visibility 3

AS-SET

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

  • Route object: none25
ChangePrefix or setDetailFull-table peers
Route object: none2401:71c0:1::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:2::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:3::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:4::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:5::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:6::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:7::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:8::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:9::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:a::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:b::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:c::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:d::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:e::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:f::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:11::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:12::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:13::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none2401:71c0:14::/48No route object for it. Add a route object with origin AS151311 in the RIR database for the space.3 of 636
Route object: none123.58.32.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673
Route object: none123.58.33.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673
Route object: none123.58.34.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673
Route object: none123.58.36.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673
Route object: none123.58.44.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673
Route object: none123.58.64.0/24Route objects for it name AS4816. Add a route object with origin AS151311 in the RIR database for the space.1 of 673

Route objects not announced

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