asn.dev

Observed topology

AS262493 AS262493

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262493: 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
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv61,057

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271361IJSAT INTERNET LTDAUnclassifiedIPv6198
AS269641RURALNET BRASILUnclassifiedIPv672
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv463
AS270737G G BRUZARROSCO SERVICOS DE TELECOMUNICACOES LTDAUnclassifiedIPv633
AS263991WFNET INTERNET LTDAUnclassifiedIPv630
AS22431ABASE - SERVICOS TELECOM DES E COM SOFT LTDAUnclassifiedIPv610
AS53054AS53054UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv61,572
AS271361IJSAT INTERNET LTDAUnclassifiedIPv6198
AS263991WFNET INTERNET LTDAUnclassifiedIPv675
AS269641RURALNET BRASILUnclassifiedIPv672
AS270737G G BRUZARROSCO SERVICOS DE TELECOMUNICACOES LTDAUnclassifiedIPv633
AS22431ABASE - SERVICOS TELECOM DES E COM SOFT LTDAUnclassifiedIPv610
AS53054AS53054UnclassifiedIPv41

Provenance

Where this comes from

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