asn.dev

Observed topology

AS58580 FASTRACK Fastrack Technology

Unclassified APNIC

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS58580: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6837
AS174Cogent Communications, LLCTransitIPv4448
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6228
AS2764AAPT LimitedUnclassifiedIPv4192
AS24324Kordia LimitedUnclassifiedIPv458
AS49915Megaport (UK) LimitedUnclassifiedIPv433
AS24482SG.GSHostingIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS64073Vetta GroupUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139736Apexhost Pty LtdUnclassifiedIPv4295

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6837
AS174Cogent Communications, LLCTransitIPv4448
AS2764AAPT LimitedUnclassifiedIPv4369
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6346
AS139736Apexhost Pty LtdUnclassifiedIPv4295
AS24324Kordia LimitedUnclassifiedIPv458
AS49915Megaport (UK) LimitedUnclassifiedIPv433
AS24482SG.GSHostingIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv412

Provenance

Where this comes from

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