asn.dev

Observed topology

AS52580 Azion Technologies Ltda.

Hosting AFRINIC Content

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS52580: 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
AS60068Datacamp LimitedHostingIPv4 IPv6762
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6453
AS174Cogent Communications, LLCTransitIPv4 IPv6407
AS1299Arelion Sweden ABTransitIPv4 IPv6295
AS4455IX Reach LtdUnclassifiedIPv4 IPv6161
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6158
AS18747IFX CorporationUnclassifiedIPv4 IPv6125
AS6939Hurricane Electric LLCTransitIPv4 IPv6123
AS27988Servicios y Telecomunicaciones S.A.ResidentialIPv4 IPv692
AS28283Adylnet TelecomResidentialIPv4 IPv692

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6762
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6453
AS174Cogent Communications, LLCTransitIPv4 IPv6407
AS1299Arelion Sweden ABTransitIPv4 IPv6295
AS4455IX Reach LtdUnclassifiedIPv4 IPv6161
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6158
AS18747IFX CorporationUnclassifiedIPv4 IPv6125
AS6939Hurricane Electric LLCTransitIPv4 IPv6123
AS27988Servicios y Telecomunicaciones S.A.ResidentialIPv4 IPv692
AS28283Adylnet TelecomResidentialIPv4 IPv692

Provenance

Where this comes from

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