Observed topology

AS39279 CTS-

Unclassified RIPE Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39279: 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
AS25319	Information Technology and Cyber Security Service	Unclassified	IPv4	341
AS3223	Voxility LLP	Hosting	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS28990	Information Technology and Cyber Security Service	Unclassified	IPv4	349
AS216137	IP UTM	Unclassified	IPv4	104

Adjacency

Adjacent networks

All 12

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

AS	Network	Type	Families	Paths seen
AS25319	Information Technology and Cyber Security Service	Unclassified	IPv4	756
AS174	Cogent Communications, LLC	Transit	IPv4	379
AS28990	Information Technology and Cyber Security Service	Unclassified	IPv4	349
AS8926	Moldtelecom SA	Residential	IPv4	252
AS31500	Global Network Management Inc	Unclassified	IPv4	221
AS31313	Serviciul de Telecomunicatii Speciale	Hosting	IPv4	104
AS216137	IP UTM	Unclassified	IPv4	104
AS6939	Hurricane Electric LLC	Transit	IPv4	50
AS208972	GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI	Unclassified	IPv4	23
AS1299	Arelion Sweden AB	Transit	IPv4	5

All 12 adjacent →

Provenance

Where this comes from

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