Observed topology
AS6846 UKRPACK Joint Ukrainan-German Enterprise "INFOCOM" LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6846: 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 | 513 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 IPv6 | 216 |
| AS35297 | Dataline LLC | Unclassified | IPv4 IPv6 | 170 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 87 |
| AS41820 | New Information Systems PP | Unclassified | IPv4 | 36 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 29 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 | 13 |
Transit
Downstream networks
Networks for which AS6846 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8601 | Ltd. Networking Center | Unclassified | IPv4 | 503 |
| AS29436 | Buryanov Konstantin Volodimirovich | Unclassified | IPv4 IPv6 | 348 |
| AS29044 | Ivano-Frankivsk INFOCOM LLC | Unclassified | IPv4 | 195 |
| AS210353 | PJSC NATIONAL POWER COMPANY UKRENERGO (NPC UKRENERGO) | Unclassified | IPv4 | 184 |
| AS56751 | Ministry of Internal Affairs of Ukraine | Unclassified | IPv4 IPv6 | 98 |
| AS47919 | PJSC JSB UkrGasBank | Unclassified | IPv4 | 89 |
| AS16007 | UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" | Unclassified | IPv4 | 78 |
| AS28804 | National University Kievo-Mohylanska Academia | Unclassified | IPv4 | 66 |
| AS48637 | JSC "UKRPOSHTA" | Unclassified | IPv4 | 66 |
| AS49589 | FOP Abashin Andrew Aleksandrovich | Unclassified | IPv4 | 66 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6846 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199995 | Omega Telecom LLC | Residential | IPv4 IPv6 | 1,380 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 IPv6 | 1,065 |
| AS35297 | Dataline LLC | Unclassified | IPv4 IPv6 | 535 |
| AS8601 | Ltd. Networking Center | Unclassified | IPv4 | 503 |
| AS29436 | Buryanov Konstantin Volodimirovich | Unclassified | IPv4 IPv6 | 348 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 263 |
| AS210353 | PJSC NATIONAL POWER COMPANY UKRENERGO (NPC UKRENERGO) | Unclassified | IPv4 | 198 |
| AS29044 | Ivano-Frankivsk INFOCOM LLC | Unclassified | IPv4 | 195 |
| AS198033 | Ministry of finance of Ukraine | Unclassified | IPv4 | 130 |
| AS56751 | Ministry of Internal Affairs of Ukraine | Unclassified | IPv4 IPv6 | 98 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.