Observed topology
AS34525 KOBA-AS Polish ISP
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34525: 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 | 237 |
| AS29535 | Orange Polska Spolka Akcyjna | Unclassified | IPv4 | 192 |
| AS20804 | Exatel S.A. | Unclassified | IPv4 | 24 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 17 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS34525 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51436 | IDEALAN Sp. z o.o. | Unclassified | IPv4 | 121 |
| AS198995 | SulikaNET s.c. Tomasz Lewko i Pawel Mojzuk | Unclassified | IPv4 | 120 |
| AS210146 | Dawid Lewandowski | Unclassified | IPv4 IPv6 | 76 |
| AS56597 | FALCONN Falkowski Tomasz | Unclassified | IPv4 | 61 |
| AS50101 | Wnorowski i wspolnicy sp.j | Unclassified | IPv4 IPv6 | 52 |
| AS205677 | SiberSoft, Niegierysz, Plonski sp.j. | Unclassified | IPv4 | 10 |
| AS203677 | HomeNet Technologies Sp. z o.o. | Unclassified | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34525 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 476 |
| AS29535 | Orange Polska Spolka Akcyjna | Unclassified | IPv4 | 216 |
| AS20804 | Exatel S.A. | Unclassified | IPv4 | 135 |
| AS51436 | IDEALAN Sp. z o.o. | Unclassified | IPv4 | 121 |
| AS198995 | SulikaNET s.c. Tomasz Lewko i Pawel Mojzuk | Unclassified | IPv4 | 120 |
| AS210146 | Dawid Lewandowski | Unclassified | IPv4 IPv6 | 76 |
| AS56597 | FALCONN Falkowski Tomasz | Unclassified | IPv4 | 61 |
| AS50101 | Wnorowski i wspolnicy sp.j | Unclassified | IPv4 IPv6 | 52 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 37 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 30 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.