asn.dev

Observed topology

AS271358 AP INTERNET

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271358: 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
AS269138MOV TELECOM SERVICOS DE PROVEDORES DE INTERNET LTDUnclassifiedIPv4 IPv6131
AS269665LEKST TELECOMResidentialIPv4114
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv656
AS271529ONLINE TELECOM.IP LTDA MEHostingIPv4 IPv641
AS271683BRISNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv639

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269138MOV TELECOM SERVICOS DE PROVEDORES DE INTERNET LTDUnclassifiedIPv4 IPv6131
AS269665LEKST TELECOMResidentialIPv4114
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv656
AS271529ONLINE TELECOM.IP LTDA MEHostingIPv4 IPv641
AS271683BRISNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv639

Provenance

Where this comes from

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