asn.dev

Observed topology

AS61776 Provedor de Acesso a Internet Eireli

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61776: 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
AS262462Aranet PlayUnclassifiedIPv4 IPv6477
AS264329ESTRATEGIA REDES DE TELECOMUNICACOES LTDA.UnclassifiedIPv4 IPv6232
AS264022REDE CONEXAONETUnclassifiedIPv460
AS264496Fibralink LTDAResidentialIPv4 IPv624
AS26615TIM S/AMobileIPv413
AS264525Coelho TecnologiaResidentialIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265500ALMEIRIM TELECOM LTDA - MEUnclassifiedIPv461
AS28572Apoiocom Digital Ltda - EPPUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262462Aranet PlayUnclassifiedIPv4 IPv6477
AS264329ESTRATEGIA REDES DE TELECOMUNICACOES LTDA.UnclassifiedIPv4 IPv6342
AS265500ALMEIRIM TELECOM LTDA - MEUnclassifiedIPv461
AS264022REDE CONEXAONETUnclassifiedIPv460
AS28572Apoiocom Digital Ltda - EPPUnclassifiedIPv459
AS264496Fibralink LTDAResidentialIPv4 IPv624
AS26615TIM S/AMobileIPv423
AS264525Coelho TecnologiaResidentialIPv65

Provenance

Where this comes from

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