asn.dev

Observed topology

AS39529 MTRX-ALCHEVSK-AS

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39529: 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
AS201776Miranda-Media LtdUnclassifiedIPv4342
AS39728Likhno Dmitriy trading as LuganetUnclassifiedIPv4180
AS24482SG.GSHostingIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS49673Truenetwork LLCUnclassifiedIPv49
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214702Net Line LLCUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS201776Miranda-Media LtdUnclassifiedIPv4352
AS39728Likhno Dmitriy trading as LuganetUnclassifiedIPv4188
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv410
AS24482SG.GSHostingIPv49
AS49673Truenetwork LLCUnclassifiedIPv49
AS214702Net Line LLCUnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv41

Provenance

Where this comes from

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