asn.dev

Observed topology

AS267797 EMPRESA NACIONAL DE TRANSMISION ELECTRICA ENATREL

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267797: 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 IPv61,746
AS264609TECOMUNICA NICARAGUAUnclassifiedIPv41,379

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25607IBW CommunicationsUnclassifiedIPv4815
AS263765XINWEI INTELCOM.NIC, S.A.UnclassifiedIPv4 IPv6394
AS264609TECOMUNICA NICARAGUAUnclassifiedIPv4174
AS274013SERVICIOS DE INTERNET Y TELECOMUNICACIONES SOCIEDAD ANONIMAUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv63,483
AS264609TECOMUNICA NICARAGUAUnclassifiedIPv41,730
AS263765XINWEI INTELCOM.NIC, S.A.UnclassifiedIPv4 IPv6833
AS25607IBW CommunicationsUnclassifiedIPv4815
AS274013SERVICIOS DE INTERNET Y TELECOMUNICACIONES SOCIEDAD ANONIMAUnclassifiedIPv4 IPv692

Provenance

Where this comes from

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