Observed topology

AS203620 Polnocny Klaster ICT SP. z.o.o.

Unclassified RIPE Cable/DSL/ISP

Upstreams 0 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203620: 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 AS203620 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS201637	Tomasz Naruszewicz	Unclassified	IPv4	54
AS60466	INTROLAN Marzenna Barbara Bronakowska	Unclassified	IPv4	28
AS197701	NET-KOMP Krystian Kania	Unclassified	IPv4	27
AS199449	Maciej Zukowski trading as Netkom Uslugi informatyczne	Residential	IPv4	15
AS43073	Artur Wojtysiak trading as Danar Sp. z o.o.	Unclassified	IPv4	14
AS203302	Adam Gwozdz trading as IWKD	Unclassified	IPv4	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS24724	Atman Sp. z o.o.	Hosting	IPv4	135
AS201637	Tomasz Naruszewicz	Unclassified	IPv4	54
AS60466	INTROLAN Marzenna Barbara Bronakowska	Unclassified	IPv4	28
AS197701	NET-KOMP Krystian Kania	Unclassified	IPv4	27
AS199449	Maciej Zukowski trading as Netkom Uslugi informatyczne	Residential	IPv4	15
AS43073	Artur Wojtysiak trading as Danar Sp. z o.o.	Unclassified	IPv4	14
AS6939	Hurricane Electric LLC	Transit	IPv4	6
AS203302	Adam Gwozdz trading as IWKD	Unclassified	IPv4	6
AS24115	Equinix	Hosting	IPv4	3

Provenance

Where this comes from

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