Observed topology

AS205671 MAINPL MAIN Sp. z o.o.

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS205671, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS205671 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205671: 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
AS12741	Netia SA	Residential	IPv4 IPv6	199
AS9141	P4 Sp. z o.o.	Mobile	IPv4	68
AS6939	Hurricane Electric LLC	Transit	IPv4	35
AS20853	eTOP sp. z o.o.	Unclassified	IPv4	22
AS24482	SG.GS	Hosting	IPv4 IPv6	6
AS29632	Netassist International EOOD	Unclassified	IPv6	1
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS44415	GlobTel GmbH	Unclassified	IPv4	118

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12741	Netia SA	Residential	IPv4 IPv6	262
AS44415	GlobTel GmbH	Unclassified	IPv4	118
AS9141	P4 Sp. z o.o.	Mobile	IPv4	80
AS20853	eTOP sp. z o.o.	Unclassified	IPv4	51
AS6939	Hurricane Electric LLC	Transit	IPv4	47
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS29632	Netassist International EOOD	Unclassified	IPv6	1
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	1

Provenance

Where this comes from

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