Observed topology
AS39089 UGLETELECOM-AS STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM"
Unclassified RIPE
Transit
Upstream networks
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.
Transit
Downstream networks
Networks for which AS39089 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS39089 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 719 |
| AS206810 | GUP DNR "UGLETELECOM" | Unclassified | IPv4 | 368 |
| AS202279 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "REPUBLICAN TELECOMMUNICATIONS OPERATOR" | Unclassified | IPv4 | 316 |
| AS12773 | Meshnet ltd. | Unclassified | IPv4 | 244 |
| AS44539 | Redi LLC | Unclassified | IPv4 | 172 |
| AS48084 | Uzhnie Magistraljnie Linii Svyazi LLC | Unclassified | IPv4 | 112 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 67 |
| AS20590 | Donbass Electronic Communications Ltd. | Unclassified | IPv4 | 57 |
| AS24482 | SG.GS | Hosting | IPv4 | 11 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
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.