asn.dev

Observed topology

AS273412 CN TELECOM SERVICOS DE INTERNET LTDA

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS273412: 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
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6402
AS269237CarandaiNet Servicos de Internet Ltda.UnclassifiedIPv4 IPv6239
AS28198SEMPRE TELECOMUNICACOES LTDAResidentialIPv4 IPv630

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv6187
AS269237CarandaiNet Servicos de Internet Ltda.UnclassifiedIPv4 IPv6164

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6686
AS269237CarandaiNet Servicos de Internet Ltda.UnclassifiedIPv4 IPv6406
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv6187
AS28198SEMPRE TELECOMUNICACOES LTDAResidentialIPv4 IPv694

Provenance

Where this comes from

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