asn.dev

Observed topology

AS50837 CLOUDSIGMA-AS

Hosting RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS50837: 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
AS6461Zayo BandwidthTransitIPv4 IPv6492
AS25091IP-Max SAUnclassifiedIPv4 IPv6426
AS174Cogent Communications, LLCTransitIPv4 IPv6397
AS29684Nour Internet Company for Communications and Information Technology Ltd.UnclassifiedIPv4356
AS30815Detecon Al Saudia Co. Ltd.UnclassifiedIPv4240
AS15612ServeCentric Ltd.UnclassifiedIPv4180
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6179
AS34224Neterra Ltd.UnclassifiedIPv4 IPv6159
AS6939Hurricane Electric LLCTransitIPv4 IPv6108
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv690

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS64462Stephan Roland WolfUnclassifiedIPv4124

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS25091IP-Max SAUnclassifiedIPv4 IPv6562
AS6461Zayo BandwidthTransitIPv4 IPv6492
AS174Cogent Communications, LLCTransitIPv4 IPv6397
AS29684Nour Internet Company for Communications and Information Technology Ltd.UnclassifiedIPv4356
AS30815Detecon Al Saudia Co. Ltd.UnclassifiedIPv4240
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6211
AS15612ServeCentric Ltd.UnclassifiedIPv4180
AS34224Neterra Ltd.UnclassifiedIPv4 IPv6159
AS64462Stephan Roland WolfUnclassifiedIPv4124
AS6939Hurricane Electric LLCTransitIPv4 IPv6120

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.