asn.dev

Observed topology

AS266989 AS266989 - ETH ENTERPRISE TECNOLOGIA LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266989: 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
AS269597STALKER ENGENHARIA EIRELIUnclassifiedIPv4 IPv61,354
AS24482SG.GSHostingIPv4 IPv641
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv641
AS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERNResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271375ZEEP INTERNETUnclassifiedIPv4126
AS52705FRANET TELECOMUnclassifiedIPv415
AS52519rodrigo przybycienUnclassifiedIPv43
AS274512V MIX DESENVOLVIMENTO DE SOFTWARE LTDAUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269597STALKER ENGENHARIA EIRELIUnclassifiedIPv4 IPv61,480
AS271375ZEEP INTERNETUnclassifiedIPv4126
AS24482SG.GSHostingIPv4 IPv646
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv643
AS52705FRANET TELECOMUnclassifiedIPv415
AS265234N-MULTIMIDIA TELECOMUNICACOES LTDA - MEResidentialIPv412
AS52519rodrigo przybycienUnclassifiedIPv43
AS274512V MIX DESENVOLVIMENTO DE SOFTWARE LTDAUnclassifiedIPv43
AS35280F5 Networks SARLHostingIPv42
AS53052MULTIVELOX SERVICOS DE PROVEDOR DE ACESSO A INTERNResidentialIPv61

Provenance

Where this comes from

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