Due to unforeseen changes on the European hosting platform used, a number of servers have been migrated and restructured. The migration was performed despite frozen period, given that the migration could take longer and become more costly than reasonable when executed later. The migration was executed between January 10 and January 13, 2026.
The names of the Invantive servers such as “https://cloud.invantive.com” remain unchanged.
The total capacity in terms of processors and work memory remains unchanged.
Capacity considerations
The capacity of the servers has been significantly changed by re-assigning and splitting capacity.
The typical workload cycle on Invantive Cloud is 24 hour. After completion of the first 24-hour cycle, there have been no signals that users experienced consequences.
Whitelisting new IP address
Outbound connections on Invantive Cloud will originate from a different IP address. The IP address 51.159.148.160 remains in use, but the IP address 51.159.170.87 will be used from January 12 on for outbound connections on Invantive Cloud.
Typically on connections towards SQL Server, PostgreSQL, Oracle RDBMS and MySQL, changes may be needed in the firewall. Such connections are typically used to replicate data.
When the necessary changes to the firewall are not made, Invantive Bridge Online and App Online will run fine, but opening the SQL editor on Invantive Cloud can raise errors such as itgenase349. The SQL editor will open again fine when the firewall has been adapted without further changes within Invantive Cloud.
There is no workaround without whitelisting the IP address and neither a rollback is possible. It is assumed that the SQL editor is solely used for non-critical production tasks.
The IP address of outbound connections on Invantive Bridge Online and Invantive App Online remains 51.159.148.160.
The additional IP address has been reflected in the firewall whitelist:
Security and Compliance
There are no known changes in TLS, certificates, authentication, security and compliance features.