asn.dev

Observed topology

AS27678 NIC Chile

Hosting AFRINIC Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27678: 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
AS14259Gtd Internet S.A.ResidentialIPv4 IPv6563
AS18747IFX CorporationUnclassifiedIPv640
AS6429Telmex Chile Internet S.A.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52305NIC ChileUnclassifiedIPv4 IPv617
AS52234NIC ChileUnclassifiedIPv410
AS52306NIC ChileUnclassifiedIPv410
AS52304NIC ChileUnclassifiedIPv47
AS61455LACTLD - LATIN AMERICAN AND CARIBBEAN TLD ASSOCIATIONHostingIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14259Gtd Internet S.A.ResidentialIPv4 IPv6626
AS18747IFX CorporationUnclassifiedIPv643
AS52305NIC ChileUnclassifiedIPv4 IPv617
AS28377Network Information Center MexicoUnclassifiedIPv4 IPv616
AS52234NIC ChileUnclassifiedIPv410
AS52306NIC ChileUnclassifiedIPv410
AS52304NIC ChileUnclassifiedIPv47
AS61455LACTLD - LATIN AMERICAN AND CARIBBEAN TLD ASSOCIATIONHostingIPv46
AS6429Telmex Chile Internet S.A.UnclassifiedIPv61

Provenance

Where this comes from

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