asn.dev

Observed topology

AS50889 GFN-EMEA NVIDIA GeForce NOW

Hosting RIPE Content

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS50889: 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
AS1299Arelion Sweden ABTransitIPv4688
AS6461Zayo BandwidthTransitIPv4493
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4183
AS8866Vivacom Bulgaria EADResidentialIPv4143
AS3257GTT Communications Inc.TransitIPv499
AS3356Level 3 Parent, LLCTransitIPv469
AS49800GNC-Alfa CJSCResidentialIPv460
AS174Cogent Communications, LLCTransitIPv453
AS6939Hurricane Electric LLCTransitIPv453
AS8220COLT Technology Services Group LimitedHostingIPv452

All 27 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4688
AS6461Zayo BandwidthTransitIPv4493
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv4183
AS8866Vivacom Bulgaria EADResidentialIPv4143
AS3257GTT Communications Inc.TransitIPv499
AS3356Level 3 Parent, LLCTransitIPv469
AS49800GNC-Alfa CJSCResidentialIPv460
AS174Cogent Communications, LLCTransitIPv453
AS6939Hurricane Electric LLCTransitIPv453
AS8220COLT Technology Services Group LimitedHostingIPv452

All 27 adjacent →

Provenance

Where this comes from

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