asn.dev

Observed topology

AS264054 AS264054 - FALCON COMUNICACOES E INFORMATICA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264054: 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
AS266094CONEXAO MB E TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv651
AS263390FNT Telecomunicacoes e Acesso a Redes de InternetResidentialIPv4 IPv642
AS35280F5 Networks SARLHostingIPv4 IPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272619FIVE TELECOM LTDAUnclassifiedIPv4 IPv6251
AS271263GILEADE TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv4 IPv69

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS272619FIVE TELECOM LTDAUnclassifiedIPv4 IPv6251
AS263390FNT Telecomunicacoes e Acesso a Redes de InternetResidentialIPv4 IPv6208
AS266094CONEXAO MB E TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6145
AS271263GILEADE TELECOMUNICACOES E MULTIMIDIA LTDAUnclassifiedIPv4 IPv69
AS35280F5 Networks SARLHostingIPv4 IPv68

Provenance

Where this comes from

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