Voyado Outage History

Voyado is up right now

Voyado had 38 outages in the last 2 years totaling 61h 21m of downtime — averaging 1.6 incidents per month.

There were 38 Voyado outages since May 20, 2025 totaling 61h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.voyado.com

Minor September 23, 2025

[Engage] System Performance Degradation

Detected by Pingoru
Sep 23, 2025, 10:28 AM UTC
Resolved
Sep 23, 2025, 12:01 PM UTC
Duration
1h 33m
Affected: APIWeb ApplicationMessagingAutomations3rd Party Integrations
Timeline · 3 updates
  1. investigating Sep 23, 2025, 10:28 AM UTC

    We are currently investigating reports of general slowness and degraded performance across the platform. Users may experience unusually long loading times in the web application and APIs, and this may also impact processing times for automations and sendouts. Our team is working to identify the root cause and will provide an update as soon as more information is available. Thank you for your patience.

  2. monitoring Sep 23, 2025, 10:49 AM UTC

    We have taken actions that appear to have improved overall platform performance. Loading times in the web application and processing times for automations and sendouts are returning to normal levels. We are continuing to monitor the situation closely to ensure stability and will provide further updates as needed.

  3. resolved Sep 23, 2025, 12:01 PM UTC

    We have monitored the platform closely following the earlier performance issues, and all systems have remained stable. Loading times and processing are back to normal levels. While we are still investigating the underlying root cause to prevent recurrence, the immediate issue has been resolved. Thank you for your patience during this incident.

Read the full incident report →

Notice September 15, 2025

[Elevate] Relevance order degradation for a subset of customers

Detected by Pingoru
Sep 15, 2025, 02:37 PM UTC
Resolved
Sep 14, 2025, 11:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 15, 2025, 02:37 PM UTC

    We experienced an issue affecting a small subset of clusters where product results were not ordered with the expected relevance. The incident occurred between approximately 11:30 UTC and 13:45 UTC. The issue has been resolved, and relevance order is now restored for all affected clusters. No further impact is expected.

Read the full incident report →

Minor August 20, 2025

[Engage] Service Disruption

Detected by Pingoru
Aug 20, 2025, 12:29 PM UTC
Resolved
Aug 20, 2025, 03:17 PM UTC
Duration
2h 47m
Affected: API
Timeline · 5 updates
  1. investigating Aug 20, 2025, 12:29 PM UTC

    We are currently investigating a potential disruption. At this stage, information is limited, further updates will be shared as soon as possible.

  2. monitoring Aug 20, 2025, 12:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Aug 20, 2025, 01:21 PM UTC

    We are continuing to monitor for any further issues. Current performance remains stable and has been looking good since the implemented fix.

  4. resolved Aug 20, 2025, 03:17 PM UTC

    This incident has been resolved.

  5. postmortem Aug 26, 2025, 07:19 AM UTC

    **Summary** On August 20th, we experienced an issue affecting connectivity and performance in our API Gateway. The incident was identified and resolved within a short time frame. **Customer impact** During the incident, some customers experienced degraded performance and intermittent connectivity issues when accessing the API Gateway. Other platform functionality remained unaffected. **Root cause** The issue was caused by an SSL certificate deployment that introduced unexpected connectivity and performance problems. **Mitigation** Once identified, the deployment was quickly reverted, which immediately stabilized the platform. A permanent fix has since been implemented, and no further performance degradation has been observed. **Next steps** We have updated our deployment routines and processes to ensure similar issues are avoided in the future.

Read the full incident report →

Major August 19, 2025

[Engage] Slow Response Times on Contact API

Detected by Pingoru
Aug 19, 2025, 08:05 AM UTC
Resolved
Aug 19, 2025, 02:49 PM UTC
Duration
6h 43m
Affected: API
Timeline · 6 updates
  1. identified Aug 19, 2025, 08:05 AM UTC

    We have identified increased response times on our Contacts API. Users may experience slow response times and potential timeouts. Our team is actively working on deploying a hotfix as soon as possible to resolve the issue.

  2. monitoring Aug 19, 2025, 09:55 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Aug 19, 2025, 11:22 AM UTC

    Unfortunately our initial hotfix did not fully resolve our API response times. We are currently deploying a new hotfix to resolve this issue.

  4. monitoring Aug 19, 2025, 01:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 19, 2025, 02:49 PM UTC

    We have been monitoring the performance closely and can confirm that services are now running as expected. We apologize for any inconvenience caused during this incident, and can confirm that it has been resolved.

  6. postmortem Aug 27, 2025, 12:30 PM UTC

    ## Summary On August 19th, Voyado Engage experienced degraded performance on the Contact API due to an issue introduced in a recent release. ## Customer Impact Customers using the Contact API may have experienced slower response times. Other parts of the platform remained fully operational. ## Root Cause A code change led to unintended system behavior that affected backend performance. The issue was related to a specific component used to detect changes in contact data. ## Mitigation The problematic code was disabled through a targeted hotfix, which restored normal performance. ## Next steps We are improving safeguards around this component and enhancing our deployment checks to prevent similar issues in the future. We are sorry for the disruption this caused and appreciate your patience while we worked to resolve the issue.

Read the full incident report →

Minor August 10, 2025

[Engage] Delays in SMS Delivery Statistics and Possible SMS Delivery Delays

Detected by Pingoru
Aug 10, 2025, 12:01 PM UTC
Resolved
Aug 10, 2025, 04:46 PM UTC
Duration
4h 45m
Affected: Messaging
Timeline · 3 updates
  1. identified Aug 10, 2025, 12:01 PM UTC

    We have identified delays in delivery statistics affecting a subset of our customers since 10.19 today. According to our SMS provider, delays in SMS deliveries may also be experienced. The disruption is due to an ongoing incident at one of our SMS providers. You can follow the provider’s status here: https://status.sinch.com/

  2. monitoring Aug 10, 2025, 01:09 PM UTC

    Our SMS provider has implemented a fix, and we have since observed that the delay in delivery statistics for sendouts is resolving.

  3. resolved Aug 10, 2025, 04:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 22, 2025

Elevate App

Detected by Pingoru
Jul 22, 2025, 04:35 PM UTC
Resolved
Jul 22, 2025, 06:47 PM UTC
Duration
2h 12m
Affected: Apps
Timeline · 3 updates
  1. investigating Jul 22, 2025, 06:26 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 22, 2025, 06:47 PM UTC

    This incident has been resolved.

  3. postmortem Jul 24, 2025, 07:04 AM UTC

    A separate service from a third party/vendor is used to host the Elevate application. Due to an error in their invoicing service the Elevate application was suspended.

Read the full incident report →

Minor July 2, 2025

[Engage] Contact lookup Performance Degradation

Detected by Pingoru
Jul 02, 2025, 02:31 PM UTC
Resolved
Jul 02, 2025, 06:51 PM UTC
Duration
4h 20m
Affected: 3rd Party Integrations
Timeline · 3 updates
  1. investigating Jul 02, 2025, 02:31 PM UTC

    We are currently experiencing service disruptions due to an issue with an external provider. This may affect the availability or performance of contact lookups for the subset of customers which are using this feature. We are monitoring the situation closely and will provide updates as more information becomes available.

  2. investigating Jul 02, 2025, 03:47 PM UTC

    This issue is still being investigated by our provider. Current status and more detailed updates can be followed here: https://status.dnb.com/. We will keep you informed about the development as we learn more.

  3. resolved Jul 02, 2025, 06:51 PM UTC

    The affected service is restored back to normal and contact lookups are now fully operational again.

Read the full incident report →