asn.dev

Observed topology

AS265170 GSM TELECOM SERVICO DE PROVEDOR DE INTERNET LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265170: 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
AS53087TELY Ltda.ResidentialIPv463
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv462
AS264273A & G TELECOMUNICACOES LTDA EPPUnclassifiedIPv459
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv424
AS53102S.I. TELECOM. SERVICOS DE TELEFONIA LTDA EPPResidentialIPv421
AS273480NOW FIBRA PROVEDOR DE INTERNET LTDAResidentialIPv412
AS1031PEER 1031 LLCUnclassifiedIPv42

Transit

Downstream networks

inferred

Networks for which AS265170 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 AS265170 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS53087TELY Ltda.ResidentialIPv463
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv462
AS264273A & G TELECOMUNICACOES LTDA EPPUnclassifiedIPv459
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv424
AS53102S.I. TELECOM. SERVICOS DE TELEFONIA LTDA EPPResidentialIPv421
AS273480NOW FIBRA PROVEDOR DE INTERNET LTDAResidentialIPv412
AS1031PEER 1031 LLCUnclassifiedIPv42

Provenance

Where this comes from

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