Observed topology

AS36165 ITM-TELECOM

Hosting ARIN

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36165: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	470
AS1299	Arelion Sweden AB	Transit	IPv4	80
AS174	Cogent Communications, LLC	Transit	IPv4	60
AS3356	Level 3 Parent, LLC	Transit	IPv4	20
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	10
AS24482	SG.GS	Hosting	IPv4	10

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269879	INTEGRACION DE TECNOLOGIAS MOVILES ITM C.A.	Unclassified	IPv4	888
AS263771	IP NET, C.A.	Unclassified	IPv4	692

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	2,109
AS269879	INTEGRACION DE TECNOLOGIAS MOVILES ITM C.A.	Unclassified	IPv4	1,504
AS263771	IP NET, C.A.	Unclassified	IPv4	692
AS1299	Arelion Sweden AB	Transit	IPv4	371
AS174	Cogent Communications, LLC	Transit	IPv4	235
AS3356	Level 3 Parent, LLC	Transit	IPv4	50
AS24482	SG.GS	Hosting	IPv4	42
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	39

Provenance

Where this comes from

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