asn.dev

Observed topology

AS265249 AS265249 - TCM TELECOM LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265249: 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 TelecomUnclassifiedIPv4152
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv638
AS262293Sistema Oeste de Servicos LTDAUnclassifiedIPv417
AS24482SG.GSHostingIPv4 IPv64
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264561ASSUNET LTDA - MEUnclassifiedIPv4405

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4534
AS264561ASSUNET LTDA - MEUnclassifiedIPv4405
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv645
AS262293Sistema Oeste de Servicos LTDAUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv611
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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