asn.dev

Observed topology

AS22869 CABLECOLOR S.A.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22869: 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
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv61,243
AS23520Columbus Networks USA, Inc.ResidentialIPv4551

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27884CABLECOLOR S.A.UnclassifiedIPv4 IPv67,428
AS27729Globalnet.hnUnclassifiedIPv4 IPv61,652
AS264637Blue Consulting Group, S. A.ResidentialIPv4375
AS28049ISP SOLUTIONS S.A.UnclassifiedIPv4137
AS273884SISTECOM, S.A.UnclassifiedIPv458
AS269830ESTRATEGIAS Y TELECOMUNICACIONES S.A. (ETELECOM)UnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv612,498
AS27884CABLECOLOR S.A.UnclassifiedIPv4 IPv68,665
AS27729Globalnet.hnUnclassifiedIPv4 IPv62,050
AS23520Columbus Networks USA, Inc.ResidentialIPv4823
AS264637Blue Consulting Group, S. A.ResidentialIPv4 IPv6610
AS28049ISP SOLUTIONS S.A.UnclassifiedIPv4137
AS273884SISTECOM, S.A.UnclassifiedIPv458
AS269830ESTRATEGIAS Y TELECOMUNICACIONES S.A. (ETELECOM)UnclassifiedIPv47

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.