Observed topology

AS14845 Universidad Nacional del Sur

Unclassified APNIC

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14845: 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
AS11664	Techtel LMDS Comunicaciones Interactivas S.A.	Residential	IPv4	48
AS4270	Red de Interconexion Universitaria	Education	IPv4	16
AS52332	CABASE Camara Arg de Base de Datos y Serv en Linea	Unclassified	IPv4	10

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269784	UNIVERSIDAD PROVINCIAL DEL SUDOESTE (UPSO)	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11664	Techtel LMDS Comunicaciones Interactivas S.A.	Residential	IPv4	107
AS269784	UNIVERSIDAD PROVINCIAL DEL SUDOESTE (UPSO)	Unclassified	IPv4	59
AS4270	Red de Interconexion Universitaria	Education	IPv4	16
AS52332	CABASE Camara Arg de Base de Datos y Serv en Linea	Unclassified	IPv4	10

Provenance

Where this comes from

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