TL;DR: Always use only the single IP shown in the specific API importer. The IPs listed below are technically used but usually do not need to be manually added. If whitelisting still fails, delete the job and create a new one with the freshly displayed IP (see troubleshooting section below).
CoinTracking uses multiple IP addresses to retrieve transactions via exchange APIs.
Some exchanges offer IP whitelisting for their APIs.
Important: You do not need to add all IP addresses anymore. Instead, use only the IP shown directly in the respective API importer (e.g. Bitvavo, KuCoin, Binance).
Full List of exchanges:
Backpack
Binance
Bitget
Bitmart
Bitrue
Bitunix
Bitvavo
Bitvavo by Hyphe
BlockFin
BloFin
Bybit Unified
CoinEx
Gemini
Kraken
KuCoin
MEXC
OKX
One Trading
Phemex
Poloniex
WEEX
WooX
The following IPs are used by CoinTracking:
63.32.3.10 63.32.21.240 34.254.117.125
Comma separated for easier copy and paste: 63.32.3.10,63.32.21.240,34.254.117.125
On exchanges* with strong API restrictions (e.g. Binance, KuCoin, Gate.io), calls can also be made via the following IPs:
18.202.210.42, 18.202.90.187, 18.203.26.123, 34.241.219.17, 34.248.103.244, 52.18.20.232, 52.50.200.166, 63.32.177.239, 63.33.123.58, 63.34.82.235, 18.203.76.129, 3.251.22.30, 3.248.77.147, 54.155.19.138, 54.155.85.51, 54.171.4.84, 54.217.61.91, 54.72.124.90, 52.18.43.25, 54.155.82.146, 54.228.189.212, 54.72.61.106, 52.19.131.128, 54.74.133.229, 54.247.149.100, 52.18.74.165, 54.77.179.30, 52.212.217.93, 52.30.115.202, 52.51.126.45, 52.31.170.238, 54.74.215.87, 54.75.228.192, 54.75.92.101, 108.128.186.127, 52.19.9.31, 52.30.70.110, 54.154.215.131, 3.248.239.243, 18.200.78.43, 52.19.155.226, 54.155.253.67, 34.249.59.170, 54.170.122.235, 54.228.133.152, 54.246.25.102, 63.32.12.84, 54.195.121.16, 63.33.231.214, 79.125.14.40, 108.128.163.76, 52.50.130.226, 52.16.219.214, 18.203.145.5, 52.211.51.184, 3.251.9.71, 34.243.225.67, 34.246.249.62, 46.51.161.213, 52.16.228.51
We retain the right to change these addresses in the future if necessary or add additional addresses.
What to do if IP whitelisting fails?
If you have whitelisted an IP on the exchange side but the API connection still doesn't work (e.g. you still get an IP-restriction error), the IP shown in the importer may have changed in the meantime. In that case:
- Delete the existing job/API key in CoinTracking for that exchange.
- Reload the CoinTracking page so the importer displays the currently active IP address.
- Create a new API connection (new job/key) using this newly displayed IP, and whitelist that IP on the exchange.
This ensures you're always whitelisting the IP that CoinTracking is actually using at that moment, rather than an outdated one.
Last Update: June 2026