asn.dev

Observed topology

AS39684 MANGO-TELECOM-AS

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS39684: 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
AS197068HLL LLCHostingIPv4236
AS12389PJSC RostelecomResidentialIPv4164
AS3216PJSC "Vimpelcom"MobileIPv495
AS20485Joint Stock Company TransTeleComUnclassifiedIPv464
AS20764CJSC RASCOMUnclassifiedIPv448
AS57304JSC "RetnNet"UnclassifiedIPv430
AS29226JSC MastertelUnclassifiedIPv424
AS6939Hurricane Electric LLCTransitIPv414
AS3175Citytelecom LLCHostingIPv412
AS1299Arelion Sweden ABTransitIPv410

All 17 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS197068HLL LLCHostingIPv4236
AS12389PJSC RostelecomResidentialIPv4164
AS3216PJSC "Vimpelcom"MobileIPv495
AS20485Joint Stock Company TransTeleComUnclassifiedIPv464
AS20764CJSC RASCOMUnclassifiedIPv448
AS57304JSC "RetnNet"UnclassifiedIPv430
AS29226JSC MastertelUnclassifiedIPv424
AS6939Hurricane Electric LLCTransitIPv414
AS3175Citytelecom LLCHostingIPv412
AS1299Arelion Sweden ABTransitIPv410

All 17 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.