asn.dev

Observed topology

AS32590 VALVE-CORPORATION

Hosting ARIN Content

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

Transit

Upstream networks

All 74

Networks observed carrying traffic for AS32590: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,138
AS1299Arelion Sweden ABTransitIPv4 IPv6612
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6258
AS174Cogent Communications, LLCTransitIPv4 IPv6253
AS2914NTT America, Inc.TransitIPv4 IPv6213
AS21859Zenlayer IncHostingIPv4 IPv6194
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6151
AS3257GTT Communications Inc.TransitIPv4 IPv6145
AS4637Telstra GlobalUnclassifiedIPv4 IPv696
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv683

All 74 upstreams →

Transit

Downstream networks

inferred

Networks for which AS32590 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 74

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,138
AS1299Arelion Sweden ABTransitIPv4 IPv6612
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6258
AS174Cogent Communications, LLCTransitIPv4 IPv6253
AS2914NTT America, Inc.TransitIPv4 IPv6213
AS21859Zenlayer IncHostingIPv4 IPv6194
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6151
AS3257GTT Communications Inc.TransitIPv4 IPv6145
AS4637Telstra GlobalUnclassifiedIPv4 IPv696
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv683

All 74 adjacent →

Provenance

Where this comes from

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