Observed topology

AS39838 as-peering_latam Valor Information Technologies, S.L.

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39838: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	60
AS49353	Valor Information Technologies, S.L.	Unclassified	IPv4	60
AS39640	Valor Information Technologies, S.L.	Hosting	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS272809	THUNDERNET, C.A.	Residential	IPv4 IPv6	3,694
AS21826	Corporacion Telemic C.A.	Unclassified	IPv4 IPv6	2,568
AS274208	VERLA S.A.S.	Unclassified	IPv4 IPv6	244

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	6,512
AS272809	THUNDERNET, C.A.	Residential	IPv4 IPv6	3,696
AS21826	Corporacion Telemic C.A.	Unclassified	IPv4 IPv6	2,573
AS274208	VERLA S.A.S.	Unclassified	IPv4 IPv6	244
AS49353	Valor Information Technologies, S.L.	Unclassified	IPv4	60
AS271957	SOMOS NETWORKS COLOMBIA S.A.S. BIC	Residential	IPv6	50
AS39640	Valor Information Technologies, S.L.	Hosting	IPv6	32
AS6939	Hurricane Electric LLC	Transit	IPv4	8
AS52320	GlobeNet Cabos Submarinos Colombia, S.A.S.	Unclassified	IPv4	3

Provenance

Where this comes from

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