asn.dev

Observed topology

AS43171 MAXNET Lukasz Rafal Hamerski trading as Maxnet

Residential RIPE Cable/DSL/ISP

Upstreams 5 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 0
Upstream graph Who carries AS43171, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS43171 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43171: 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.

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4278
AS9141P4 Sp. z o.o.MobileIPv4100
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv410
AS24482SG.GSHostingIPv45
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv43

Transit

Downstream networks

inferred

Networks for which AS43171 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS202962ok360 Sp. z o.o.UnclassifiedIPv465
AS215204PCC INTERMODAL SPOLKA AKCYJNAUnclassifiedIPv427
AS197848NETPOL Piotr PrubaUnclassifiedIPv44

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS43171 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4380
AS9141P4 Sp. z o.o.MobileIPv4126
AS202962ok360 Sp. z o.o.UnclassifiedIPv465
AS5550Technical University of Gdansk, Academic Computer Center TASKEducationIPv435
AS215204PCC INTERMODAL SPOLKA AKCYJNAUnclassifiedIPv427
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS197848NETPOL Piotr PrubaUnclassifiedIPv44
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv43

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.