asn.dev

Observed topology

AS270816 AS270816 - ZAMTECH COM TELECOMUNICACOES LTDA

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270816: 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
AS268235VLA TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6332
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS35280F5 Networks SARLHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271661WESLEY RAMOS DIASUnclassifiedIPv4 IPv6445
AS271411FIBRA 1000 TELECOM LTDA - MEUnclassifiedIPv4 IPv6212

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268235VLA TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6821
AS271661WESLEY RAMOS DIASUnclassifiedIPv4 IPv6445
AS271411FIBRA 1000 TELECOM LTDA - MEUnclassifiedIPv4 IPv6212
AS6939Hurricane Electric LLCTransitIPv4 IPv6192
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv619
AS35280F5 Networks SARLHostingIPv62

Provenance

Where this comes from

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