asn.dev

Observed topology

AS264387 AS264387 - OZONIO TELECOMUNICACOES LTDA

Unclassified LACNIC

Upstreams 3 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 2
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.

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6186
AS26615TIM S/AMobileIPv633
AS264470Logic Pro TecnologiaResidentialIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6186
AS26615TIM S/AMobileIPv4 IPv652
AS264470Logic Pro TecnologiaResidentialIPv422
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv416
AS263450NORTE BRASIL NETWORK TELECOMUNICACOES LTDAUnclassifiedIPv43

Provenance

Where this comes from

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