asn.dev

Observed topology

AS53808 MOEDOVE-N2 - MoeDove

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53808: 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
AS30058FDCservers.netUnclassifiedIPv4 IPv6396
AS44324MoeDove LLCResidentialIPv4 IPv6240
AS26042FiberState, LLCHostingIPv4 IPv6164
AS51847Nearoute LimitedHostingIPv4 IPv694
AS204044Packet Star Networks LimitedUnclassifiedIPv4 IPv690

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214731ETO Networks LimitedUnclassifiedIPv6166
AS62246WJY LimitedResidentialIPv445
AS26682ByteNya LLCUnclassifiedIPv632
AS214963Puhe YouUnclassifiedIPv632
AS202335Zhanrui TianUnclassifiedIPv626

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30058FDCservers.netUnclassifiedIPv4 IPv6727
AS44324MoeDove LLCResidentialIPv4 IPv6270
AS214731ETO Networks LimitedUnclassifiedIPv6166
AS26042FiberState, LLCHostingIPv4 IPv6164
AS51847Nearoute LimitedHostingIPv4 IPv694
AS204044Packet Star Networks LimitedUnclassifiedIPv4 IPv690
AS62246WJY LimitedResidentialIPv445
AS26682ByteNya LLCUnclassifiedIPv632
AS214963Puhe YouUnclassifiedIPv632
AS202335Zhanrui TianUnclassifiedIPv626

Provenance

Where this comes from

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