LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

147.123.36.0/22

No anonymizer space · no proxy exits in 30 days

Equinix (EMEA) Acquisition Enterprises B.V. · space held by Equinix (Netherlands) Enterprises BV

Announcement
this exact prefix
RPKI valid
Announced by
AS15830
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
147.123.0.0/1665,536EQUINIX-147-123-0-0Equinix (Netherlands) Enterprises BV (ORG-EEB6-RIPE) · NLLEGACYFeb 5, 2009smc@equinix.com
└ 147.123.36.0/221,024EQUINIX-AM-137-174-40-0-22Equinix (Netherlands) B.V. (ORG-EB17-RIPE) · NLLEGACYSep 25, 2023smc@equinix.com
└ 147.123.36.16/2816IN_COMMODITIES_A_SEquinix Customer - In Commodities A/SLEGACYMay 1, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.32/304HARBERS_ASP_B_VEquinix Customer - Harbers Asp B.V.LEGACYMay 16, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.36/304HARBERS_ASP_B_VEquinix Customer - Harbers Asp B.V.LEGACYMay 21, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.40/304EQUINIX_NETHERLANDS_BVEquinix Customer - Equinix (Netherlands) BVLEGACYJun 10, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.44/304EQUINIX_NETHERLANDS_BVEquinix Customer - Equinix (Netherlands) BVLEGACYJun 10, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.48/304EQUINIX_MANAGED_SERVICES_NLEquinix Customer - Equinix Managed Services (NL)LEGACYJun 11, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.52/304EQUINIX_MANAGED_SERVICES_NLEquinix Customer - Equinix Managed Services (NL)LEGACYJun 11, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.56/304EQUINIX_NETHERLANDS_BVEquinix Customer - Equinix (Netherlands) BVLEGACYJun 11, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.60/304EQUINIX_NETHERLANDS_BVEquinix Customer - Equinix (Netherlands) BVLEGACYJun 11, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.64/304EQUINIX_NETHERLANDSEquinix Customer - Equinix (Netherlands)LEGACYSep 13, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.68/304EQUINIX_NETHERLANDSEquinix Customer - Equinix (Netherlands)LEGACYSep 16, 2024smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.72/304EQUINIX_MANAGED_SERVICESEquinix Customer - Equinix Managed ServicesLEGACYJan 20, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.76/304EQUINIX_MANAGED_SERVICESEquinix Customer - Equinix Managed ServicesLEGACYJan 20, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.80/298EQUINIX_MANAGED_SERVICESEquinix Customer - Equinix Managed ServicesLEGACYJan 20, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.88/304EQUINIX_NETHERLANDSEquinix Customer - Equinix (Netherlands)LEGACYJan 21, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.92/304EQUINIX_NETHERLANDSEquinix Customer - Equinix (Netherlands)LEGACYJan 21, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.96/298EQUINIX_NETHERLANDSEquinix Customer - Equinix (Netherlands)LEGACYJan 21, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.104/304KONINKLIJKEEquinix Customer - KoninklijkeLEGACYMay 12, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.108/304KLMEquinix Customer - KLMLEGACYMay 12, 2025smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.112/298STICHTING_SINTEquinix Customer - Stichting SintLEGACYApr 21, 2026smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.120/298STICHTING_SINTEquinix Customer - Stichting SintLEGACYApr 21, 2026smc@equinix.com
via EQUINIX-AM-137-174-40-0-22
└ 147.123.36.128/298STICHTING_SINT_MAARTENSKLINIEKEquinix Customer - Stichting Sint MaartenskliniekLEGACYMay 13, 2026smc@equinix.com
via EQUINIX-AM-137-174-40-0-22

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2023
Current origin since
Oct 2023 · 3.1 yr
Origin networks
1