Autonomous System
AS58563
Last fetched
AS58563 is operated by CHINATELECOM-Hubei-IDC - CHINANET Hubei province network, registered in CN, and announces 210 prefixes to 4 BGP neighbours. AS58563 has a reputation score of 15.9 (NEUTRAL); 39 of its 160,512 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 210
- BGP neighbours
- 4
- RPKI ROAs
- 206
- MOAS conflicts
- 0
- CAIDA AS-rank
- 5,005
- Customer-cone ASNs
- 4
- Facilities
- 0
- Internet exchanges
- 0
- Customer degree
- 3
- Peer degree
- 0
- Provider degree
- 1
- 27.18.12.0/24
- 27.18.13.0/24
- 27.19.220.0/22
- 27.19.248.0/21
- 58.49.144.0/21
- 58.49.152.0/22
- 58.49.157.0/24
- 58.49.156.0/22
- 58.49.160.0/22
- 58.49.184.0/21
- 58.49.192.0/22
- 58.49.196.0/22
- 58.49.212.0/22
- 58.49.216.0/22
- 58.49.220.0/22
- 58.49.224.0/21
- 58.49.232.0/22
- 58.49.236.0/22
- 58.49.240.0/22
- 58.49.244.0/22
- 58.49.248.0/22
- 58.49.252.0/22
- 61.183.164.0/22
- 111.172.0.0/24
- 111.172.208.0/22
Route origin authorizations
A sample of 10 of this network’s 206 ROAs.
- 103.163.180.0/24 · max length /32
- 111.172.0.0/24 · max length /24
- 111.172.208.0/22 · max length /22
- 116.211.112.0/20 · max length /20
- 116.211.128.0/22 · max length /22
- 116.211.132.0/22 · max length /22
- 116.211.136.0/22 · max length /22
- 116.211.140.0/22 · max length /22
- 116.211.144.0/21 · max length /21
- 116.211.152.0/21 · max length /21
Upstreams
The networks that most often share an observed BGP path with AS58563.
Blast radius
- Announced IPv4 addresses
- 160,512
- Threat-listed addresses
- 39
- Threat density
- 0.0243 %
- Routed prefixes
- 177
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 4 of this network’s 4 BGP neighbours.
Reputation
15.9reputation score (NEUTRAL)
AS58563 (CHINATELECOM-Hubei-IDC - CHINANET Hubei province network, CN) has a reputation score of 58.2 (NEUTRAL).
- Threat density
- 75.5/100
- Graph metrics
- 30.0/100
- Historical behaviour
- 85.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- CHINANET Hubei province network
- RIR
- APNIC
- Registered
- Fri, 23 Mar 2012 04:54:30 GMT
- Abuse contact
- anti-spam@chinatelecom.cn
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS58563 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.