asn.dev

Observed topology

AS201053 Stowarzyszenie e-Poludnie

Unclassified RIPE

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv622
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv612

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv63,687
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv61,551
AS47232ISP Alliance a.s.ResidentialIPv4750
AS29504Freenet Liberec, z.s.UnclassifiedIPv4581
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv6533
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6370
AS37100SEACOM LimitedUnclassifiedIPv4328
AS212261Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv6280
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6206
AS212024Marc SchmittUnclassifiedIPv4 IPv6131

All 28 adjacent →

Provenance

Where this comes from

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