asn.dev

Observed topology

AS14340 SALESFORCE

Hosting ARIN Content

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS14340: 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, LLCTransitIPv4 IPv6585
AS2914NTT America, Inc.TransitIPv4 IPv6532
AS6939Hurricane Electric LLCTransitIPv4 IPv6368
AS34549meerfarbig GmbH & Co. KGHostingIPv4148
AS577Bell CanadaMobileIPv4 IPv680
AS9002RETN LimitedUnclassifiedIPv4 IPv659
AS33891Core-Backbone GmbHHostingIPv4 IPv645
AS852TELUS Communications Inc.ResidentialIPv4 IPv640
AS6696VERIXI SAUnclassifiedIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv640

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394808Salesforce.com, Inc.UnclassifiedIPv4348
AS22606Salesforce.com, Inc.HostingIPv4300

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6774
AS3356Level 3 Parent, LLCTransitIPv4 IPv6690
AS6939Hurricane Electric LLCTransitIPv4 IPv6469
AS394808Salesforce.com, Inc.UnclassifiedIPv4348
AS22606Salesforce.com, Inc.HostingIPv4300
AS34549meerfarbig GmbH & Co. KGHostingIPv4181
AS577Bell CanadaMobileIPv4 IPv6102
AS9002RETN LimitedUnclassifiedIPv4 IPv659
AS33891Core-Backbone GmbHHostingIPv4 IPv654
AS852TELUS Communications Inc.ResidentialIPv4 IPv651

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.