Observed topology

AS52153 BGCOM Pawel Kowalski BGCOM

Residential RIPE

Upstreams 4 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52153: 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
AS219062	Nera sp z.o.o	Unclassified	IPv4	57
AS9002	RETN Limited	Unclassified	IPv4	6
AS24482	SG.GS	Hosting	IPv4	1
AS212261	Stowarzyszenie e-Poludnie	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS38923	Pawel Kowalski BGCOM	Unclassified	IPv4	319
AS44855	Aptitude Software (Poland) Sp. z o.o.	Unclassified	IPv4	63
AS57875	PORT LOTNICZY WROCLAW SA	Unclassified	IPv4	41
AS31106	Wroclawski Park Technologiczny S.A.	Unclassified	IPv4	25

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS219062	Nera sp z.o.o	Unclassified	IPv4	446
AS38923	Pawel Kowalski BGCOM	Unclassified	IPv4	319
AS44855	Aptitude Software (Poland) Sp. z o.o.	Unclassified	IPv4	63
AS57875	PORT LOTNICZY WROCLAW SA	Unclassified	IPv4	41
AS9002	RETN Limited	Unclassified	IPv4	34
AS31106	Wroclawski Park Technologiczny S.A.	Unclassified	IPv4	25
AS3356	Level 3 Parent, LLC	Transit	IPv4	24
AS24482	SG.GS	Hosting	IPv4	8
AS212261	Stowarzyszenie e-Poludnie	Unclassified	IPv4	1

Provenance

Where this comes from

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