asn.dev

Observed topology

AS35680 VOLIA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35680: 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
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv41,020

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30860Virtual Systems LLCHostingIPv438
AS31437Engler parts llcUnclassifiedIPv45
AS8870Overseas Technologies LLCUnclassifiedIPv42
AS39528Video Internet Technologies LTD.UnclassifiedIPv41
AS43773PE Konstantin Vladimirovich KravchenkoUnclassifiedIPv41
AS44351Miritec LLCUnclassifiedIPv41
AS51743LLC "HOST PARK GROUP"UnclassifiedIPv41
AS57167Maksym RivtinUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv41,071
AS30860Virtual Systems LLCHostingIPv439
AS31437Engler parts llcUnclassifiedIPv45
AS8870Overseas Technologies LLCUnclassifiedIPv42
AS39528Video Internet Technologies LTD.UnclassifiedIPv41
AS43773PE Konstantin Vladimirovich KravchenkoUnclassifiedIPv41
AS44351Miritec LLCUnclassifiedIPv41
AS51743LLC "HOST PARK GROUP"UnclassifiedIPv41
AS57167Maksym RivtinUnclassifiedIPv41

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.