asn.dev

Observed topology

AS50050 NU Metropolitan Area Network

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS50050: 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
AS24785Broadband Hosting B.V.HostingIPv4312
AS174Cogent Communications, LLCTransitIPv488
AS6939Hurricane Electric LLCTransitIPv476
AS16097HL komm Telekommunikations GmbHResidentialIPv412
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv410
AS6797GlobalConnect ABUnclassifiedIPv410
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS37100SEACOM LimitedUnclassifiedIPv410

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208290WIFISAX GmbHUnclassifiedIPv4174

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS24785Broadband Hosting B.V.HostingIPv4372
AS208290WIFISAX GmbHUnclassifiedIPv4174
AS174Cogent Communications, LLCTransitIPv4154
AS6939Hurricane Electric LLCTransitIPv497
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv413
AS6797GlobalConnect ABUnclassifiedIPv413
AS17639Converge ICT Solutions Inc.UnclassifiedIPv413
AS20485Joint Stock Company TransTeleComUnclassifiedIPv413
AS24482SG.GSHostingIPv413
AS37100SEACOM LimitedUnclassifiedIPv413

All 15 adjacent →

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.