asn.dev

Observed topology

AS30860 YURTEH-AS Virtual Systems LLC

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30860: 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
AS6698Virtual Systems LLCHostingIPv4 IPv62,355
AS3223Voxility LLPHostingIPv4376
AS43641SOLLUTIUM EU Sp z.o.o.UnclassifiedIPv4191
AS35680Volia-Cable LLCUnclassifiedIPv438
AS6939Hurricane Electric LLCTransitIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6698Virtual Systems LLCHostingIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6698Virtual Systems LLCHostingIPv4 IPv62,357
AS3223Voxility LLPHostingIPv4377
AS43641SOLLUTIUM EU Sp z.o.o.UnclassifiedIPv4191
AS35680Volia-Cable LLCUnclassifiedIPv439
AS6939Hurricane Electric LLCTransitIPv43

Provenance

Where this comes from

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