asn.dev

Observed topology

AS57624 BeeksFX Beeks Financial Cloud Ltd

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57624: 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
AS1299Arelion Sweden ABTransitIPv4320
AS174Cogent Communications, LLCTransitIPv4190
AS53427TGLOBAL NETWORKSUnclassifiedIPv457
AS34549meerfarbig GmbH & Co. KGHostingIPv430
AS22652Videotron LteeResidentialIPv420
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29697BeeksFX VPS USA Inc.HostingIPv449
AS396886BeeksFX VPS USA Inc.UnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4361
AS174Cogent Communications, LLCTransitIPv4204
AS53427TGLOBAL NETWORKSUnclassifiedIPv457
AS29697BeeksFX VPS USA Inc.HostingIPv449
AS34549meerfarbig GmbH & Co. KGHostingIPv433
AS22652Videotron LteeResidentialIPv422
AS396886BeeksFX VPS USA Inc.UnclassifiedIPv413
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv43

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.