asn.dev

Observed topology

AS28006 CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EP

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28006: 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
AS26613CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv4 IPv644,795

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27757CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPMobileIPv4417
AS52331CORPORACION FINANCIERA NACIONALUnclassifiedIPv4107
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS23031TELECU TELECOMUNICACIONES DEL ECUADOR TELECUSA S.A.S.ResidentialIPv463
AS28011CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS26613CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv4 IPv645,537
AS27757CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPMobileIPv4417
AS52331CORPORACION FINANCIERA NACIONALUnclassifiedIPv4107
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS23031TELECU TELECOMUNICACIONES DEL ECUADOR TELECUSA S.A.S.ResidentialIPv465
AS28011CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EPUnclassifiedIPv460

Provenance

Where this comes from

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