Observed topology

AS39199 RADIONET

Unclassified RIPE NSP

Upstreams 5 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39199: 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
AS43380	Digital Telecom IX LLC	Unclassified	IPv4	174
AS6939	Hurricane Electric LLC	Transit	IPv4	80
AS35297	Dataline LLC	Unclassified	IPv4	68
AS9002	RETN Limited	Unclassified	IPv4	30
AS199995	Omega Telecom LLC	Residential	IPv4	16

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS29574	Vinnytsia National Technical University	Unclassified	IPv4	128
AS20714	"Merlin-Telekom" LLC	Residential	IPv4	64
AS206259	SKAYVIN LLC	Unclassified	IPv4	64
AS16005	LLC CMSM	Unclassified	IPv4	45
AS211570	PE TV and Radio Company Kentavr-TV	Unclassified	IPv4	18
AS212983	METANNET LLC	Unclassified	IPv4	6

Adjacency

Adjacent networks

All 11

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

AS	Network	Type	Families	Paths seen
AS35297	Dataline LLC	Unclassified	IPv4	238
AS43380	Digital Telecom IX LLC	Unclassified	IPv4	224
AS29574	Vinnytsia National Technical University	Unclassified	IPv4	128
AS9002	RETN Limited	Unclassified	IPv4	109
AS6939	Hurricane Electric LLC	Transit	IPv4	80
AS20714	"Merlin-Telekom" LLC	Residential	IPv4	64
AS206259	SKAYVIN LLC	Unclassified	IPv4	64
AS16005	LLC CMSM	Unclassified	IPv4	45
AS199995	Omega Telecom LLC	Residential	IPv4	42
AS211570	PE TV and Radio Company Kentavr-TV	Unclassified	IPv4	18

All 11 adjacent →

Provenance

Where this comes from

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