Observed topology
AS60159 EUROLINE-NET EUROLINE UKRAINE LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS60159: 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 |
|---|---|---|---|---|
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 174 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 51 |
| AS15830 | Equinix (EMEA) Acquisition Enterprises B.V. | Hosting | IPv4 | 21 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 5 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 4 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS60159 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56899 | Granat Ukraine LLC | Unclassified | IPv4 | 90 |
| AS204384 | LLC "OTT UKRAINE" | Hosting | IPv4 | 67 |
| AS202538 | Private Enterprise TRK "ATV-PLUS" | Unclassified | IPv4 | 36 |
| AS44921 | FOP A.L. Kryuchkov | Unclassified | IPv4 | 29 |
| AS44294 | Lopatin Arkadiy Borisovich | Unclassified | IPv4 | 23 |
| AS212375 | PJSC Kyiv Vitamin Plant | Unclassified | IPv4 | 21 |
| AS212048 | Monchulyak Serhiy | Unclassified | IPv4 | 20 |
| AS51993 | LLC Telekompaniya Region | Residential | IPv4 | 14 |
| AS35588 | Telecompany LiS LTD | Unclassified | IPv4 | 5 |
| AS35362 | LIMITED LIABILITY COMPANY "BEST SOLUTIONS" | Residential | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS60159 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15830 | Equinix (EMEA) Acquisition Enterprises B.V. | Hosting | IPv4 IPv6 | 1,147 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 1,036 |
| AS56899 | Granat Ukraine LLC | Unclassified | IPv4 | 175 |
| AS204384 | LLC "OTT UKRAINE" | Hosting | IPv4 | 67 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 57 |
| AS44294 | Lopatin Arkadiy Borisovich | Unclassified | IPv4 | 47 |
| AS202538 | Private Enterprise TRK "ATV-PLUS" | Unclassified | IPv4 | 36 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 33 |
| AS44921 | FOP A.L. Kryuchkov | Unclassified | IPv4 | 29 |
| AS212375 | PJSC Kyiv Vitamin Plant | Unclassified | IPv4 | 21 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.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.