asn.dev

Observed topology

AS23487 CONECEL

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23487: 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
AS1299Arelion Sweden ABTransitIPv4 IPv68,521
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6877
AS174Cogent Communications, LLCTransitIPv4 IPv6667
AS12684SES ASTRA S.A.ResidentialIPv4 IPv694
AS3257GTT Communications Inc.TransitIPv4 IPv675
AS12252America Movil Peru S.A.C.MobileIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27738Ecuadortelecom S.A.UnclassifiedIPv4 IPv623,868
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv63,327
AS27998Contecon Guayaquil S.A.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS27738Ecuadortelecom S.A.UnclassifiedIPv4 IPv623,868
AS3257GTT Communications Inc.TransitIPv4 IPv614,427
AS1299Arelion Sweden ABTransitIPv4 IPv613,436
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv610,182
AS174Cogent Communications, LLCTransitIPv4 IPv610,051
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv66,310
AS12684SES ASTRA S.A.ResidentialIPv4 IPv694
AS27998Contecon Guayaquil S.A.UnclassifiedIPv459
AS12252America Movil Peru S.A.C.MobileIPv4 IPv627

Provenance

Where this comes from

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