Observed topology

AS264106 ANDRADE & LANDIM TELECOMUNICACOES LTDA

Unclassified AFRINIC

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264106: 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
AS264409	Huge Solucoes Corporativas Ltda	Unclassified	IPv4	232
AS7738	V tal	Unclassified	IPv4	105
AS28306	Voluy Telecom Eireli	Unclassified	IPv4	52
AS52531	G6 Internet	Unclassified	IPv4	48

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270616	Carlos Eduardo de Carvalho Silva ME	Unclassified	IPv4	250
AS264427	FUNDACAO INSTITUTO NACIONAL DE TELECOMUNICACOES	Education	IPv4	108

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS264409	Huge Solucoes Corporativas Ltda	Unclassified	IPv4	392
AS270616	Carlos Eduardo de Carvalho Silva ME	Unclassified	IPv4	250
AS7738	V tal	Unclassified	IPv4	210
AS28306	Voluy Telecom Eireli	Unclassified	IPv4	119
AS264427	FUNDACAO INSTITUTO NACIONAL DE TELECOMUNICACOES	Education	IPv4	108
AS52531	G6 Internet	Unclassified	IPv4	74

Provenance

Where this comes from

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