asn.dev

Observed topology

AS26613 AS26613 - CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EP

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26613: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6138
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4131

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28006CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv4 IPv644,854
AS28025CENTROSURUnclassifiedIPv4312
AS16550Google LLCUnclassifiedIPv4120

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28006CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv4 IPv645,597
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv626,789
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv619,509
AS28025CENTROSURUnclassifiedIPv4312
AS16550Google LLCUnclassifiedIPv4120

Provenance

Where this comes from

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