asn.dev

Observed topology

AS53292 MWAY

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53292: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,573
AS27589MOJOHOSTHostingIPv4 IPv6330
AS6939Hurricane Electric LLCTransitIPv4 IPv6227
AS20473The Constant Company, LLCHostingIPv4118
AS20205Amplex Electric, Inc.ResidentialIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63251Metro Wireless International, Inc.UnclassifiedIPv4684
AS54456CloudAccess.net, LLCUnclassifiedIPv4 IPv6510
AS15324Barracuda Networks, Inc.UnclassifiedIPv4175
AS400101Ringfree Communications, IncUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv62,524
AS63251Metro Wireless International, Inc.UnclassifiedIPv4972
AS27589MOJOHOSTHostingIPv4 IPv6745
AS6939Hurricane Electric LLCTransitIPv4 IPv6569
AS54456CloudAccess.net, LLCUnclassifiedIPv4 IPv6510
AS15324Barracuda Networks, Inc.UnclassifiedIPv4175
AS20473The Constant Company, LLCHostingIPv4118
AS400101Ringfree Communications, IncUnclassifiedIPv458
AS20205Amplex Electric, Inc.ResidentialIPv422

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.