Observed topology

AS17400 MSTelcom-Mercury Servicos de Telecomunicacoes, S.A.R.L - MSTelcom-Mercury Servicos de Telecomunicacoes, S.A.R.L

Residential LACNIC Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17400: 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
AS37468	Angola Cables	Unclassified	IPv4 IPv6	3,784
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	329

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS36917	Angola Comunicacoes & Systems LDA	Unclassified	IPv4	180
AS36976	Sonangol	Unclassified	IPv4	134
AS329564	Agencia Nacional de Pertoleo, Gas e Biocombustiveis	Unclassified	IPv4	60
AS10798	The Standard Bank of South Africa (Proprietary) Limited	Unclassified	IPv4	15
AS328283	Banco de Poupança e Crédito S.A	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS37468	Angola Cables	Unclassified	IPv4 IPv6	4,207
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	345
AS36917	Angola Comunicacoes & Systems LDA	Unclassified	IPv4	180
AS36976	Sonangol	Unclassified	IPv4	134
AS329564	Agencia Nacional de Pertoleo, Gas e Biocombustiveis	Unclassified	IPv4	60
AS33763	Paratus Telecommunications Limited	Unclassified	IPv4	45
AS10798	The Standard Bank of South Africa (Proprietary) Limited	Unclassified	IPv4	15
AS328283	Banco de Poupança e Crédito S.A	Unclassified	IPv4	5

Provenance

Where this comes from

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