Observed topology
AS50581 UTG Ukrainian Telecommunication Group LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS50581: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 918 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 721 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 653 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 636 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 557 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 244 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 92 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 92 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 92 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 92 |
Transit
Downstream networks
Networks for which AS50581 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49889 | Crystal Telecom Ltd | Unclassified | IPv4 | 1,800 |
| AS47245 | Network Technology Line LTD | Unclassified | IPv4 | 610 |
| AS196777 | SKORUK ANDRIY OLEKSANDROVYCH | Unclassified | IPv4 IPv6 | 450 |
| AS197554 | ISP RIAD Ltd | Unclassified | IPv4 | 366 |
| AS51742 | FOP Molochko Nina Vasilievna, | Residential | IPv4 | 351 |
| AS43786 | PP NVF Sistema i Tehnika | Unclassified | IPv4 | 300 |
| AS57993 | FOP Khalik Andrey Volodumurovuch | Unclassified | IPv4 | 244 |
| AS51993 | LLC Telekompaniya Region | Residential | IPv4 | 183 |
| AS42441 | CHP Shmatko Sergey Leonidovic | Unclassified | IPv4 IPv6 | 154 |
| AS197144 | PP SVS Stream | Unclassified | IPv4 | 122 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50581 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,047 |
| AS6204 | INTERKVM HOST SRL | Unclassified | IPv4 IPv6 | 2,005 |
| AS49889 | Crystal Telecom Ltd | Unclassified | IPv4 | 1,800 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,520 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,233 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 1,105 |
| AS47245 | Network Technology Line LTD | Unclassified | IPv4 | 610 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 564 |
| AS196777 | SKORUK ANDRIY OLEKSANDROVYCH | Unclassified | IPv4 IPv6 | 511 |
| AS197554 | ISP RIAD Ltd | Unclassified | IPv4 | 366 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.