Observed topology
AS197091 METROPORT
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS197091: 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 | 117 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 37 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 24 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 6 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 | 4 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1 |
| AS24115 | Equinix | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS197091 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56544 | MARLENA Marek Zieba | Unclassified | IPv4 | 87 |
| AS41266 | "NET-PARTNER" S.C. IZABELA KOZLOWSKA, TOMASZ KOZLOWSKI | Unclassified | IPv4 | 60 |
| AS51757 | Infratel-Operator Infrastrukturalny sp. z o.o. | Unclassified | IPv4 | 60 |
| AS51079 | P.H.U. MOKADI Wieslawa Kazmierczak | Unclassified | IPv4 | 52 |
| AS33951 | "FORWEB" S.C. Monika Bodetko, Tomasz Pawlowski | Residential | IPv4 | 45 |
| AS201091 | ETH Sieci Komputerowe Sp. z o.o. | Unclassified | IPv4 | 34 |
| AS203157 | Lukasz Kazimierczak Cronel | Unclassified | IPv4 | 22 |
| AS56869 | MPCNET SP. Z O.O. | Unclassified | IPv4 | 18 |
| AS50349 | Timplus sp. z o.o. | Unclassified | IPv4 | 11 |
| AS50239 | SOFTNET TELEKOM BIELINSKA sp.j. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS197091 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 385 |
| AS56544 | MARLENA Marek Zieba | Unclassified | IPv4 | 87 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 71 |
| AS41266 | "NET-PARTNER" S.C. IZABELA KOZLOWSKA, TOMASZ KOZLOWSKI | Unclassified | IPv4 | 60 |
| AS51757 | Infratel-Operator Infrastrukturalny sp. z o.o. | Unclassified | IPv4 | 60 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 57 |
| AS51079 | P.H.U. MOKADI Wieslawa Kazmierczak | Unclassified | IPv4 | 52 |
| AS33951 | "FORWEB" S.C. Monika Bodetko, Tomasz Pawlowski | Residential | IPv4 | 49 |
| AS201091 | ETH Sieci Komputerowe Sp. z o.o. | Unclassified | IPv4 | 34 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 32 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.