Voyado Outage History

A recent network configuration update unintentionally interrupted communication between the Elevate App backend and a subset of Elevate clusters. Because DNS records were still being served from cache, the change didn’t take effect right away. Once those cached entries expired, the loss of connectivity surfaced. This timing gap made it harder to connect the incident to the earlier change, which extended our troubleshooting and recovery time.

A release of Elevate introduced a bug in the calculation of promotion statistics, which caused CPU exhaustion leading to performance degradation of some Storefront endpoints. When noticed, the release was aborted and rollback was made to the previous version. The endpoints primarily affected were the landing-page and the product-page. Not all customers were affected.

## **Summary** On January 13th, we experienced an issue that temporarily prevented access to the Design Studio for some customers using the Orders module. ## **Customer Impact** Customers with the Orders module enabled and using a specific storage configuration were unable to access data sources and email modules in the Design Studio. Email sending was not affected. ## **Root Cause** The issue was caused by a configuration error that prevented necessary data from loading correctly. ## **Mitigation** We identified the root cause and applied a fix by adjusting the storage setup. Full functionality was restored by 12:14 CET on the same day. ## **Next Steps** To prevent this from happening again, we are improving our internal testing environments and reviewing the need for this specific configuration going forward. We sincerely apologize for the inconvenience this may have caused and appreciate your patience while we worked to resolve the issue.

## **Summary** On 2025-11-12, an issue was introduced in a morning update that caused registration forms to fail silently on submission for multiple customers. The forms appeared to work but did not process user input. ## **Customer Impact** End-users were unable to submit registration forms or update communication preferences. No error messages were shown, which impacted onboarding and preference management flows. ## **Root Cause** A bug in the released code affected how registration forms handled certain preference fields, causing submissions to fail without visible errors. ## **Mitigation** A fix was identified and deployed to resolve the issue. ## **Next Steps** We are implementing additional testing safeguards and improving our internal processes to detect similar issues earlier. We apologize for the disruption and appreciate your understanding.

## Summary A background system component failed to start due to outdated software. This caused some data to stop updating for a short period. ## Customer Impact For a limited time, some customers saw outdated or missing data in the Revenue Overview Dashboard. ## Root Cause and Mitigation The issue was caused by an outdated software dependency. The system was updated to the latest version, and we’ve added improved monitoring to detect similar issues earlier in the future.