This issue was caused by a configuration issue introduced as part of two changes being made to the Vivantio SaaS Platform:
Normally these changes have no effect on, or interruption to, service to customers; hence no notification of these changes were publicised. Also, in the majority of cases, Vivantio does not make infrastructure and application changes at the same time – changes are isolated to minimize risk. However, due to the nature of the changes being made, that was not possible in this case.
In addition, the issue was only present in a small number of customer instances of Vivantio, and did not affect the entire platform – meaning Vivantio’s standard post-change testing, both manual and automated, failed to highlight the issue.
To mitigate the risk of this happening again, Vivantio’s development and infrastructure teams are working on improving post-release testing/monitoring to ensure full coverage of all instances within a given region.