Observed topology

AS10778 MCL Internet

Residential LACNIC

Upstreams 4 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

Upstream graph Who carries AS10778, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS10778 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10778: 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.

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	468
AS6939	Hurricane Electric LLC	Transit	IPv4	115
AS18747	IFX Corporation	Unclassified	IPv4	73
AS19338	Telmex Chile Internet S.A.	Unclassified	IPv4	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS4995	Netup S.A.	Unclassified	IPv4	986
AS52246	INDEXA S A	Unclassified	IPv4	96
AS21711	Maxtel USA Corp	Unclassified	IPv4	58
AS64121	Virtualiza S.A	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	1,116
AS4995	Netup S.A.	Unclassified	IPv4	986
AS18747	IFX Corporation	Unclassified	IPv4	509
AS6939	Hurricane Electric LLC	Transit	IPv4	124
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4	106
AS52246	INDEXA S A	Unclassified	IPv4	96
AS21711	Maxtel USA Corp	Unclassified	IPv4	58
AS64121	Virtualiza S.A	Unclassified	IPv4	57
AS19338	Telmex Chile Internet S.A.	Unclassified	IPv4	6
AS21838	CIRION TECHNOLOGIES ARGENTINA S.A.	Unclassified	IPv4	2

Provenance

Where this comes from

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