Observed topology

AS50261 ACENET

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50261: 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
AS41206	United Telecom Zartkoruen Mukodo Reszvenytarsasag	Unclassified	IPv4 IPv6	514

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS201450	ITConsult-Pro Zrt.	Unclassified	IPv4 IPv6	154
AS214308	Rackforest Zrt.	Unclassified	IPv4 IPv6	81
AS30012	Universal Music Group, INC.	Unclassified	IPv4	60
AS61294	Andreas Stihl Kereskedelmi Kft.	Unclassified	IPv4	60
AS206814	SCI-Network pInc.	Unclassified	IPv4 IPv6	47
AS208891	Kozlekedesi es Beruhazasi Miniszterium	Unclassified	IPv4	12
AS20742	Internet4U Kereskedelmi es Szolgaltato Kft.	Residential	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS41206	United Telecom Zartkoruen Mukodo Reszvenytarsasag	Unclassified	IPv4 IPv6	931
AS201450	ITConsult-Pro Zrt.	Unclassified	IPv4 IPv6	154
AS214308	Rackforest Zrt.	Unclassified	IPv4 IPv6	81
AS30012	Universal Music Group, INC.	Unclassified	IPv4	60
AS61294	Andreas Stihl Kereskedelmi Kft.	Unclassified	IPv4	60
AS206814	SCI-Network pInc.	Unclassified	IPv4 IPv6	47
AS208891	Kozlekedesi es Beruhazasi Miniszterium	Unclassified	IPv4	12
AS20742	Internet4U Kereskedelmi es Szolgaltato Kft.	Residential	IPv4	3

Provenance

Where this comes from

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