Observed topology
AS59589 KA2
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS59589: 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 |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 75 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 34 |
| AS20764 | CJSC RASCOM | Unclassified | IPv6 | 29 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 12 |
| AS1299 | Arelion Sweden AB | Transit | IPv6 | 4 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 2 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 2 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 2 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS59589 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57918 | ACOD JSC | Unclassified | IPv4 | 305 |
| AS49779 | Joint-Stock Company Investpribor | Unclassified | IPv4 IPv6 | 159 |
| AS39604 | Non-public corporation MASARMAT | Unclassified | IPv4 | 120 |
| AS29304 | JSC SATIS-TL-94 | Unclassified | IPv4 | 68 |
| AS34211 | Lanport-S LLC | Unclassified | IPv4 | 63 |
| AS201298 | LLC "MIKROTEK" | Unclassified | IPv4 | 63 |
| AS9039 | Institute of information & analytical technologies IIAT, Limited | Unclassified | IPv4 | 34 |
| AS39125 | KB Rubin Ltd. | Unclassified | IPv4 | 20 |
| AS15757 | Joint Stock Company Gazprom Space Systems | Unclassified | IPv4 | 18 |
Adjacency
Adjacent networks
Every AS seen directly next to AS59589 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 330 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 316 |
| AS57918 | ACOD JSC | Unclassified | IPv4 | 305 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 212 |
| AS49779 | Joint-Stock Company Investpribor | Unclassified | IPv4 IPv6 | 159 |
| AS39604 | Non-public corporation MASARMAT | Unclassified | IPv4 | 120 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 94 |
| AS39125 | KB Rubin Ltd. | Unclassified | IPv4 | 82 |
| AS29304 | JSC SATIS-TL-94 | Unclassified | IPv4 | 68 |
| AS34211 | Lanport-S LLC | Unclassified | IPv4 | 63 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.