Observed topology

AS50467 BESKID-MEDIA-AS

Residential RIPE Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 7

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50467: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	354
AS9002	RETN Limited	Unclassified	IPv4 IPv6	174
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	157
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS24115	Equinix	Hosting	IPv6	2
AS29632	Netassist International EOOD	Unclassified	IPv6	2
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS198133	AIRNET MARIUSZ KAJDAS, TOMASZ PYREK sp.j.	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	354
AS9002	RETN Limited	Unclassified	IPv4 IPv6	176
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	158
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS198133	AIRNET MARIUSZ KAJDAS, TOMASZ PYREK sp.j.	Unclassified	IPv4	3
AS24115	Equinix	Hosting	IPv6	2
AS29632	Netassist International EOOD	Unclassified	IPv6	2
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	1

Provenance

Where this comes from

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