asn.dev

Observed topology

AS39134 UNITEDNET EDINAYA SET LIMITED LIABILITY COMPANY

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39134: 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
AS50340JSC SelectelHostingIPv4 IPv63,366
AS12389PJSC RostelecomResidentialIPv4192
AS6939Hurricane Electric LLCTransitIPv430
AS59692IQWeb FZ-LLCUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv610
AS49673Truenetwork LLCUnclassifiedIPv49
AS57724DDOS-GUARD LTDUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197695"Domain names registrar REG.RU", LtdHostingIPv4 IPv6295
AS49352"Domain names registrar REG.RU", LtdUnclassifiedIPv438

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50340JSC SelectelHostingIPv4 IPv63,737
AS197695"Domain names registrar REG.RU", LtdHostingIPv4 IPv6295
AS12389PJSC RostelecomResidentialIPv4192
AS39561"Domain names registrar REG.RU", LtdUnclassifiedIPv4 IPv638
AS49352"Domain names registrar REG.RU", LtdUnclassifiedIPv438
AS6939Hurricane Electric LLCTransitIPv430
AS59692IQWeb FZ-LLCUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv610
AS49673Truenetwork LLCUnclassifiedIPv49
AS57724DDOS-GUARD LTDUnclassifiedIPv42

Provenance

Where this comes from

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