asn.dev

Observed topology

AS40929 MOEDOVE-BN

Hosting ARIN

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS40929: 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
AS20473The Constant Company, LLCHostingIPv4 IPv61,311
AS17433Hytron Network Services LimitedResidentialIPv4 IPv6337
AS216211CYBERVERSE LLCHostingIPv4 IPv6241
AS27523Kawaii Networks LLCUnclassifiedIPv6237
AS137409GSL Networks Pty LTDUnclassifiedIPv6201
AS34927iFog GmbHHostingIPv4 IPv6153
AS44324MoeDove LLCResidentialIPv6122
AS955LSHIY LLCUnclassifiedIPv4 IPv680
AS53667FranTech SolutionsHostingIPv677
AS202335Zhanrui TianUnclassifiedIPv677

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203236Mingyang ShenUnclassifiedIPv4 IPv6187
AS202335Zhanrui TianUnclassifiedIPv633

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv4 IPv61,311
AS17433Hytron Network Services LimitedResidentialIPv4 IPv6401
AS216211CYBERVERSE LLCHostingIPv4 IPv6299
AS27523Kawaii Networks LLCUnclassifiedIPv6237
AS34927iFog GmbHHostingIPv4 IPv6210
AS137409GSL Networks Pty LTDUnclassifiedIPv6201
AS203236Mingyang ShenUnclassifiedIPv4 IPv6187
AS202335Zhanrui TianUnclassifiedIPv6131
AS44324MoeDove LLCResidentialIPv6129
AS955LSHIY LLCUnclassifiedIPv4 IPv6106

All 16 adjacent →

Provenance

Where this comes from

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