Observed topology

AS33923 ART-COM ART-COM Sp. z o.o.

Residential RIPE Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33923: 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
AS50607	Stowarzyszenie e-Poludnie	Unclassified	IPv4 IPv6	170
AS9141	P4 Sp. z o.o.	Mobile	IPv4 IPv6	79
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4 IPv6	21
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	19
AS24482	SG.GS	Hosting	IPv4 IPv6	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS200061	Gmina Miasta Jaworzna	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS50607	Stowarzyszenie e-Poludnie	Unclassified	IPv4 IPv6	212
AS9141	P4 Sp. z o.o.	Mobile	IPv4 IPv6	96
AS200061	Gmina Miasta Jaworzna	Unclassified	IPv4	65
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4 IPv6	25
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	20
AS24482	SG.GS	Hosting	IPv4 IPv6	7

Provenance

Where this comes from

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