asn.dev

Observed topology

AS27986 ENTEL CHILE S.A.

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27986: 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 IPv6230
AS262589SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4111
AS3356Level 3 Parent, LLCTransitIPv4 IPv6107
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv633

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27651ENTEL CHILE S.A.ResidentialIPv4 IPv662,820
AS6471ENTEL CHILE S.A.ResidentialIPv43,880
AS27925Entel PCS Telecomunicaciones S.A.UnclassifiedIPv41,080

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS27651ENTEL CHILE S.A.ResidentialIPv4 IPv662,820
AS3356Level 3 Parent, LLCTransitIPv4 IPv622,296
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv621,438
AS262589SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv414,856
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv611,620
AS6471ENTEL CHILE S.A.ResidentialIPv45,829
AS27925Entel PCS Telecomunicaciones S.A.UnclassifiedIPv41,080

Provenance

Where this comes from

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