Observed topology

AS39875 W3Z

Residential RIPE

Upstreams 18 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 18

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS39875: 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
AS174	Cogent Communications, LLC	Transit	IPv4	55
AS6939	Hurricane Electric LLC	Transit	IPv4	17
AS4455	IX Reach Ltd	Unclassified	IPv4	8
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	6
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	5
AS50304	Blix Solutions AS	Unclassified	IPv4	4
AS3741	Dimension Data	Unclassified	IPv4	2
AS4657	StarHub Ltd	Residential	IPv4	2
AS12552	GlobalConnect AB	Unclassified	IPv4	2
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	2

All 18 upstreams →

Transit

Downstream networks

inferred

Networks for which AS39875 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 18

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	55
AS6939	Hurricane Electric LLC	Transit	IPv4	17
AS4455	IX Reach Ltd	Unclassified	IPv4	8
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	6
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	5
AS50304	Blix Solutions AS	Unclassified	IPv4	4
AS3741	Dimension Data	Unclassified	IPv4	2
AS4657	StarHub Ltd	Residential	IPv4	2
AS12552	GlobalConnect AB	Unclassified	IPv4	2
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	2

All 18 adjacent →

Provenance

Where this comes from

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