asn.dev

Observed topology

AS39089 UGLETELECOM-AS STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39089: 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
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4368
AS12389PJSC RostelecomResidentialIPv4126

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202279STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "REPUBLICAN TELECOMMUNICATIONS OPERATOR"UnclassifiedIPv4316
AS12773Meshnet ltd.UnclassifiedIPv4157
AS20590Donbass Electronic Communications Ltd.UnclassifiedIPv457
AS44539Redi LLCUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4719
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4368
AS202279STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "REPUBLICAN TELECOMMUNICATIONS OPERATOR"UnclassifiedIPv4316
AS12773Meshnet ltd.UnclassifiedIPv4244
AS44539Redi LLCUnclassifiedIPv4172
AS48084Uzhnie Magistraljnie Linii Svyazi LLCUnclassifiedIPv4112
AS6939Hurricane Electric LLCTransitIPv467
AS20590Donbass Electronic Communications Ltd.UnclassifiedIPv457
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv46

Provenance

Where this comes from

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