asn.dev

Observed topology

AS264963 AS264963 - LUMIAR TELECOMUNICACOES

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264963: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv490
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv686
AS262734TUX NET SERVICOS DE INFORMATICA LTDAResidentialIPv479
AS6939Hurricane Electric LLCTransitIPv418
AS24482SG.GSHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271130WABA PROVEDOR DE INTERNET LTDAUnclassifiedIPv4122
AS269396UNIR TELECOMUnclassifiedIPv625

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6481
AS28186ITS TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6236
AS269396UNIR TELECOMUnclassifiedIPv4 IPv6166
AS262734TUX NET SERVICOS DE INFORMATICA LTDAResidentialIPv4 IPv6144
AS271130WABA PROVEDOR DE INTERNET LTDAUnclassifiedIPv4122
AS265393FIRENET SERVICOS DE TELECOMUNICACOES LTDAUnclassifiedIPv648
AS271042BOT INTERNET E SERVICOS DE TELECOMUNICACOES LTDAUnclassifiedIPv646
AS6939Hurricane Electric LLCTransitIPv4 IPv642
AS262999IVI TECNOLOGIA E COMUNICACAO LTDAUnclassifiedIPv630
AS266181GOLDEN LINKResidentialIPv627

All 15 adjacent →

Provenance

Where this comes from

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