asn.dev

Observed topology

AS29944 DATABANK-LATISYS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29944: 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 IPv6557
AS13767DataBank Holdings, Ltd.HostingIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14292CSRA Consular Services Inc.UnclassifiedIPv4177
AS23008NORCUnclassifiedIPv4 IPv692
AS12171Fast Enterprises, LLCUnclassifiedIPv459
AS54954INFOSTRUCTURES, INC.UnclassifiedIPv459
AS54391Crutchfield New Media LLCUnclassifiedIPv4 IPv644

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,008
AS14292CSRA Consular Services Inc.UnclassifiedIPv4177
AS13767DataBank Holdings, Ltd.HostingIPv4 IPv6169
AS23008NORCUnclassifiedIPv4 IPv692
AS12171Fast Enterprises, LLCUnclassifiedIPv459
AS54954INFOSTRUCTURES, INC.UnclassifiedIPv459
AS54391Crutchfield New Media LLCUnclassifiedIPv4 IPv644

Provenance

Where this comes from

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