asn.dev

Observed topology

AS264496 AS264496 - Fibralink LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264496: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv61,412
AS6939Hurricane Electric LLCTransitIPv4 IPv6365
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv659
AS24482SG.GSHostingIPv4 IPv633
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv421

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266568MBG TECNOLOGIA LTDA EPPResidentialIPv4 IPv6225
AS268057J C G SILVA INFORMATICA EIRELIUnclassifiedIPv4 IPv664
AS61776Provedor de Acesso a Internet EireliUnclassifiedIPv4 IPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv61,681
AS6939Hurricane Electric LLCTransitIPv4 IPv6384
AS266568MBG TECNOLOGIA LTDA EPPResidentialIPv4 IPv6225
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv688
AS268057J C G SILVA INFORMATICA EIRELIUnclassifiedIPv4 IPv664
AS24482SG.GSHostingIPv4 IPv636
AS61776Provedor de Acesso a Internet EireliUnclassifiedIPv4 IPv632
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv422

Provenance

Where this comes from

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