Observed topology
AS202520 SKYPASS-AS SkyPass Solutions Sp. z o.o.
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS202520: 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 |
|---|---|---|---|---|
| AS6204 | ZET Communications S.R.L. | Unclassified | IPv4 IPv6 | 462 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 81 |
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 | 61 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 44 |
| AS35179 | Korbank S. A. | Unclassified | IPv6 | 32 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS5617 | Orange Polska Spolka Akcyjna | Mobile | IPv4 | 10 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 | 10 |
| AS49559 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS202520 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215437 | SummerHosting sp. z o. o. | Unclassified | IPv4 | 123 |
| AS215703 | FREAKHOSTING LTD | Unclassified | IPv4 | 122 |
| AS42763 | FPUH Czajen Krzysztof Czaja | Residential | IPv4 | 103 |
| AS198187 | Studio WIK Sp. z o.o. | Residential | IPv4 | 65 |
| AS206589 | NSIX Data Center sp. z o.o. | Unclassified | IPv4 | 50 |
| AS200750 | Klikom.net Sp.z o.o. | Residential | IPv4 | 43 |
| AS198317 | Uslugowa KOMPEX Gabriel Sulka | Residential | IPv4 | 41 |
| AS198857 | NOWOGROD.NET SP. Z O.O. | Residential | IPv4 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS202520 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6204 | ZET Communications S.R.L. | Unclassified | IPv4 IPv6 | 774 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 176 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 133 |
| AS215437 | SummerHosting sp. z o. o. | Unclassified | IPv4 | 123 |
| AS215703 | FREAKHOSTING LTD | Unclassified | IPv4 | 122 |
| AS42763 | FPUH Czajen Krzysztof Czaja | Residential | IPv4 | 103 |
| AS62403 | PletX GmbH | Unclassified | IPv4 | 68 |
| AS198187 | Studio WIK Sp. z o.o. | Residential | IPv4 | 65 |
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 | 61 |
| AS206589 | NSIX Data Center sp. z o.o. | Unclassified | IPv4 | 50 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.