asn.dev

Observed topology

AS265703 AS265703 - AUSTRO INTERNET S.A.

Residential RIPE Cable/DSL/ISP

Upstreams 3 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 3
Upstream graph Who carries AS265703, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS265703 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265703: 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.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6242
AS6939Hurricane Electric LLCTransitIPv4 IPv6127
AS263237PowerHost Telecom SPAUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265831SOC. COMERCIAL WIRENET CHILE LTDA.ResidentialIPv4528
AS272957TELECOMUNICACIONES MARJORIE ANDREA MORI LAGOS E.I.R.L.UnclassifiedIPv4372
AS64139GRUPO METROWAN TELECOM SPAResidentialIPv424

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,106
AS265831SOC. COMERCIAL WIRENET CHILE LTDA.ResidentialIPv4528
AS272957TELECOMUNICACIONES MARJORIE ANDREA MORI LAGOS E.I.R.L.UnclassifiedIPv4372
AS6939Hurricane Electric LLCTransitIPv4 IPv6187
AS64139GRUPO METROWAN TELECOM SPAResidentialIPv424
AS263237PowerHost Telecom SPAUnclassifiedIPv64

Provenance

Where this comes from

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