Data as of Nov 22, 2026

137.174.208.0/21

1 residential-proxy exit · 30 days

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

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recent change
New origin Jul 2026
its first announcement on record

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
2
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • Byteful
  • Oxylabs

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
137.174.0.0/1665,536EQUINIX-137-174-0-0Equinix (Netherlands) Enterprises BV (ORG-EEB6-RIPE) · NLLEGACY—smc@equinix.com
└ 137.174.214.0/298Equinix_IndiaunknownLEGACYJul 30, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.16/298Telstra_Telecommunications_Private_Limited_NvidiaEquinix Customer - Telstra Telecommunications Private Limited - NvidiaLEGACYSep 1, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.24/304NXP_INDIA_PRIVATE_LIMITEDunknownLEGACYSep 1, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.28/304NXP_INDIA_PRIVATE_LIMITEDunknownLEGACYSep 1, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.40/298Telstra_Telecommunications_Private_Limited_NvidiaEquinix Customer - Telstra Telecommunications Private Limited - NvidiaLEGACYSep 2, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.84/304Tucows_India_Private_LimitedEquinix Customer - Tucows (India) Private LimitedLEGACYOct 9, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.88/298Eqvilent_Investments_LtdEquinix Customer - Eqvilent Investments LtdLEGACYOct 8, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.96/298Xonware_Technologies_Pvt_LtdEquinix Customer - Xonware Technologies Pvt LtdLEGACYOct 14, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.112/304DAZN_SOFTWARE_PRIVATE_LIMITEDEquinix Customer - DAZN SOFTWARE PRIVATE LIMITEDLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.116/304DAZN_SOFTWARE_PRIVATE_LIMITEDEquinix Customer - DAZN SOFTWARE PRIVATE LIMITEDLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.120/298DAZN_SOFTWARE_PRIVATE_LIMITEDEquinix Customer - DAZN SOFTWARE PRIVATE LIMITEDLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.128/304Equinix_customerEquinix Customer - 46 Labs, IncLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.132/304Equinix_customerEquinix Customer - 46 Labs, IncLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0
└ 137.174.214.136/298Equinix_customerEquinix Customer - 46 Labs, IncLEGACYNov 11, 2026smc@equinix.com
via EQUINIX-137-174-0-0

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

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2026
Current origin since
Jul 2026 · 4 mo
Origin networks
1