Skip to content

Autonomous System

AS56046 — CMNET-Jiangsu-AP - China Mobile communications corporation(CN)

Last fetched

AS56046 is an Autonomous System operated by CMNET-Jiangsu-AP - China Mobile communications corporation and registered in CN. As of Mon, 03 Aug 2026 23:07:43 GMT, it announces 5,328 routed IP prefixes and peers with 9 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS56046Routing diversity10.0/10Peering density4.0/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/56046

Routing footprint

AS56046 announces 5,328 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

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

Peer ASNOperatorCountry
AS137718VOLCANO-ENGINE - Beijing Volcano Engine Technology Co., Ltd.CN
AS146822CHINANET-XINFU - Shenzhenshi Zhongyun Shujujishu YouxiangongsiCN
AS151300AS151300-85 - China Internet Network Information CenterCN
AS18257BITCOMM-AS - ChangZhou Bitcomm Software Technology Co., LimitedCN
AS56012LGNET-China - LGNET ChinaCN
AS59048CLOUDTIMES - Bei Jing Cloud Times Technology Co.,LtdCN
AS63708LTIDC - Guangdong LITONG Network Technology LimitedCN
AS9808CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd.CN
AS9939DYXNET-CN - DYXNET of Shenzhen Communication Co., Ltd.CN

Blast radius

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

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

MOAS / hijack watch

Prefixes routed by AS56046 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 AS56046 is unique to AS56046 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS56046.

Cypher and MCP

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

MATCH (a:ASN {name: "AS56046"})-[: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.