asn.dev

Observed topology

AS13739 DATACENTER-IP

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13739: 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 IPv6789
AS174Cogent Communications, LLCTransitIPv4462

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400690KSB Industries, LLCUnclassifiedIPv4928
AS14569Intellipop, LLCUnclassifiedIPv4522
AS396191Echo Broadband, IncUnclassifiedIPv4232
AS55011eFolder, IncUnclassifiedIPv4120
AS36025WickedFastInternet.comUnclassifiedIPv4116
AS12284Computer Solutions / CSolutionsUnclassifiedIPv4 IPv692
AS53845Broadband Dynamics, LLCUnclassifiedIPv485

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv62,136
AS174Cogent Communications, LLCTransitIPv41,214
AS400690KSB Industries, LLCUnclassifiedIPv4928
AS14569Intellipop, LLCUnclassifiedIPv4522
AS396191Echo Broadband, IncUnclassifiedIPv4232
AS55011eFolder, IncUnclassifiedIPv4124
AS36025WickedFastInternet.comUnclassifiedIPv4116
AS12284Computer Solutions / CSolutionsUnclassifiedIPv4 IPv692
AS53845Broadband Dynamics, LLCUnclassifiedIPv485

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.