asn.dev

Observed topology

AS266975 EURONET TELECOM

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266975: 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
AS264562PBR SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv4 IPv695
AS263427Carlos Henrique Santos de Oliveira MEUnclassifiedIPv4 IPv681
AS264293Smart Solucoes em TelecomunicacoesResidentialIPv4 IPv657
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv447
AS6939Hurricane Electric LLCTransitIPv434
AS269217ATTILA ALMEIDA DE AGUIAR MEUnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271752METEC SOLUCOESUnclassifiedIPv656

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263427Carlos Henrique Santos de Oliveira MEUnclassifiedIPv4 IPv6137
AS264562PBR SERVICOS DE TELECOMUNICACOES LTDAResidentialIPv4 IPv695
AS264293Smart Solucoes em TelecomunicacoesResidentialIPv4 IPv657
AS271752METEC SOLUCOESUnclassifiedIPv656
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv447
AS6939Hurricane Electric LLCTransitIPv434
AS269217ATTILA ALMEIDA DE AGUIAR MEUnclassifiedIPv413

Provenance

Where this comes from

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