asn.dev

Observed topology

AS266465 COSTA & SILVA LTDA - ME

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266465: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6165
AS28624PROVEDORA CMA INTERNET LTDAUnclassifiedIPv4 IPv6157
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv43
AS266607REELU NET COMUNICACOES LTDAResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267628CLOVIS DA SILVA ALBUQUERQUE INTERNET - MEUnclassifiedIPv4 IPv6199
AS266060DIGIL 360 PROVEDORES DE ACESSO LTDA-MEUnclassifiedIPv4 IPv6152
AS270503R LUIZ LEANDROUnclassifiedIPv460
AS268384AJC TELECOMUnclassifiedIPv4 IPv649

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28624PROVEDORA CMA INTERNET LTDAUnclassifiedIPv4 IPv6490
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6291
AS267628CLOVIS DA SILVA ALBUQUERQUE INTERNET - MEUnclassifiedIPv4 IPv6199
AS266060DIGIL 360 PROVEDORES DE ACESSO LTDA-MEUnclassifiedIPv4 IPv6152
AS270503R LUIZ LEANDROUnclassifiedIPv460
AS268384AJC TELECOMUnclassifiedIPv4 IPv649
AS6939Hurricane Electric LLCTransitIPv49
AS24482SG.GSHostingIPv44
AS266607REELU NET COMUNICACOES LTDAResidentialIPv61

Provenance

Where this comes from

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