asn.dev

Observed topology

AS264009 AS264009 - INFIX TELECOM LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264009: 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
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6508
AS262417UltraTelecom Provedora de InternetUnclassifiedIPv4 IPv6234
AS6939Hurricane Electric LLCTransitIPv4110
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv496
AS24482SG.GSHostingIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263059Cleber Luciano dos AnjosUnclassifiedIPv4 IPv6771
AS264336Bloom telecomunicacoes LTDAUnclassifiedIPv4 IPv6464
AS271176BLUVELLOX TELECOMUNICACOES LTDAUnclassifiedIPv439
AS52737Floriani Servicos de Telecomunicacao Ltda MEUnclassifiedIPv417

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28343UNIFIQUE TELECOMUNICACOES S/AUnclassifiedIPv4 IPv61,268
AS263059Cleber Luciano dos AnjosUnclassifiedIPv4 IPv6771
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6550
AS264336Bloom telecomunicacoes LTDAUnclassifiedIPv4 IPv6464
AS262417UltraTelecom Provedora de InternetUnclassifiedIPv4 IPv6234
AS6939Hurricane Electric LLCTransitIPv4 IPv6184
AS271176BLUVELLOX TELECOMUNICACOES LTDAUnclassifiedIPv439
AS52737Floriani Servicos de Telecomunicacao Ltda MEUnclassifiedIPv417
AS24482SG.GSHostingIPv4 IPv66

Provenance

Where this comes from

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