asn.dev

Observed topology

AS6698 virtualsystems Virtual Systems LLC

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6698: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,993
AS174Cogent Communications, LLCTransitIPv4343
AS29107Synapse Network LTDUnclassifiedIPv458
AS30860Virtual Systems LLCHostingIPv458
AS24482SG.GSHostingIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30860Virtual Systems LLCHostingIPv4 IPv62,279
AS29107Synapse Network LTDUnclassifiedIPv41,334
AS26383Baxet Group Inc.UnclassifiedIPv4 IPv6160
AS31469Virtual Systems LLCUnclassifiedIPv4126
AS42504SPD Bilopol Roman LeonidovichUnclassifiedIPv488

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv65,861
AS30860Virtual Systems LLCHostingIPv4 IPv62,337
AS29107Synapse Network LTDUnclassifiedIPv41,655
AS174Cogent Communications, LLCTransitIPv4 IPv61,102
AS42504SPD Bilopol Roman LeonidovichUnclassifiedIPv4465
AS26383Baxet Group Inc.UnclassifiedIPv4 IPv6160
AS31469Virtual Systems LLCUnclassifiedIPv4126
AS24482SG.GSHostingIPv410

Provenance

Where this comes from

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