asn.dev

Observed topology

AS264609 AS264609 - TECOMUNICA NICARAGUA

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264609: 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
AS3356Level 3 Parent, LLCTransitIPv4296
AS11830Instituto Costarricense de Electricidad y Telecom.ResidentialIPv4 IPv6149
AS52468UFINET PANAMA S.A.UnclassifiedIPv462

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267797EMPRESA NACIONAL DE TRANSMISION ELECTRICA (ENATREL)UnclassifiedIPv41,266
AS263765XINWEI INTELCOM.NIC, S.A.UnclassifiedIPv453

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv41,865
AS267797EMPRESA NACIONAL DE TRANSMISION ELECTRICA (ENATREL)UnclassifiedIPv41,569
AS11830Instituto Costarricense de Electricidad y Telecom.ResidentialIPv4 IPv6202
AS52468UFINET PANAMA S.A.UnclassifiedIPv462
AS263765XINWEI INTELCOM.NIC, S.A.UnclassifiedIPv453

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.