asn.dev

Observed topology

AS28323 AYKO TECNOLOGIA LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28323: 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
AS7738V talUnclassifiedIPv4 IPv61,491
AS262288Go In TecnologiaResidentialIPv4 IPv61,029
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv6395
AS174Cogent Communications, LLCTransitIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28650Lojas Simonetti LtdaUnclassifiedIPv470
AS262991MG Vidros Automotivos Ltda.UnclassifiedIPv4 IPv624

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7738V talUnclassifiedIPv4 IPv61,559
AS262288Go In TecnologiaResidentialIPv4 IPv61,029
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv6421
AS28650Lojas Simonetti LtdaUnclassifiedIPv470
AS174Cogent Communications, LLCTransitIPv458
AS262991MG Vidros Automotivos Ltda.UnclassifiedIPv4 IPv624

Provenance

Where this comes from

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