asn.dev

Observed topology

AS55064 ARISTAASN1

Unclassified ARIN Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55064: 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
AS13335Cloudflare, Inc.HostingIPv4 IPv6296
AS6461Zayo BandwidthTransitIPv657
AS33651Comcast Cable Communications, LLCUnclassifiedIPv622
AS174Cogent Communications, LLCTransitIPv610
AS33667Comcast Cable Communications, LLCUnclassifiedIPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS53766Arista Networks, Inc.UnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4 IPv6296
AS33651Comcast Cable Communications, LLCUnclassifiedIPv4 IPv683
AS53766Arista Networks, Inc.UnclassifiedIPv461
AS6461Zayo BandwidthTransitIPv657
AS174Cogent Communications, LLCTransitIPv610
AS33667Comcast Cable Communications, LLCUnclassifiedIPv69

Provenance

Where this comes from

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