Observed topology
AS42739 FONE-ASN Hawe Telekom S.A.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS42739: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 152 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 106 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 102 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 86 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 66 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 53 |
| AS5511 | Orange S.A. | Transit | IPv4 | 24 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 22 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 17 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
Transit
Downstream networks
Networks for which AS42739 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47544 | IQ PL Sp. z o.o. | Hosting | IPv4 IPv6 | 543 |
| AS50840 | Marek Bajerski trading as HITME.PL | Unclassified | IPv4 IPv6 | 466 |
| AS197226 | "SPRINT" S.A. | Hosting | IPv4 IPv6 | 430 |
| AS197615 | NaszaSiec.NET Krakow Damian Murzynowski | Residential | IPv4 | 312 |
| AS35745 | Provector Sp. z o.o | Unclassified | IPv4 IPv6 | 305 |
| AS199234 | Komputerowe Studio Grafiki, Wojciech Lis | Unclassified | IPv4 IPv6 | 246 |
| AS203828 | DSS OPERATOR SPOLKA AKCYJNA | Unclassified | IPv4 | 196 |
| AS41385 | KONIN-MIASTO NA PRAWACH POWIATU | Unclassified | IPv4 | 183 |
| AS204782 | MARCIN SEBASTIAN ZIOLEK trading as MATCOM | Unclassified | IPv4 | 183 |
| AS20592 | Wojewodztwo Swietokrzyskie | Unclassified | IPv4 | 153 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42739 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,306 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 661 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 620 |
| AS47544 | IQ PL Sp. z o.o. | Hosting | IPv4 IPv6 | 610 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 500 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 468 |
| AS50840 | Marek Bajerski trading as HITME.PL | Unclassified | IPv4 IPv6 | 466 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 436 |
| AS197226 | "SPRINT" S.A. | Hosting | IPv4 IPv6 | 430 |
| AS35745 | Provector Sp. z o.o | Unclassified | IPv4 IPv6 | 411 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.