asn.dev

Observed topology

AS19239 KLA - KLA Corporation

Unclassified ARIN

Upstreams 14 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 0
Upstream graph Who carries AS19239, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS19239 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS19239: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4171
AS2687AT&T Enterprises, LLCUnclassifiedIPv4123
AS12129123.Net, Inc.HostingIPv4122
AS8220COLT Technology Services Group LimitedHostingIPv4116
AS9498BHARTI Airtel Ltd.MobileIPv4102
AS3491PCCW Global (HK) Ltd.TransitIPv453
AS8551Bezeq International Ltd.UnclassifiedIPv451
AS55410Vodafone Idea LtdMobileIPv440
AS2856British Telecommunications LimitedResidentialIPv438
AS5089Virgin Media LimitedResidentialIPv422

Transit

Downstream networks

inferred

Networks for which AS19239 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 14

Every AS seen directly next to AS19239 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4171
AS2687AT&T Enterprises, LLCUnclassifiedIPv4123
AS12129123.Net, Inc.HostingIPv4122
AS8220COLT Technology Services Group LimitedHostingIPv4116
AS9498BHARTI Airtel Ltd.MobileIPv4102
AS3491PCCW Global (HK) Ltd.TransitIPv453
AS8551Bezeq International Ltd.UnclassifiedIPv451
AS55410Vodafone Idea LtdMobileIPv440
AS2856British Telecommunications LimitedResidentialIPv438
AS5089Virgin Media LimitedResidentialIPv422

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.