Skip to content

Autonomous System

AS4760 — HKTIMS-AP HKT Limited(HK)

Last fetched

AS4760 is an Autonomous System operated by HKTIMS-AP HKT Limited and registered in HK. As of Thu, 21 May 2026 16:31:10 GMT, it announces 680 routed IP prefixes and peers with 15 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

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

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS2914NTT-DATA-2914 - NTT America, Inc.US
AS137409GSLNETWORKS-AS-AP GSL Networks Pty LTDAU
AS135146PCCW-BIA-HK PCCW IMS Ltd PCCW Business Internet AccessHK
AS38819HKCSL-AS-AP HKCSL GPRS NETWORKHK
AS24482SGGS-AS-AP SG.GSSG
AS20940AKAMAI-ASN1NL
AS13335CLOUDFLARENET - Cloudflare, Inc.US
AS10111ZEONET-AS-AP Zeofast NetworkCN
AS9304HUTCHISON-AS-AP HGC Global Communications LimitedHK
AS8966ETISALAT-AS P.O. Box 1150, Dubai, UAE
AS8359MTSRU
AS6939HURRICANE - Hurricane Electric LLCUS
AS4635HKIX-RS1 Hong Kong Internet Exchange--Route Server 1HK
AS4515PCCW-AS-AP PCCW IMS Ltd PCCW Business Internet AccessHK
AS3491PCCWG-APAC-HK PCCW Global HK Ltd.HK

Blast radius

Approximate count of dependent hostnames if AS4760 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 AS4760 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 AS4760 is unique to AS4760 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS4760.

Cypher and MCP

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

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