asn.dev

Observed topology

AS50107 VISTA-TECHNOLOGY

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50107: 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
AS47864V-NET B.V.UnclassifiedIPv4 IPv6161
AS6939Hurricane Electric LLCTransitIPv4 IPv6115
AS205103Telegraph42 Management GmbHUnclassifiedIPv4 IPv614
AS174Cogent Communications, LLCTransitIPv64
AS35168TNS-Plus LLPUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198084Orbicom LLPUnclassifiedIPv4 IPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS47864V-NET B.V.UnclassifiedIPv4 IPv64,436
AS198084Orbicom LLPUnclassifiedIPv4 IPv64,275
AS6939Hurricane Electric LLCTransitIPv4 IPv6115
AS205103Telegraph42 Management GmbHUnclassifiedIPv4 IPv614
AS174Cogent Communications, LLCTransitIPv64
AS35168TNS-Plus LLPUnclassifiedIPv44

Provenance

Where this comes from

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