Is Voyado Down?

A fix was deployed and confirmed working. Service is restored. --- [2026-10-21T11:49:46.924+02:00] (investigating) We have reports on registration links not working from SMS. We are working on a fix.

### Summary On October 19, between approximately 11:05 and 12:00 CEST, the Voyado Engage APIs experienced degraded performance and some API requests failed, this was due to an infrastructure issue affecting our cloud provider. The issue caused increased response times across our API services, which were further amplified by an internal traffic management mechanism. We identified the contributing factors and took action to restore normal performance. ### Customer impact During the incident, customers experienced slower response times when making requests to the Voyado Engage APIs. Some customers also experienced failed requests, with temporary errors \(503\). Performance was back to normal at about 12:00 CEST. Other platform functionality was confirmed not to be affected. ### Root cause The incident was initially triggered by an infrastructure issue at our cloud provider, which caused reduced performance across multiple services simultaneously. This triggered an internal traffic management mechanism designed to balance load and isolate unusually slow API traffic to protect overall platform performance. The mechanism did not manage the situation as intended which caused delays and some failed API requests for affected customers. ### Mitigation As part of our mitigation efforts, we increased the capacity available to handle the redirected API traffic. Alongside the recovery of the underlying cloud infrastructure, this helped restore normal API performance by approximately 12:00 CEST on October 19. We continued monitoring the platform to ensure stability before formally closing the incident on October 20. ### Next steps To reduce the risk of similar incidents, we are reviewing and taking appopriate actions of the following: * Review and enhance how our traffic management mechanism responds to platform-wide performance degradation. * Expand the capacity available to handle redirected API traffic to improve resilience during unexpected load. * Improve our ability to detect unusual traffic patterns and infrastructure-related performance issues sooner. We remain committed to improving the reliability and resilience of Voyado Engage and appreciate your patience and understanding. We apologize for the disruption this caused. --- [2026-10-20T09:43:45.414+02:00] (resolved) Monitoring has shown stabilized operational status of the response time. We are conducing a post mortem to understand what was the root cause and will update with an incident report. --- [2026-10-19T12:22:00.140+02:00] (monitoring) Changes was made to remediate the slowness, and things are looking better since 11:59 CEST. --- [2026-10-19T11:49:05.340+02:00] (investigating) We are currently seeing longer response times in our APIs - investigation ongoing.

**Date:** October 7, 2026 **Duration:** 14:13–15:32 CEST \(approximately 1 hour and 20 minutes\) **Affected service:** Engage Web Application ### Summary On October 7, 2026, between approximately 14:13 and 15:32 CEST, the Voyado Engage web application was unavailable to customers. During this period, users were unable to log in or access the web application. Our team identified the cause and restored service at 15:32 CEST. Following a period of monitoring, the incident was confirmed as resolved. ### Customer impact The incident affected access to the Engage web application for nearly all production environments. Users attempting to access the application experienced continuous loading, preventing them from logging in or using the interface. The partner portal remained accessible, and no data was lost during the incident. ### Root cause The incident was caused by a software update that introduced an issue with how the web application handles security tokens used during user sessions. ### Mitigation Once the issue was identified, our development team initiated a new deployment that removed the problematic change. In parallel, we restored a previously working version of the affected application components to accelerate recovery. This allowed functionality to return progressively while the updated deployment was completed. Full access was confirmed restored at approximately 15:32 CEST. ### Next steps To reduce the risk of similar incidents and improve our ability to recover quickly, we are focusing on the following improvements: * **Faster recovery:** Improve our deployment processes to enable quicker rollbacks to previously working application versions. * **Improved monitoring:** Introduce automated checks for login and application loading to help detect issues before customers are affected. * **Enhanced testing:** Strengthen testing procedures to better cover differences between production and testing environments. We sincerely apologize for the disruption this caused and appreciate your patience while we worked to restore the service. --- [2026-10-07T16:26:30.373+02:00] (resolved) This incident has been resolved. --- [2026-10-07T15:33:51.693+02:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-07T14:57:23.490+02:00] (identified) A fix has been implemented, and deployment is in progress. --- [2026-10-07T14:39:11.776+02:00] (identified) The issue has been identified and a fix is being implemented.