V2 Shutdown and IP Whitelist Migration
Tealstreet is moving from the old AWS infrastructure to a new Vultr fleet in Tokyo. If your exchange API keys use Tealstreet IP whitelisting, update them to include the new IP addresses before the AWS shutdown on November 2, 2026 at 00:00 UTC.
Tealstreet is moving legacy infrastructure from AWS to a new Vultr Tokyo fleet. Most users only need to know which path applies to them:
- If you still use the old V2 terminal, move to V3 and add your exchange accounts there.
- If you already use V3 with Tealstreet IP whitelisting enabled, update the IP whitelist on each exchange API key during the overlap window.
- If you use V3 on multiple devices, turn on Cloud Sync for API Keys before the cutover so the same Tealstreet API key list is available everywhere you sign in.
Which one am I?
I use V2
You are a V2 user if you still trade from the old Tealstreet terminal or have not created a V3 Tealstreet account yet. V2 account data and exchange connections do not move automatically into V3.
Follow V2 user - move to V3.
I already use V3
You are a V3 user if you already sign in to the current Tealstreet terminal and have added exchange API keys there.
If any of your exchange API keys use the Tealstreet Network, TS Network, or Tealstreet IP whitelist option, follow V3 user - update your exchange IP whitelist.
If your exchange key does not use Tealstreet IP whitelisting, this migration should not require an exchange-side whitelist edit.
Migration timeline
| Item | Status |
|---|---|
| New Tealstreet IP list available | Available now |
| Migration window | Now until November 2, 2026 at 00:00 UTC |
| Final V2 shutdown | November 2, 2026 at 00:00 UTC |
| Old AWS IPs retired | November 2, 2026 at 00:00 UTC |
During the overlap window, keep both the old and new Tealstreet IPs on your exchange API key when the exchange allows it. Do not remove the old IPs until Tealstreet announces that the cutover is complete.
V2 user - move to V3
V2 is being retired on November 2, 2026 at 00:00 UTC. To keep trading on Tealstreet, create or use a V3 account and add your exchange API keys there.
Before you start
- Keep your exchange website open in a separate tab. Some exchanges require two-factor authentication or email confirmation before you can create or edit API keys.
- Leave enough time for exchange security cooldowns. Some venues delay API key changes before they become active.
- If you have open positions, plan the move when you can monitor your exchange account directly.
Move your account
- Sign in to the current Tealstreet V3 terminal.
- Open Settings and choose Add new key.
- Select your exchange.
- Create a new API key on the exchange, or edit an existing key if the exchange supports doing that safely.
- Add the required permissions shown in the exchange-specific guide.
- Add the Tealstreet IP whitelist values shown in the V3 API key form.
- Paste the API key and secret into Tealstreet V3.
- Save the key and confirm that the account connects successfully.
- Turn on Cloud Sync for API Keys if you want the new V3 key to follow you to your other Tealstreet devices.
Start with the general API walkthrough, then use the guide for your exchange:
Some exchanges offer a Tealstreet third-party app selector instead of a manual IP whitelist field. If your exchange guide shows that option, use the selector shown there and follow the exchange-specific instructions.
V3 user - update your exchange IP whitelist
If you already use V3, you usually do not need a new Tealstreet account. The main task is to update the IP whitelist on every exchange API key that uses Tealstreet routing.
What changes
Tealstreet is replacing the old AWS IP addresses used by the Tealstreet Network with a simplified Vultr Tokyo fleet. For a short overlap window, both sets should work. After the AWS shutdown on November 2, 2026 at 00:00 UTC, keys that still allow only the old AWS IPs may stop connecting through Tealstreet.
Cloud sync can help make your Tealstreet API key list available on every device while you work through this migration. It does not edit the exchange API key or its IP whitelist, so complete the whitelist update below for each affected exchange account.
IP list
Add the full new Tealstreet IP list anywhere your exchange asks for the Tealstreet Network, TS Network, or Tealstreet IP whitelist.
Going forward, Tealstreet Network routing uses one region instead of split Japan and Singapore routing. Add the single Tokyo list below; there are no separate Singapore, proxy, or exchange-specific IP blocks to add.
New Tealstreet IPs, Vultr Tokyo fleet
167.179.112.21745.63.121.23545.77.135.138108.61.162.122149.28.30.214108.160.129.10845.77.27.6945.76.52.241108.61.247.61
Old Tealstreet IPs, AWS fleet
These are the old AWS IPs that Tealstreet is retiring. Your exchange may show some or all of these Japan and Singapore IPs on existing API keys.
Old Japan region IPs
18.178.14.2735.75.147.20135.78.132.22754.238.24.24654.65.38.58
Old Singapore region IPs
13.215.143.17954.169.98.7818.139.171.8752.76.105.5113.251.151.22054.179.219.8418.139.81.245
When Tealstreet shows both old and new blocks in the API key form, copy the new Tealstreet IP list for your exchange. Keep the old list in place until the November 2, 2026 at 00:00 UTC shutdown when the exchange allows both lists.
Update each exchange key
Repeat these steps for each Tealstreet-connected exchange account:
- Open the Tealstreet V3 API key settings for that exchange account.
- Copy the new Tealstreet IP list shown in the form.
- Open the API management page on the exchange website.
- Find the API key used by Tealstreet.
- Edit the IP whitelist or allowed IP addresses.
- Add the new Tealstreet IPs.
- Keep the old Tealstreet IPs during the overlap window, if the exchange allows enough entries.
- Save the exchange-side API key changes and complete any 2FA or email checks.
- Return to Tealstreet and reconnect or validate the account.
API key edits can take several minutes to propagate. Some exchanges also apply security cooldowns after changing API permissions or IP whitelists. If a key does not reconnect immediately, wait a few minutes and try again before deleting or recreating it.
If the exchange does not allow both lists
Some exchanges limit how many IP addresses can be added to one API key. If you cannot keep both the old and new Tealstreet IPs at the same time:
- Confirm that you copied the exact new list shown in Tealstreet.
- Check the exchange-specific guide for that venue.
- Contact Tealstreet support before removing the old list if you are unsure.
- Avoid making the change while you are actively managing a position only through Tealstreet.
Troubleshooting
Tealstreet says my API key, secret, or whitelist is incorrect
Check the exchange API key first:
- The API key and secret must match the key you added to Tealstreet.
- The key must still have the required trading permissions.
- The IP whitelist must include the new Tealstreet IPs for your routing option.
- If the old and new lists are both required during the overlap window, confirm both were saved.
I updated the whitelist and it still will not connect
Wait a few minutes, refresh Tealstreet, and validate the account again. If it still fails, take a screenshot of the exchange-side API whitelist and contact support.
Should I create a brand-new exchange API key?
If the exchange allows you to safely edit the IP whitelist on the existing key, editing is usually faster. If the exchange applies long cooldowns, has a strict IP limit, or the key has old permissions you no longer understand, creating a fresh key may be safer. Follow the exchange-specific guide before deleting the old key.
Where can I get help?
Use the Contact Us page if you need help from the Tealstreet team. Include your exchange name, whether you are moving from V2 or already on V3, and the exact error shown in Tealstreet.