asn.dev

Observed topology

AS211692 LVLDN-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211692: 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
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv439
AS6939Hurricane Electric LLCTransitIPv49
AS12773Meshnet ltd.UnclassifiedIPv46
AS44539Redi LLCUnclassifiedIPv45
AS24482SG.GSHostingIPv41
AS37721Virtual-Technologies-Solutions-SAResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214268ORANGE LLCUnclassifiedIPv4430
AS31069FOP Mukhina Kateryna VolodymyrivnaResidentialIPv4122
AS196629Antipov OlegUnclassifiedIPv4122

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4620
AS214268ORANGE LLCUnclassifiedIPv4566
AS12773Meshnet ltd.UnclassifiedIPv4123
AS31069FOP Mukhina Kateryna VolodymyrivnaResidentialIPv4122
AS196629Antipov OlegUnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv486
AS44539Redi LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv410
AS37721Virtual-Technologies-Solutions-SAResidentialIPv410

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.