asn.dev

Observed topology

AS18809 Cable Onda

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18809: 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
AS262206COMCEL GUATEMALA S.A.UnclassifiedIPv4 IPv642,640
AS3356Level 3 Parent, LLCTransitIPv4118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14709Cable OndaUnclassifiedIPv41,865
AS13335Cloudflare, Inc.HostingIPv4 IPv692
AS21599Cable OndaUnclassifiedIPv459
AS26105Cable OndaUnclassifiedIPv456

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262206COMCEL GUATEMALA S.A.UnclassifiedIPv4 IPv645,659
AS14709Cable OndaUnclassifiedIPv41,925
AS26105Cable OndaUnclassifiedIPv4 IPv6945
AS3356Level 3 Parent, LLCTransitIPv4118
AS21599Cable OndaUnclassifiedIPv4116
AS13335Cloudflare, Inc.HostingIPv4 IPv692
AS264788Telconet S.AUnclassifiedIPv459

Provenance

Where this comes from

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