Skip to content

Autonomous System

AS19239 — KLA - KLA Corporation(US)

Last fetched

AS19239 is an Autonomous System operated by KLA - KLA Corporation and registered in US. As of Thu, 13 Aug 2026 23:53:17 GMT, it announces 15 routed IP prefixes and peers with 14 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS19239Routing diversity6.0/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/19239

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS12129123NET - 123.Net, Inc.US
AS12400PARTNER-AS - Partner Communications Ltd.IL
AS2687ATGS-MMD-AS - AT&T Enterprises, LLCUS
AS2856BT-UK-AS - British Telecommunications LimitedGB
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS3491PCCWG-APAC-HK - PCCW Global (HK) Ltd.HK
AS45820TTSL-MEISISP - Tata Teleservices ISP ASIN
AS4755TATACOMM-AS - TATA Communications formerly VSNL is Leading ISPIN
AS5089NTL - Virgin Media LimitedGB
AS55410VIL-AS-AP - Vodafone Idea LtdIN
AS7018ATT-INTERNET4 - AT&T Enterprises, LLCUS
AS8220COLT - COLT Technology Services Group LimitedGB
AS8551BEZEQ-INTERNATIONAL-AS - Bezeq International Ltd.IL
AS9498BBIL-AP - BHARTI Airtel Ltd.IN

Blast radius

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

171 hostnames depend on this network.Exact count across all 15 announced prefixes. Snapshot Sun, 14 Jun 2026 00:00:32 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS19239.

Cypher and MCP

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

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