Skip to content

Autonomous System

AS38166 — SCB1-AS-HK-AP - Standard Chartered Bank (Hong Kong) Limited.Banking and(HK)

Last fetched

AS38166 is an Autonomous System operated by SCB1-AS-HK-AP - Standard Chartered Bank (Hong Kong) Limited.Banking and and registered in HK. As of Tue, 04 Aug 2026 03:31:13 GMT, it announces 57 routed IP prefixes and peers with 11 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

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

Routing footprint

AS38166 announces 57 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
AS19551INCAPSULA - Incapsula IncUS
AS24435SUPERNET-PAKISTAN-AS-AP - Supernet Limited Transit Autonomous System NumberPK
AS4755TATACOMM-AS - TATA Communications formerly VSNL is Leading ISPIN
AS4788TTSSB-MY - TM TECHNOLOGY SERVICES SDN. BHD.MY
AS54004LIGHTPATH - Cablevision Lightpath LLCUS
AS5511Opentransit - Orange S.A.FR
AS55410VIL-AS-AP - Vodafone Idea LtdIN
AS6453AS6453 - TATA COMMUNICATIONS (AMERICA) INCUS
AS9498BBIL-AP - BHARTI Airtel Ltd.IN
AS9541CYBERNET-AP - Cyber Internet Services (Pvt) Ltd.PK
AS9583SIFY-AS-IN - Sify LimitedIN

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS38166.

Cypher and MCP

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

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