asn.dev

Observed topology

AS10780 PURE-STORAGE

Unclassified ARIN

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS10780: 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
AS6461Zayo BandwidthTransitIPv4 IPv6225
AS3356Level 3 Parent, LLCTransitIPv4200
AS8220COLT Technology Services Group LimitedHostingIPv4174
AS9498BHARTI Airtel Ltd.MobileIPv491
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv458
AS10021KVH Co.,LtdUnclassifiedIPv456
AS5400British Telecommunications LimitedUnclassifiedIPv452
AS6855Slovak Telekom, a.s.MobileIPv452
AS7018AT&T Enterprises, LLCResidentialIPv447
AS6830Liberty Global Europe Holding B.V.ResidentialIPv443

All 20 upstreams →

Transit

Downstream networks

inferred

Networks for which AS10780 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 20

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6225
AS3356Level 3 Parent, LLCTransitIPv4200
AS8220COLT Technology Services Group LimitedHostingIPv4174
AS9498BHARTI Airtel Ltd.MobileIPv491
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv458
AS10021KVH Co.,LtdUnclassifiedIPv456
AS5400British Telecommunications LimitedUnclassifiedIPv452
AS6855Slovak Telekom, a.s.MobileIPv452
AS7018AT&T Enterprises, LLCResidentialIPv447
AS6830Liberty Global Europe Holding B.V.ResidentialIPv443

All 20 adjacent →

Provenance

Where this comes from

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