bgpreport

Network · data from 2026-11-12

AS136501 HKBNES-AS-AP - HKBN Enterprise Solutions HK Limited

Registry name: HKBNES-AS-AP - HKBN Enterprise Solutions HK Limited, HK · not in PeeringDB

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

Announced routes

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

163.223.77.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.228.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.229.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.230.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.231.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.232.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.233.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.234.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.235.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.236.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.237.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

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

  • Route object: not announced41

Route objects not announced

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

38.76.140.0/23ALTDBNo ROA
38.248.20.0/24ALTDBNo ROA
38.248.21.0/24ALTDBNo ROA
45.207.128.0/20RADBValid
82.38.42.0/23RIPEValid
82.38.46.0/23RADB, RIPEValid
82.38.80.0/23RADB, RIPEValid
95.134.6.0/24RADB, RIPEValid
95.134.200.0/24RADB, RIPEValid
95.134.207.0/24RADB, RIPEValid
95.134.214.0/24RADB, RIPEValid
95.134.215.0/24RADB, RIPEValid
95.134.222.0/24RADB, RIPEValid
95.135.40.0/24RADB, RIPEValid
103.177.44.0/23APNICValid
103.177.44.0/24APNICValid
103.177.45.0/24APNICValid
143.14.144.0/24RADB, RIPEValid
143.14.214.0/24RADB, RIPEValid
143.14.222.0/24RADB, RIPEValid
151.242.180.0/22ALTDB, RADB, RIPEValid
151.242.255.0/24RIPEInvalid: origin
154.92.192.0/24RADBValid
154.92.193.0/24RADBValid
154.92.194.0/24RADBValid
154.92.195.0/24RADBValid
154.92.196.0/24RADBValid
154.92.197.0/24RADBValid
154.92.198.0/24RADBValid
173.213.107.0/24ARINValid
175.29.22.0/23APNIC, RADBValid
175.29.22.0/24APNICValid
175.29.23.0/24APNICValid
178.83.82.0/23RADB, RIPEValid
202.60.228.0/22APNICValid
202.60.232.0/22APNICValid
202.60.236.0/23APNICValid
202.60.238.0/24APNICValid
202.85.53.0/24ALTDBNo ROA
202.85.76.0/24ALTDBNo ROA
216.38.168.0/22ARINValid

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.