Observed topology
AS44894 UCMA-AS Ukrchermetavtomatika LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS44894: 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 |
|---|---|---|---|---|
| AS199995 | Omega Telecom LLC | Residential | IPv4 IPv6 | 1,234 |
| AS1820 | WNET TELECOM USA Corp. | Residential | IPv4 | 454 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 310 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 73 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 69 |
| AS24482 | SG.GS | Hosting | IPv4 | 28 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 | 19 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 | 8 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS44894 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211621 | West-TV LLC | Unclassified | IPv4 | 335 |
| AS213009 | Department of Information Technology of the Dnipro City Council | Unclassified | IPv4 | 54 |
| AS62146 | OPTI Scientific Production Enterprise Ltd | Unclassified | IPv4 | 48 |
| AS56459 | PE Golub Iryna Anatoliivna | Unclassified | IPv4 | 38 |
| AS203716 | FOP Kushnarev Sergii Mikolayevich | Unclassified | IPv4 | 31 |
| AS58099 | GUM Limited Liability Company | Unclassified | IPv4 | 23 |
| AS199440 | "ATB-market" LLC | Unclassified | IPv4 | 16 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44894 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199995 | Omega Telecom LLC | Residential | IPv4 IPv6 | 1,301 |
| AS1820 | WNET TELECOM USA Corp. | Residential | IPv4 | 621 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 601 |
| AS211621 | West-TV LLC | Unclassified | IPv4 | 335 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 82 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 73 |
| AS213009 | Department of Information Technology of the Dnipro City Council | Unclassified | IPv4 | 54 |
| AS62146 | OPTI Scientific Production Enterprise Ltd | Unclassified | IPv4 | 48 |
| AS56459 | PE Golub Iryna Anatoliivna | Unclassified | IPv4 | 38 |
| AS24482 | SG.GS | Hosting | IPv4 | 35 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.