Observed topology

AS264387 OZONIO TELECOMUNICACOES LTDA

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264387: 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
AS4230	CLARO S.A.	Residential	IPv4 IPv6	190
AS26615	TIM S/A	Mobile	IPv6	34
AS264470	Logic Pro Tecnologia	Residential	IPv4	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268293	Tribunal Regional do Trabalho - 11a Regiao	Unclassified	IPv4	58
AS263450	NORTE BRASIL NETWORK TELECOMUNICACOES LTDA	Unclassified	IPv4	5
AS262663	METROFLEX TELECOMUNICACOES LTDA	Unclassified	IPv6	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4230	CLARO S.A.	Residential	IPv4 IPv6	248
AS268293	Tribunal Regional do Trabalho - 11a Regiao	Unclassified	IPv4	58
AS26615	TIM S/A	Mobile	IPv4 IPv6	42
AS264470	Logic Pro Tecnologia	Residential	IPv4	22
AS263450	NORTE BRASIL NETWORK TELECOMUNICACOES LTDA	Unclassified	IPv4	7
AS262663	METROFLEX TELECOMUNICACOES LTDA	Unclassified	IPv6	1

Provenance

Where this comes from

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