asn.dev

Observed topology

AS24989 EQUINIX-CONNECT-GERMANY Equinix Germany

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24989: 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
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4479
AS35280F5 Networks SARLHostingIPv4118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39588Mimecast Services LimitedUnclassifiedIPv4 IPv6163
AS26063Alcon Labs, Inc.UnclassifiedIPv460
AS13806NCR Voyix CorporationUnclassifiedIPv454

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6756
AS39588Mimecast Services LimitedUnclassifiedIPv4 IPv6163
AS35280F5 Networks SARLHostingIPv4118
AS26063Alcon Labs, Inc.UnclassifiedIPv460
AS13806NCR Voyix CorporationUnclassifiedIPv454

Provenance

Where this comes from

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