asn.dev

Observed topology

AS262473 SAMISSA TELECOM

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262473: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6516
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6475
AS52573Une Telecom LtdaResidentialIPv4 IPv6381
AS6939Hurricane Electric LLCTransitIPv4 IPv6124
AS24482SG.GSHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267303CENTRO OESTE PROVEDORUnclassifiedIPv4171

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6638
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6516
AS52573Une Telecom LtdaResidentialIPv4 IPv6381
AS267303CENTRO OESTE PROVEDORUnclassifiedIPv4171
AS6939Hurricane Electric LLCTransitIPv4 IPv6144
AS24482SG.GSHostingIPv4 IPv616
AS264023SE77E TELECOM EIRELI MEResidentialIPv614
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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