Observed topology

AS268464 IAGO GUERRA RESENDE COMUNICACOES - ME

Unclassified LACNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 3

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268464: 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
AS52965	1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA	Unclassified	IPv4 IPv6	237
AS270946	ULTRANET PROVEDOR CUSTODIA LTDA	Unclassified	IPv4 IPv6	62
AS267332	PROVEDOR NET MAIS LTDA - ME	Residential	IPv4 IPv6	50
AS28598	DB3 SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv6	31

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270946	ULTRANET PROVEDOR CUSTODIA LTDA	Unclassified	IPv6	27

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS52965	1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA	Unclassified	IPv4 IPv6	237
AS270946	ULTRANET PROVEDOR CUSTODIA LTDA	Unclassified	IPv4 IPv6	89
AS28598	DB3 SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv6	58
AS267332	PROVEDOR NET MAIS LTDA - ME	Residential	IPv4 IPv6	50

Provenance

Where this comes from

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