asn.dev

Observed topology

AS50782 COSYS COSYS DATA GmbH

Residential RIPE

Upstreams 9 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 7
Upstream graph Who carries AS50782, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS50782 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50782: 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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6471
AS174Cogent Communications, LLCTransitIPv4 IPv680
AS24482SG.GSHostingIPv4 IPv611
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv611
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611
AS9002RETN LimitedUnclassifiedIPv68
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS13030Init7 (Switzerland) Ltd.HostingIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213053EasySolutions GmbHUnclassifiedIPv466
AS210982aRanger GmbHUnclassifiedIPv424

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6891
AS213053EasySolutions GmbHUnclassifiedIPv4510
AS174Cogent Communications, LLCTransitIPv4 IPv6170
AS210982aRanger GmbHUnclassifiedIPv424
AS24482SG.GSHostingIPv4 IPv617
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv617
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611
AS9002RETN LimitedUnclassifiedIPv68

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.