Observed topology

AS27924 AMPLIA COMMUNICATIONS LTD.

Residential LACNIC

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27924: 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
AS6762	TELECOM ITALIA SPARKLE S.p.A.	Transit	IPv4	1,071
AS5639	Telecommunication Services of Trinidad and Tobago	Residential	IPv4 IPv6	1,018
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	469
AS6939	Hurricane Electric LLC	Transit	IPv4	352
AS24482	SG.GS	Hosting	IPv4	33

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS14789	Cloudflare, Inc.	Unclassified	IPv4 IPv6	91
AS264811	AIR LINK COMMUNICATIONS	Residential	IPv4 IPv6	90
AS17044	THE INTERPUBLIC GROUP OF COMPANIES, INC.	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6762	TELECOM ITALIA SPARKLE S.p.A.	Transit	IPv4	1,167
AS5639	Telecommunication Services of Trinidad and Tobago	Residential	IPv4 IPv6	1,023
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4 IPv6	608
AS6939	Hurricane Electric LLC	Transit	IPv4	352
AS14789	Cloudflare, Inc.	Unclassified	IPv4 IPv6	91
AS264811	AIR LINK COMMUNICATIONS	Residential	IPv4 IPv6	90
AS17044	THE INTERPUBLIC GROUP OF COMPANIES, INC.	Unclassified	IPv4	59
AS24482	SG.GS	Hosting	IPv4	33

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.