Observed topology
AS34170 AS-AZTELEKOM Aztelekom LLC
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS34170: 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 |
|---|---|---|---|---|
| AS196925 | Azertelecom LLC | Unclassified | IPv4 | 910 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 325 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 251 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 192 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 68 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 57 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 52 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 34 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 33 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 33 |
Transit
Downstream networks
Networks for which AS34170 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15723 | "AZERONLINE LTD" JOINT ENTERPRISE | Unclassified | IPv4 | 3,536 |
| AS31721 | Azercell Telecom Ltd | Unclassified | IPv4 | 3,179 |
| AS8814 | Aztelekom LLC | Unclassified | IPv4 | 2,579 |
| AS28787 | Aztelekom LLC | Unclassified | IPv4 | 1,556 |
| AS199524 | G-Core Labs S.A. | Hosting | IPv4 IPv6 | 216 |
| AS13099 | "AZ-EVRO TEL" LLC | Unclassified | IPv4 | 120 |
| AS200729 | AzInTelecom LLC | Unclassified | IPv4 | 94 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 91 |
| AS138915 | Kaopu Cloud HK Limited | Hosting | IPv4 IPv6 | 56 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34170 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15723 | "AZERONLINE LTD" JOINT ENTERPRISE | Unclassified | IPv4 | 3,536 |
| AS31721 | Azercell Telecom Ltd | Unclassified | IPv4 | 3,179 |
| AS196925 | Azertelecom LLC | Unclassified | IPv4 IPv6 | 2,774 |
| AS8814 | Aztelekom LLC | Unclassified | IPv4 | 2,579 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 2,453 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,415 |
| AS28787 | Aztelekom LLC | Unclassified | IPv4 | 2,019 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,840 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 1,210 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 387 |
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.