Voyado Outage History

Voyado's FTP server experienced issues that prevented normal file transfer operations for 33 minutes. The incident affected the FTP component of the Engage service. The problem was investigated and resolved without further details on the specific cause or fix.

Voyado Engage experienced intermittent performance degradation that affected API, Messaging, and Automations components for a subset of customers over 25.6 hours. The issue was a recurrence of a previous day's problem, indicating that initial remediation efforts were insufficient. The service was stabilized and fully resolved, with continued monitoring to ensure system stability.

Voyado Engage experienced intermittent performance degradation affecting API, Messaging, and Automations components for a subset of customers over 23.7 hours. The issue was a recurrence of problems from the previous day, indicating that initial remediation efforts were insufficient. The service was restored to normal operation after additional actions were taken to address the underlying performance issues.

Voyado Engage experienced intermittent performance degradation affecting a subset of customers and the API service for 6 hours. The engineering team investigated the root cause and deployed fixes to address the performance issues. All services returned to normal operation after the fixes were implemented and monitored for stability.

Voyado experienced a major service incident where external API call activities failed for a subset of customers, specifically impacting Vipps and CowHills integrations. The issue was caused by a high volume of updates that overloaded the integration service. The incident was resolved after 55 minutes of investigation and monitoring.

Voyado's Delta Share exports used an incorrect UNIX timestamp format instead of the expected format for 26.1 hours over the weekend, potentially affecting how timestamps were interpreted in exported Parquet files. The service rolled back the change and re-ran all exports to restore the correct timestamp format. No data was lost during the incident.