asn.dev

Observed topology

AS50265 GT-AS Invest Mobile LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50265: 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
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv6361
AS3216PJSC "Vimpelcom"MobileIPv4181
AS12695LLC Digital NetworkHostingIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS49673Truenetwork LLCUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43628ATD LLCUnclassifiedIPv462
AS210342CKU-IT LLC.UnclassifiedIPv418

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv6404
AS3216PJSC "Vimpelcom"MobileIPv4211
AS43628ATD LLCUnclassifiedIPv462
AS12695LLC Digital NetworkHostingIPv4 IPv629
AS210342CKU-IT LLC.UnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS49673Truenetwork LLCUnclassifiedIPv410

Provenance

Where this comes from

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