asn.dev

Observed topology

AS28296 Acessa Telecomunicacoes Ltda

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28296: 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
AS21574Century Telecom LtdaUnclassifiedIPv4290
AS265369C-ComTelecom Servios Ltda-MEResidentialIPv459
AS6939Hurricane Electric LLCTransitIPv619
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269302Fourlink Telecom Servicos de Telecomunicacoes LtdaUnclassifiedIPv4193
AS270704MAIS NORTE TELECOM LTDAUnclassifiedIPv458
AS264100RIO CABLE TELECOM LTDAResidentialIPv457

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS21574Century Telecom LtdaUnclassifiedIPv4435
AS269302Fourlink Telecom Servicos de Telecomunicacoes LtdaUnclassifiedIPv4193
AS264100RIO CABLE TELECOM LTDAResidentialIPv4155
AS6939Hurricane Electric LLCTransitIPv4 IPv671
AS265369C-ComTelecom Servios Ltda-MEResidentialIPv459
AS270704MAIS NORTE TELECOM LTDAUnclassifiedIPv458
AS24482SG.GSHostingIPv45
AS35280F5 Networks SARLHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv44

Provenance

Where this comes from

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