Observed topology

AS264404 NETGOOL TELECOMUNICACOES

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264404: 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
AS28186	ITS TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	134
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	77
AS1031	PEER 1031 LLC	Unclassified	IPv4	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS264881	NTG COMUNICACOES LTDA	Unclassified	IPv4 IPv6	110
AS268177	D & B TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	40
AS273391	PROVNET SERVICOS DE TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	34

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS28186	ITS TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	333
AS264881	NTG COMUNICACOES LTDA	Unclassified	IPv4 IPv6	110
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	94
AS268177	D & B TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	78
AS273391	PROVNET SERVICOS DE TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	34
AS1031	PEER 1031 LLC	Unclassified	IPv4	18

Provenance

Where this comes from

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