asn.dev

Observed topology

AS264899 R L COMERCIO MANUTENCAO REPRESENTACAO DE ELETRO-E

Unclassified LACNIC

Upstreams 1 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 7
Upstream graph Who carries AS264899, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS264899 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264899: 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 IPv6265

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268257SIDI SERVICOS DE COMUNICACAO LTDA-MEUnclassifiedIPv4 IPv6617
AS270348Sidia Instituto de Ciencia e TecnologiaUnclassifiedIPv4 IPv6284
AS273781CONECT + FIBRAUnclassifiedIPv633
AS275844RMDSA1582UnclassifiedIPv632
AS270483OVERNET FIBRAUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv6965
AS268257SIDI SERVICOS DE COMUNICACAO LTDA-MEUnclassifiedIPv4 IPv6617
AS270348Sidia Instituto de Ciencia e TecnologiaUnclassifiedIPv4 IPv6284
AS26615TIM S/AMobileIPv4 IPv6268
AS273781CONECT + FIBRAUnclassifiedIPv4 IPv634
AS275844RMDSA1582UnclassifiedIPv632
AS270483OVERNET FIBRAUnclassifiedIPv61

Provenance

Where this comes from

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