pingoru pingoru Voyado had 51 outages in the last 2 years totaling 971h 7m of downtime, averaging 2.1 incidents per month.
There were 51 Voyado outages since June 4, 2025 totaling 971h 7m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We have reports on registration links not working from SMS. We are working on a fix.
A fix was deployed and confirmed working. Service is restored.
We are currently seeing longer response times in our APIs - investigation ongoing.
Changes was made to remediate the slowness, and things are looking better since 11:59 CEST.
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.
Every Tuesday at 21:00 CET/CEST we reserve the right to perform scheduled maintenance on Voyado Engage. Normally this won't affect availability at all, but on some rare occasions unresponsiveness or degraded performance may be experienced during the upgrade. We do apologize in advance for any impact on your work and/or availability, but hope that the things we release to production will make it all worth it in the end.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The scheduled maintenance has been completed.
Every Sunday at 03:00 CET/CEST we reserve the right to perform scheduled maintenance on our databases. During this time we make sure that the databases are fine tuned and all your data is protected. Normally this won’t affect availability, but some unresponsiveness or degraded performance may be experienced for short periods during the maintenance.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The scheduled maintenance has been completed.
There is currently a buildup of messages queued up on one of our processes, this is causing delays to automations triggered by interactions as well as webhooks related to contact events. It is being investigated.
We have identified a likely cause and taken steps to address it. We are now monitoring the results and will continue working on the issue until we can confirm it has been resolved.
We are seeing continued progress, with delays gradually decreasing. Delays remain, but we expect the service to recover during the evening. We will continue to monitor the service closely as it recovers.
Some delays remain. We currently expect the service to return to normal around 13:00 CEST and will continue to monitor it closely.
Unfortunately, some delays remain, but they continue to decrease. We currently expect the service to return to normal in about 30 minutes.
This incident has been resolved. We have not observed any further delays since around 15:15 CEST.
## Summary Between 5 October and 6 October 2026, processing of some events in Voyado Engage was delayed. The cause was an internal update to one of our background processes, which unexpectedly triggered a large amount of extra processing. The issue was limited to this process and has been corrected. ## Customer Impact Automations triggered by contact interactions ran later than normal. Webhooks for contact, consent and preferences changes were delayed as well. ## Root Cause and Mitigation A safeguard in the update did not work as intended, so existing data was processed again as if it were new. This happened on two occasions, 5 and 6 October. Our engineering teams stopped the process, cleared the extra processing and confirmed that everything was back to normal. ## Next Steps We are adding stronger safeguards and checks for this type of update, as well as earlier alerts so we can react faster if something similar happens. We apologize for the disruption and appreciate your patience.
We have identified an issue with Targeting affecting a subset of customers who use specific contact filters. This may impact point calculation, automations, and messages for affected customers.
A fix is currently being deployed. Impact may continue until the deployment is complete.
A fix has been deployed. We're monitoring the result.
This incident has been resolved.
When a shopper selects a facet value that has a translated label. The response may contain that value twice; once with the correct product count and once marked as selected with a count of 0. Filtering itself works correctly and the correct products are returned. The impact is limited to how the facet value list is presented, which can cause the value to appear duplicated, or not highlighted as selected in your storefront UI. Facet values without translations are not affected.
This incident has been resolved
At the moment, there are intermittent issues with email deliveries at Microsofts Exchange Online services. This means that you may see more emails in status "Unknown" for your sendouts than you normally do in Engage. This is a know issue at Microsoft and they are looking into this. Please see here more more information: https://portal.office.com/adminportal/home#/servicehealth (Note that you have to be a 365-admin to be able to access this link) We are also seeing this affecting responses from our support ticketing system not being delivered. If you have sent in tickets and not received any response, you can log in to our help center to check for responses. https://explore.voyado.com
Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to re-visit this page for more updates in this matter.
The email delivery issues affecting Microsoft Exchange Online on Friday have been resolved later that evening. Microsoft identified the cause as an incorrectly triggered anti-spam throttling rule, and they have confirmed that delivery has returned to normal levels. Emails affected during the incident may have remained in “Unknown” status in Engage until Microsoft processed the queued messages. More information is available in the Microsoft 365 Service Health portal under incident EX1467029. Note: Microsoft 365 administrator access is required.
We are currently experiencing an issue affecting the Shopify App for all customers. The Shopify App is currently offline due to an ongoing technical issue. We are actively investigating the problem and working to restore service as quickly as possible. We will provide another update as soon as we have more information.
A fix has been implemented, and the Shopify App is now back online. We are seeing promising results and are continuing to monitor the platform closely to ensure the service remains stable. Orders and contacts created during the incident will be recovered, but this process will take some time to complete. The following data will not be recovered: * Back in Stock subscribers * Inventory data for Back in Stock * Web tracking data We will provide another update once recovery has been completed or if there are any significant changes.
The situation remains stable, and the Shopify App continues to operate normally. We are still working on recovering data from the incident, as well as on long-term remediation to prevent a recurrence. We will provide another update once recovery has been completed or if there are any significant changes.
The Shopify App has been operating normally, and the service has remained stable. Additional information has been shared directly with the customers affected by the incident.
We are experiencing an ongoing intermittent outage affecting the Elevate App. We have contacted the 3rd party host provider and they are working on solving it.
The 3rd party provider has applied a mitigation that should resolved the problem temporarily, while they are investigate the root cause.
The mitigation made by the 3rd party provider resolved the problem. We will continue by monitor it closely for some time..
The 3rd party provider has resolved the issue.
We are seeing issues with short-URLs in reg forms not redirecting properly. This is being investigated.
The issue is limited to links to registration forms sent via SMS.
The issue has been identified and a fix is currently being tested before hotfix can be deployed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
### **Summary** On 2 June 2026, we identified an issue where short links used in SMS campaigns did not redirect users to the intended destination. Instead, recipients were redirected to the login screen. The issue was resolved the same day. ### **Customer impact** The issue affected customers using short links in SMS campaigns, including links to registration forms and mobile swipes. The impact period was approximately 15:40–18:17 CEST. ### **Root cause** A code change introduced in the release on 2 June changed how short link redirects were handled. As a result, some SMS short links redirected to the login screen instead of the intended page. ### **Mitigation** A hotfix was developed, verified, and deployed to production. The fix was confirmed working in production before the incident was marked as resolved. ### **Next steps** We have updated the relevant test coverage and will continue improving end-to-end testing for features using short links.
We currently have a problem with classification of new or changed product data. Already existing data is unaffected. Investigation to resolve the issue is ongoing.
The classification issue has been fixed. New and changed product data is now being processed again. We are working through the backlog, so classification for some recently added products may take some time to complete.
The issue with intermittent degraded performance from yesterday has returned, the remediations made yesterday seems not to be sufficient. Investigation ongoing.
We are currently seeing that system performance has stabilized following the recurrence of yesterday’s issue. We are continuing the investigation to identify the root cause and is actively testing additional measures to fully resolve the problem. Further updates will follow as we progress.
We are currently seeing stable system performance since 12:30. The issue causing intermittent degraded performance appears to be mitigated, and we are continuing to monitor closely.
Resolved: Following earlier performance degradation, all services have been operating normally since yesterday. We will continue to monitor to ensure stability.
The issue with intermittent degraded performance from yesterday has returned, the remediations made yesterday seems not to be sufficient. Investigation ongoing.
Following actions taken to address the issue, we are seeing improvements in system performance and stability. We will continue to monitor closely to ensure the situation remains stable.
All services are now operating normally. We will continue to monitor to ensure stability.
Elevate 3 API partially unavailable. We are currenty investigating the issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
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.
We have been alerted by our provider that they are having an issue with our telephony services and we are currently unreachable by phone. Please contact us through https://help.elevate.voyado.com or https://help.engage.voyado.com. You may also email [email protected].
This has been reported as resolved from our provider. We apologize for any inconvenience caused by the outage.