asn.dev

Observed topology

AS270353 AS270353 - Tyna Host - Datacenter no Brasil

Hosting LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270353: 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
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6437
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6135
AS6939Hurricane Electric LLCTransitIPv4 IPv6113
AS24482SG.GSHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272547Servicos de Infraestrutura e DatacenterUnclassifiedIPv4 IPv61,860
AS275773Cubo Tecnologia Ltda.UnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS272547Servicos de Infraestrutura e DatacenterUnclassifiedIPv4 IPv61,860
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv61,500
AS23106AMERICAN TOWER DO BRASIL-COMUNICACAO MULTIMIDIA LTUnclassifiedIPv4 IPv6594
AS6939Hurricane Electric LLCTransitIPv4 IPv6431
AS24482SG.GSHostingIPv4 IPv644
AS275773Cubo Tecnologia Ltda.UnclassifiedIPv633
AS37721Virtual Technologies & SolutionsResidentialIPv430

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.