Observed topology

AS17060 E-NETWORKS

Unclassified ARIN

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17060: 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
AS17035	NBCUniversal	Unclassified	IPv4	118
AS14178	Megacable Comunicaciones de Mexico, S.A. de C.V.	Unclassified	IPv4	58
AS11014	CPS	Residential	IPv4	57
AS4657	StarHub Ltd	Residential	IPv4	52
AS5580	GTT Communications Netherlands B.V.	Transit	IPv4	5
AS16814	NSS S.A.	Unclassified	IPv4	2
AS3257	GTT Communications Inc.	Transit	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS17035	NBCUniversal	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS17035	NBCUniversal	Unclassified	IPv4	122
AS14178	Megacable Comunicaciones de Mexico, S.A. de C.V.	Unclassified	IPv4	58
AS11014	CPS	Residential	IPv4	57
AS4657	StarHub Ltd	Residential	IPv4	52
AS5580	GTT Communications Netherlands B.V.	Transit	IPv4	5
AS16814	NSS S.A.	Unclassified	IPv4	2
AS3257	GTT Communications Inc.	Transit	IPv4	1

Provenance

Where this comes from

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