asn.dev

Observed topology

AS269804 AS269804 - SEPCOM COMUNICACIONES SAS

Unclassified AFRINIC Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269804: 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 IPv6324
AS18678INTERNEXA S.A. E.S.PUnclassifiedIPv4 IPv6152
AS52468UFINET PANAMA S.A.UnclassifiedIPv442

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266737UNIVERSIDAD DEL CAUCAUnclassifiedIPv4 IPv6253
AS269893NETWORK CONNEXIONS SASUnclassifiedIPv4 IPv6180
AS272978ORINOCO VENTURES GROUP SASUnclassifiedIPv4 IPv694
AS267796BETEL SOLUCIONES S.A.SUnclassifiedIPv4 IPv662
AS273168INFRAESTRUCTURA Y REDES SASUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv6507
AS18678INTERNEXA S.A. E.S.PUnclassifiedIPv4 IPv6383
AS266737UNIVERSIDAD DEL CAUCAUnclassifiedIPv4 IPv6253
AS52468UFINET PANAMA S.A.UnclassifiedIPv4218
AS269893NETWORK CONNEXIONS SASUnclassifiedIPv4 IPv6180
AS272978ORINOCO VENTURES GROUP SASUnclassifiedIPv4 IPv694
AS267796BETEL SOLUCIONES S.A.SUnclassifiedIPv4 IPv662
AS273168INFRAESTRUCTURA Y REDES SASUnclassifiedIPv61

Provenance

Where this comes from

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