New Gainium server IPs — update your exchange API whitelist

Announcements
1

We’ve expanded our server infrastructure and added five new IP addresses that Gainium uses to connect to your exchange.

If your exchange API key restricts access to specific IPs (IP whitelisting), you’ll need to add these new IPs so your bots and deals keep running without interruption.

Do I need to do anything?

No action needed if:

  • You connected Bybit, KuCoin, or OKX using the “Connect to third-party app”. These connections are configured automatically — the new IPs are already covered.
  • Your API key has no IP restriction at all (not recommended, but nothing to update).
  • Hyperliquid connections are not affected.

Action required if:

  • You created your API key manually and enabled IP whitelisting with our server IPs. This applies to manual connections on Binance, Binance.US, Coinbase, Kraken, Bitget, Bybit, KuCoin, and OKX.

If you’re not sure, it’s safest to check your API key settings on the exchange.

The new IPs to add

62.84.191.108
62.84.191.109
62.84.191.110
62.84.191.111
62.84.191.112

Important: You don’t need to delete your existing connection or recreate your API key. Just edit the existing key on the exchange and add the new IPs alongside the ones you already have.

The complete, up-to-date IP list

For reference, here is the full set of Gainium server IPs (existing + new). Your whitelist should contain all of these:

78.128.60.89
78.128.43.82
78.128.8.36
78.128.43.168
217.174.152.25
62.84.191.108
62.84.191.109
62.84.191.110
62.84.191.111
62.84.191.112

How to update (general steps)

  1. Log in to your exchange and open the API Management section.
  2. Find the API key you use with Gainium and choose Edit (do not delete it).
  3. In the IP restriction / whitelist field, add the five new IPs above to your existing list, separated however the exchange requires (commas or one per line).
  4. Save your changes.

Step-by-step guides per exchange:

What happens if I don’t update?

If we begin routing traffic through the new servers and they aren’t whitelisted, the exchange will reject those requests. Your bots and deals on that connection may stop placing or managing orders. Updating now ensures a seamless transition.

If you run into any trouble, reply here or reach out to support — we’re happy to help.

2 Likes
2

I didn’t specify any IP address on Bitget when I created the API key months ago. Do I need to take any action?

Kind regards, Wolfgang

3

Possibly no. If you didn’t receive an email regarding this it means your API keys are not affected.