Observed topology

AS41695 VOSTRON-AS

Unclassified RIPE

Upstreams 13 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 2

Upstream graph Who carries AS41695, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS41695 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS41695: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	118
AS174	Cogent Communications, LLC	Transit	IPv4	24
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	6
AS3741	Dimension Data	Unclassified	IPv4	2
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	2
AS24482	SG.GS	Hosting	IPv4	2
AS37100	SEACOM Limited	Unclassified	IPv4	2
AS37721	Virtual Technologies & Solutions	Residential	IPv4	2
AS48185	team.blue NV	Unclassified	IPv4	2
AS48362	Stadtwerke Feldkirch	Residential	IPv4	2

All 13 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16568	PROMEGA CORPORATION	Unclassified	IPv4	51

Adjacency

Adjacent networks

All 14

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	156
AS16568	PROMEGA CORPORATION	Unclassified	IPv4	51
AS174	Cogent Communications, LLC	Transit	IPv4	27
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	9
AS3741	Dimension Data	Unclassified	IPv4	3
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	3
AS24482	SG.GS	Hosting	IPv4	3
AS37100	SEACOM Limited	Unclassified	IPv4	3
AS37721	Virtual Technologies & Solutions	Residential	IPv4	3
AS50300	CustodianDC Limited	Unclassified	IPv4	3

All 14 adjacent →

Provenance

Where this comes from

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