asn.dev

Observed topology

AS266952 AS266952 - Acesso Fibra

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266952: 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
AS273517RUPI TelecomResidentialIPv4 IPv6353
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv660
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270892MANOEL GOUVEIA DA SILVA - MEUnclassifiedIPv4 IPv659
AS267512ENTERPRISE TELECOMUNICACOESUnclassifiedIPv4 IPv621

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS273517RUPI TelecomResidentialIPv4 IPv6353
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6102
AS270892MANOEL GOUVEIA DA SILVA - MEUnclassifiedIPv4 IPv659
AS267512ENTERPRISE TELECOMUNICACOESUnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv620
AS35280F5 Networks SARLHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv616

Provenance

Where this comes from

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