asn.dev

Observed topology

AS264806 AS264806 - TNA Solutions SpA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264806: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4284
AS266830AIRPOINT TELECOMUNICACIONES LIMITADAUnclassifiedIPv488
AS6939Hurricane Electric LLCTransitIPv4 IPv668

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266866CONECTIVIDAD Y REDES ROBERTO ROMULO CANDIA CANDIA EIRLUnclassifiedIPv4404
AS273019DIRECTV CHILE TELEVISION LIMITADAUnclassifiedIPv6160
AS266887SOCIEDAD GAMACON LIMITADAResidentialIPv455
AS266830AIRPOINT TELECOMUNICACIONES LIMITADAUnclassifiedIPv452

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6903
AS266866CONECTIVIDAD Y REDES ROBERTO ROMULO CANDIA CANDIA EIRLUnclassifiedIPv4404
AS273019DIRECTV CHILE TELEVISION LIMITADAUnclassifiedIPv6160
AS266830AIRPOINT TELECOMUNICACIONES LIMITADAUnclassifiedIPv4140
AS6939Hurricane Electric LLCTransitIPv4 IPv668
AS266887SOCIEDAD GAMACON LIMITADAResidentialIPv455
AS52468UFINET PANAMA S.A.UnclassifiedIPv452

Provenance

Where this comes from

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