asn.dev

Observed topology

AS262202 Telefonica de Costa Rica TC, SA

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262202: 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
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv61,599
AS52228Cable TicaUnclassifiedIPv4145

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28110NAVEGALO S.A.HostingIPv4 IPv6249
AS263713Server Lodge S.A.UnclassifiedIPv4 IPv6184
AS265873FIBER TO THE HOME FTTH SAUnclassifiedIPv4177
AS3573Accenture LLPUnclassifiedIPv4 IPv6123
AS52392Grupo Telco de Centroamerica S.A.ResidentialIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv62,349
AS28110NAVEGALO S.A.HostingIPv4 IPv6249
AS52228Cable TicaUnclassifiedIPv4220
AS263713Server Lodge S.A.UnclassifiedIPv4 IPv6184
AS265873FIBER TO THE HOME FTTH SAUnclassifiedIPv4177
AS3573Accenture LLPUnclassifiedIPv4 IPv6123
AS52392Grupo Telco de Centroamerica S.A.ResidentialIPv4 IPv692

Provenance

Where this comes from

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