asn.dev

Observed topology

AS50391 DIVERGENT DIVERGENT NETWORKS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50391: 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 IPv6129
AS61049Exascale LtdResidentialIPv4 IPv643
AS48070DSM (GB) LimitedHostingIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210985Christopher BishopHostingIPv674

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6193
AS210985Christopher BishopHostingIPv674
AS61049Exascale LtdResidentialIPv4 IPv647
AS48070DSM (GB) LimitedHostingIPv4 IPv620
AS24482SG.GSHostingIPv4 IPv67
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

Provenance

Where this comes from

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