Overview

Fireblocks' cloud services are used by all Fireblocks customers that connect to third-party services such as exchanges, fiat providers, anti-money laundering (AML) vendors, and tokenization providers. Third-party services see a limited list of IP addresses as the network connection source.

In some cases, third-party services require specifying the incoming IP address or addresses when configuring an API Key for use with a Fireblocks workspace. The third-party service can then allow connections from the specified IP address using your API Key.

Fireblocks step-by-step exchange connection guides explicitly include the relevant IP addresses. For example, see the Binance connection guide.

Some third-party services do not require specifying any IP addresses. However, limiting the source IP addresses for an API Key to only come from the Fireblocks platform is preferred for security.

Future changes to IP addresses

Occasionally, Fireblocks identifies that additional IP addresses are needed for new and existing customers. This may occur when Fireblocks detects that a third-party service cannot handle the volume of requests by parallel customers from a single IP address.

• Fireblocks will change the default source IP addresses for any new or existing user that adds another third-party account.

• Fireblocks will update the IP address list on this page and in any relevant connection guides.

• Existing customers can still access the third-party service using the original IP addresses that were provided to them during the initial setup and integration. Existing customers usually do not need to modify their third-party account configurations. However, if they experience failed exchange requests such as retrieving accurate balances, initiating withdrawals, or other transactions, they should create a new API Key with the updated IP addresses. Once the new API key is created, they can delete the existing exchange connection from their Fireblocks Console and add the account again with the new API Key.