Action may be required.
What is changing?
We are adding two new IP addresses for sending callbacks to customers who use the respective feature of the Futurae APIs, to receive updates from Futurae concerning the status of authentications and/or enrollments. Customers who use the callbacks feature and perform whitelisting of incoming traffic towards their infrastructure, are required to whitelist the below IP for inbound/ingress traffic by October 4th 2026.
If you do not use the callbacks feature of the Futurae APIs or if you do not whitelist incoming connections to your infrastructure, no action is required.
| Your setup | Action needed? |
|---|---|
| You use the callbacks feature of the Futurae APIs and you whitelist incoming connections to your infrastructure based on source IP address | ✅ Yes, whitelist the 2 new IP addresses below |
| You do not use callbacks or do not perform whitelisting of incoming connections | ❌ No action needed |
| You're not sure | Please contact Futurae Support |
The additional new IP addresses to whitelist:
- 34.65.92.210/32
- 34.65.35.109/32
These IP addresses only need to be whitelisted for inbound/ingress connections coming from Futurae towards your servers.
Required Actions
- Add the two IP addresses above to your inbound firewall IP address whitelist.
- Complete this by October 4th, 2026, to ensure that Futurae callback traffic is not disrupted.
🚫 Do not remove any of your currently whitelisted IP addresses or ranges. All existing IPv4 and IPv6 addresses listed in Futurae IP address ranges must remain whitelisted both for incoming and outgoing connections (as described in the article). This announcement only adds to that list, it does not replace it.
What happens after October 4th?
Futurae will start sending callbacks from these two IP addresses at some time after October 4th 2026. Both the existing and the two new IP addresses that are being added, will remain active, until further notice.
For any inquiries, do not hesitate to contact us at support@futurae.com.
Comments
0 comments
Article is closed for comments.