asn.dev

Observed topology

AS273721 AS273721 - TCA TELECOM LTDA - ME

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273721: 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
AS3356Level 3 Parent, LLCTransitIPv6154
AS264170Winet BrasilResidentialIPv670

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264056ULI TELECOM LTDAUnclassifiedIPv498
AS268124CONEXAO TELECOMUnclassifiedIPv459
AS275645CONCE PROJETOS TELECOM LTDAUnclassifiedIPv626

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6278
AS264170Winet BrasilResidentialIPv4 IPv6206
AS264056ULI TELECOM LTDAUnclassifiedIPv498
AS2723721unnamedUnclassifiedIPv477
AS268124CONEXAO TELECOMUnclassifiedIPv459
AS275645CONCE PROJETOS TELECOM LTDAUnclassifiedIPv626

Provenance

Where this comes from

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