Observed topology
AS206810 UGLETELECOM GUP DNR "UGLETELECOM"
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS206810: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52091 | Level-MSK Ltd. | Unclassified | IPv4 | 184 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 162 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 42 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 6 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS206810 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS214721 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "REPUBLICAN TELECOMMUNICATIONS OPERATOR" | Unclassified | IPv4 | 976 |
| AS57164 | Viacheslav Fitiunin | Residential | IPv4 | 857 |
| AS196767 | INMART.UA LLC | Unclassified | IPv4 | 736 |
| AS211101 | Nasteka Maksim Viktorovich | Unclassified | IPv4 | 560 |
| AS196638 | JSC Promtelecom | Unclassified | IPv4 | 533 |
| AS34786 | OOO NPO Intermet | Unclassified | IPv4 | 438 |
| AS202497 | "TRK "Gorodskoe stroitelstvo" LLC | Unclassified | IPv4 | 427 |
| AS39089 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM" | Unclassified | IPv4 | 369 |
| AS48687 | Aleksandr Bobrichenko | Unclassified | IPv4 | 366 |
| AS48595 | IE Parhomenko Aleksey Aleksandrovich | Unclassified | IPv4 | 362 |
Adjacency
Adjacent networks
Every AS seen directly next to AS206810 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS52091 | Level-MSK Ltd. | Unclassified | IPv4 | 5,455 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 2,687 |
| AS214721 | STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "REPUBLICAN TELECOMMUNICATIONS OPERATOR" | Unclassified | IPv4 | 1,342 |
| AS57164 | Viacheslav Fitiunin | Residential | IPv4 | 857 |
| AS196767 | INMART.UA LLC | Unclassified | IPv4 | 736 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 734 |
| AS211692 | Level-Donetsk Ltd. | Unclassified | IPv4 | 669 |
| AS211101 | Nasteka Maksim Viktorovich | Unclassified | IPv4 | 560 |
| AS196638 | JSC Promtelecom | Unclassified | IPv4 | 533 |
| AS34786 | OOO NPO Intermet | Unclassified | IPv4 | 491 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.