asn.dev

Observed topology

AS264477 FLIX TELECOM

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264477: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6403
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv4 IPv6192
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv672
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv671
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv617
AS3303Swisscom (Schweiz) AGResidentialIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS275670ASSOCIACAO EDUCACIONAL DOM BOSCOUnclassifiedIPv623

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6419
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv4 IPv6192
AS6939Hurricane Electric LLCTransitIPv4 IPv6127
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv672
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv672
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv460
AS275670ASSOCIACAO EDUCACIONAL DOM BOSCOUnclassifiedIPv623
AS24482SG.GSHostingIPv4 IPv617
AS3303Swisscom (Schweiz) AGResidentialIPv415

Provenance

Where this comes from

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