asn.dev

Observed topology

AS50392 CAMPUS-RV-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50392: 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
AS35297Dataline LLCUnclassifiedIPv4 IPv6233
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv641
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52125FOP Samosenok Alexandr SergeevichUnclassifiedIPv4325
AS43815Nash Prostir LLCUnclassifiedIPv4 IPv6233
AS59682MULTICAST LLCUnclassifiedIPv4114
AS48775Nashnet Rivne LLCUnclassifiedIPv4102
AS57954Budko Dmitro PavlovichUnclassifiedIPv4 IPv696
AS39084LLC RINETUnclassifiedIPv468
AS204669NETLABS LLCUnclassifiedIPv638
AS47361Manufacturing-Technical company System Design LLCUnclassifiedIPv47

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv4 IPv6836
AS3255LLC EKSINTECHUnclassifiedIPv4 IPv6344
AS52125FOP Samosenok Alexandr SergeevichUnclassifiedIPv4325
AS43815Nash Prostir LLCUnclassifiedIPv4 IPv6233
AS59682MULTICAST LLCUnclassifiedIPv4114
AS48775Nashnet Rivne LLCUnclassifiedIPv4102
AS57954Budko Dmitro PavlovichUnclassifiedIPv4 IPv696
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv684
AS39084LLC RINETUnclassifiedIPv468
AS204669NETLABS LLCUnclassifiedIPv638

All 12 adjacent →

Provenance

Where this comes from

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