Skip to content

Autonomous System

AS149014 — BOJINGCOLIMITED-AS-AP - bo jing(HK)

Last fetched

AS149014 is an Autonomous System operated by BOJINGCOLIMITED-AS-AP - bo jing and registered in HK. As of Tue, 04 Aug 2026 17:02:52 GMT, it announces 45 routed IP prefixes and peers with 11 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS149014Routing diversity8.3/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/149014

Routing footprint

AS149014 announces 45 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

11 distinct peers via BGP. The first 11 are listed below.

Peer ASNOperatorCountry
AS132813AISI-AS-AP - HK AISI CLOUD COMPUTING LIMITEDHK
AS137443CHANGLIAN-AS-AP - ChangLian Network Technology Co., LimitedHK
AS150706HKZTCL-AS-AP - Hong Kong Zhengxing Technology Co., Ltd.HK
AS152450CHANGLIAN1-AS-AP - ChangLian Network Technology Co., LimitedHK
AS154309INTELLIGENT1-AS-AP - Intelligent Cloud LimitedHK
AS205512Zhengxing - HONG KONG ZHENG XING TECHNOLOGY LIMITEDHK
AS206888HANMING-AS - HanMing HK LimitedHK
AS207190Yuhonet - YUHONET INTERNATIONAL LIMITEDHK
AS208628changlian - ChangLian Network Technology Co.,LimitedHK
AS21859ZEN-ECN - Zenlayer IncUS
AS2914NTT-DATA-2914 - NTT America, Inc.US

Blast radius

Count of dependent hostnames if AS149014 disappeared from the routing table.

106 hostnames depend on this network.Exact count across all 42 announced prefixes. Snapshot Sun, 31 May 2026 13:00:38 GMT.

MOAS / hijack watch

Prefixes routed by AS149014 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS149014 is unique to AS149014 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS149014.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS149014"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.