Observed topology
AS50606 VIRTUAOPERATOR-AS Horyzont Technologie Internetowe sp.z.o.o.
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS50606: 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 | 675 |
| AS29314 | VECTRA S.A. | Residential | IPv4 | 363 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 349 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 205 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 90 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 29 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 28 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS201054 | Stowarzyszenie e-Poludnie | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS50606 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201725 | Firma Tonetic Krzysztof Adamczyk | Unclassified | IPv4 | 276 |
| AS44784 | Piotr Szajkowski trading as APCOM POLAND | Unclassified | IPv4 | 258 |
| AS57478 | DAR.NET Sp. z o.o. | Residential | IPv4 | 242 |
| AS198277 | Grzegorz Maszczyk trading as MAG FIRMA HANDLOWA | Unclassified | IPv4 | 188 |
| AS60534 | Laguna sp. z o.o. | Unclassified | IPv4 IPv6 | 136 |
| AS201514 | KASPOL.NET Sp. z o.o. | Residential | IPv4 | 116 |
| AS49528 | MARCIN MALOLEPSZY @ALFANET | Unclassified | IPv4 | 89 |
| AS21111 | Ministerstwo Rozwoju i Technologii | Unclassified | IPv4 | 77 |
| AS215437 | SummerHosting sp. z o. o. | Unclassified | IPv6 | 68 |
| AS199390 | Michal Swierk trading as ALFA-KOMPUTER SYSTEM | Residential | IPv4 | 63 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50606 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,305 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 975 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 898 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 407 |
| AS29314 | VECTRA S.A. | Residential | IPv4 | 371 |
| AS201725 | Firma Tonetic Krzysztof Adamczyk | Unclassified | IPv4 | 276 |
| AS44784 | Piotr Szajkowski trading as APCOM POLAND | Unclassified | IPv4 | 258 |
| AS57478 | DAR.NET Sp. z o.o. | Residential | IPv4 | 242 |
| AS198277 | Grzegorz Maszczyk trading as MAG FIRMA HANDLOWA | Unclassified | IPv4 | 188 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 146 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.