asn.dev

Observed topology

AS268323 AZZA TELECOM SERVICOS EM TELECOMUNICACOES LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268323: 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
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv65,926
AS6939Hurricane Electric LLCTransitIPv4 IPv6129

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262610INTERall Informatica Ltda.UnclassifiedIPv4 IPv6557
AS269523Life ConnectionsResidentialIPv4 IPv6273
AS265918SMART LINCK TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6250
AS264141Vale do Ribeira Internet Ltda - MeUnclassifiedIPv4126
AS263364Tetra Pak LtdaUnclassifiedIPv463
AS271018Universal Net - Servicos de Comunicacao Mult LTDAUnclassifiedIPv65

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28220Alares Cabo Servicos de Telecomunicacoes S.A.ResidentialIPv4 IPv67,186
AS262610INTERall Informatica Ltda.UnclassifiedIPv4 IPv6557
AS269523Life ConnectionsResidentialIPv4 IPv6273
AS265918SMART LINCK TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6250
AS6939Hurricane Electric LLCTransitIPv4 IPv6138
AS264141Vale do Ribeira Internet Ltda - MeUnclassifiedIPv4126
AS263364Tetra Pak LtdaUnclassifiedIPv463
AS3356Level 3 Parent, LLCTransitIPv65
AS271018Universal Net - Servicos de Comunicacao Mult LTDAUnclassifiedIPv65

Provenance

Where this comes from

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