bgpreport

Network · data from 2026-11-12

AS140042 Zhipinshang (Hongkong) Electron Communication Technology

Registry name: IZEC-AS-AP - Zhipinshang (Hongkong) Electron Communication Technology Limited, HK · PeeringDB

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

Announced routes

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

31.57.137.0/24 Invalid: origin Other origin only 3 0%low visibility 3
2401:3620:210::/48 Invalid: origin None 3 0%low visibility 3
172.81.105.0/24 Valid Nonecovered by 172.81.104.0/21 671 100% 67
104.251.224.0/24 Valid Other IRR onlyRADB 673 100% 67
104.251.228.0/24 Valid Other IRR onlyRADB 673 100% 67
104.251.225.0/24 Valid Other IRR onlyRADB 671 100% 67
104.251.226.0/24 Valid Other IRR onlyRADB 671 100% 67
104.251.227.0/24 Valid Other IRR onlyRADB 671 100% 67
104.251.235.0/24 Valid Other IRR onlyRADB 671 100% 67
104.251.236.0/24 Valid Other IRR onlyRADB 671 100% 67
172.81.109.0/24 Valid Other IRR onlyRADB 671 100% 67
104.251.232.0/24 Valid Other IRR onlyRADB 670 100% 67
172.81.103.0/24 Valid Other IRR onlyRADB 670 100% 67
104.251.229.0/24 Valid Other IRR onlyRADB 668 99% 67
104.251.230.0/24 Valid Other IRR onlyRADB 668 99% 67
104.251.237.0/24 Valid Other IRR onlyRADB 667 99% 67
103.147.200.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
177.0.132.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
46.249.108.0/24 Valid RIR databaseRIPE 670 100% 67
103.147.201.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 636 95% 67
2401:3620:2102::/48 Valid RIR databaseAPNIC 636 100% 67

AS-SET

AS140042's PeeringDB record names no 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 80 are in fix.csv.

  • ROA: origin2
  • Route object: none3
  • Route object: RIR13
  • Route object: not announced62
ChangePrefix or setDetailFull-table peers
ROA: origin31.57.137.0/24ROAs covering it name AS834, not AS140042. If AS140042 should announce it, add a ROA for AS140042.3 of 673
Route object: none31.57.137.0/24Route objects for it name AS834, AS210507. Add a route object with origin AS140042 in the RIR database for the space.3 of 673
ROA: origin2401:3620:210::/48ROAs covering it name AS151797, not AS140042. If AS140042 should announce it, add a ROA for AS140042.3 of 636
Route object: none2401:3620:210::/48No route object for it. Add a route object with origin AS140042 in the RIR database for the space.3 of 636
Route object: none172.81.105.0/24No route object for it. A route object for 172.81.104.0/21 with origin AS140042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140042 in the RIR database for the space.671 of 673
Route object: RIR104.251.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.251.228.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.251.225.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.226.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.227.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.235.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.236.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.81.109.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.232.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR172.81.103.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR104.251.229.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR104.251.230.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR104.251.237.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

38.47.192.0/18ARINValid
38.181.0.0/18ARINValid
103.147.200.0/23APNIC, NTTCOM, RADBValid
104.251.224.0/20ARIN, RADBValid
104.251.224.0/21RADBValid
104.251.224.0/22RADBValid
104.251.224.0/23RADBValid
104.251.226.0/23RADBValid
104.251.228.0/22RADBValid
104.251.228.0/23RADBValid
104.251.230.0/23RADBValid
104.251.231.0/24RADBValid
104.251.232.0/21RADBValid
104.251.232.0/22RADBValid
104.251.232.0/23RADBValid
104.251.233.0/24RADBValid
104.251.234.0/23RADBValid
104.251.234.0/24RADBValid
104.251.236.0/22RADBValid
104.251.236.0/23RADBValid
104.251.238.0/23RADBValid
104.251.238.0/24RADBValid
104.251.239.0/24RADBValid
172.81.102.0/23ARINValid
172.81.104.0/21ARINValid
172.81.104.0/24RADBValid
172.81.108.0/24RADBValid
177.0.132.0/24APNIC, RADBValid
177.0.133.0/24APNIC, RADBValid
199.165.237.0/24RADBNo ROA
2001:550:a0c::/48RADBNo ROA
2401:3620:2100::/44APNICValid
2401:3620:2100::/45APNICValid
2401:3620:2100::/46APNICValid
2401:3620:2100::/47APNICValid
2401:3620:2100::/48APNICValid
2401:3620:2101::/48APNICValid
2401:3620:2102::/47APNICValid
2401:3620:2103::/48APNICValid
2401:3620:2104::/46APNICValid
2401:3620:2104::/47APNICValid
2401:3620:2104::/48APNICValid
2401:3620:2105::/48APNICValid
2401:3620:2106::/47APNICValid
2401:3620:2106::/48APNICValid
2401:3620:2107::/48APNICValid
2401:3620:2108::/45APNICValid
2401:3620:2108::/46APNICValid
2401:3620:2108::/47APNICValid
2401:3620:2108::/48APNICValid
2401:3620:2109::/48APNICValid
2401:3620:210a::/47APNICValid
2401:3620:210a::/48APNICValid
2401:3620:210b::/48APNICValid
2401:3620:210c::/46APNICValid
2401:3620:210c::/47APNICValid
2401:3620:210c::/48APNICValid
2401:3620:210d::/48APNICValid
2401:3620:210e::/47APNICValid
2401:3620:210e::/48APNICValid
2401:3620:210f::/48APNICValid
2405:bfc0::/32APNICValid

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.