Observed topology

AS206295 MEDSIGROUP

Unclassified RIPE

Upstreams 14 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 14

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS206295: 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
AS8359	MTS PJSC	Mobile	IPv4	260
AS6939	Hurricane Electric LLC	Transit	IPv4	57
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	21
AS1836	green.ch AG	Residential	IPv4	7
AS6797	GlobalConnect AB	Unclassified	IPv4	7
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	7
AS24482	SG.GS	Hosting	IPv4	7
AS34019	Hivane Association	Unclassified	IPv4	7
AS37100	SEACOM Limited	Unclassified	IPv4	7
AS37721	Virtual Technologies & Solutions	Residential	IPv4	7

All 14 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 14

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

AS	Network	Type	Families	Paths seen
AS8359	MTS PJSC	Mobile	IPv4	260
AS6939	Hurricane Electric LLC	Transit	IPv4	57
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	21
AS1836	green.ch AG	Residential	IPv4	7
AS6797	GlobalConnect AB	Unclassified	IPv4	7
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	7
AS24482	SG.GS	Hosting	IPv4	7
AS34019	Hivane Association	Unclassified	IPv4	7
AS37100	SEACOM Limited	Unclassified	IPv4	7
AS37721	Virtual Technologies & Solutions	Residential	IPv4	7

All 14 adjacent →

Provenance

Where this comes from

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