asn.dev

Observed topology

AS264516 A.M.A TELECOM

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264516: 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
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6239
AS52468UFINET PANAMA S.A.UnclassifiedIPv4200
AS6939Hurricane Electric LLCTransitIPv4 IPv6170
AS264215W FIBRA TELECOM LTDAUnclassifiedIPv4 IPv667
AS265330Ponto a Ponto TelecomunicacoesUnclassifiedIPv4 IPv626
AS35280F5 Networks SARLHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61660CRAPAC SERVICOS DE TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6908
AS27697NITNET INFORMATICA S/C LTDA.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61660CRAPAC SERVICOS DE TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6908
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6721
AS52468UFINET PANAMA S.A.UnclassifiedIPv4456
AS6939Hurricane Electric LLCTransitIPv4 IPv6383
AS264215W FIBRA TELECOM LTDAUnclassifiedIPv4 IPv682
AS27697NITNET INFORMATICA S/C LTDA.UnclassifiedIPv460
AS265330Ponto a Ponto TelecomunicacoesUnclassifiedIPv4 IPv626
AS35280F5 Networks SARLHostingIPv64

Provenance

Where this comes from

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