asn.dev

Observed topology

AS264773 GOZFLY S.A.

Unclassified LACNIC Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264773: 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
AS14754TELECOMUNICACIONES DE GUATEMALA, SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6239
AS263725MULTICABLE DE HONDURASUnclassifiedIPv4 IPv6147
AS6939Hurricane Electric LLCTransitIPv6100
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv681
AS263686INET CommunicationUnclassifiedIPv411
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54043GOZFLY LLCUnclassifiedIPv4 IPv689

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14754TELECOMUNICACIONES DE GUATEMALA, SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6299
AS263725MULTICABLE DE HONDURASUnclassifiedIPv4 IPv6152
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6106
AS6939Hurricane Electric LLCTransitIPv6100
AS54043GOZFLY LLCUnclassifiedIPv4 IPv689
AS263686INET CommunicationUnclassifiedIPv411
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv67
AS1Level 3 Parent, LLCUnclassifiedIPv43

Provenance

Where this comes from

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