Voyado incident

[Engage] Slow Response Times on Contact API

Major Resolved View vendor source →

Voyado experienced a major incident on August 19, 2025 affecting API, lasting 6h 43m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2025, 08:05 AM UTC
Resolved
Aug 19, 2025, 02:49 PM UTC
Duration
6h 43m
Detected by Pingoru
Aug 19, 2025, 08:05 AM UTC

Affected components

API

Update timeline

  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.