Observed topology

AS43171 MAXNET Lukasz Hamerski

Residential RIPE

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.

AS	Network	Type	Families	Paths seen
AS62081	Stowarzyszenie e-Poludnie	Unclassified	IPv4	266
AS9141	P4 Sp. z o.o.	Mobile	IPv4	100
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	15
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4	10
AS24482	SG.GS	Hosting	IPv4	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS202962	ok360 Sp. z o.o.	Unclassified	IPv4	66
AS215204	PCC INTERMODAL SPOLKA AKCYJNA	Unclassified	IPv4	28
AS197848	NETPOL Piotr Pruba	Unclassified	IPv4	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS62081	Stowarzyszenie e-Poludnie	Unclassified	IPv4	368
AS9141	P4 Sp. z o.o.	Mobile	IPv4	128
AS202962	ok360 Sp. z o.o.	Unclassified	IPv4	66
AS5550	Technical University of Gdansk, Academic Computer Center TASK	Education	IPv4	35
AS215204	PCC INTERMODAL SPOLKA AKCYJNA	Unclassified	IPv4	28
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	17
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4	12
AS24482	SG.GS	Hosting	IPv4	6
AS197848	NETPOL Piotr Pruba	Unclassified	IPv4	6

Provenance

Where this comes from

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