asn.dev

Observed topology

AS271203 AS271203 - ZUX INTERNET LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271203: 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 TelecomUnclassifiedIPv4 IPv651
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv430
AS52680BLZNET SERVICOS DE INTERNET LTDA - MEUnclassifiedIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265917RJ NET BRASIL TELECOM LTDAUnclassifiedIPv461
AS64179ZUX NET E.A.S.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv4120
AS265917RJ NET BRASIL TELECOM LTDAUnclassifiedIPv461
AS64179ZUX NET E.A.S.UnclassifiedIPv459
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv651
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv430
AS52680BLZNET SERVICOS DE INTERNET LTDA - MEUnclassifiedIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv62

Provenance

Where this comes from

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