Dixa experienced a minor incident on June 13, 2025 affecting Search, lasting 8h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 12, 2025, 12:29 PM UTC
We are experiencing some difficulties with Search. We are investigating the matter. Next update at 15:30hs
- identified Jun 12, 2025, 01:01 PM UTC
Our teams has now identified the issue. We are working on a fix that will resolve the issue. Next update at 16:00 hs CEST
- identified Jun 12, 2025, 02:37 PM UTC
We are continuing to work on fixing this issue. We are sorry for any inconvenience this may cause
- monitoring Jun 12, 2025, 08:18 PM UTC
We are continuing to see stability across our platform. We will continue monitoring.
- monitoring Jun 13, 2025, 08:01 AM UTC
While we continue working on a permanent fix for this issue, we've temporarily reverted our search functionality back to an earlier version. This means filters for custom attributes and searching contacts based on external ID might not work as expected for the time being. You should still be able to find custom attribute values by directly searching for the values without using a filter. We'll update our status page when we have more news to share.
- monitoring Jun 13, 2025, 01:32 PM UTC
We continue to actively work on restoring Search. Some users may still experience some degraded performance. We are continuing to monitor the situation closely. We'll update our status page when we have more news.
- resolved Jun 15, 2025, 09:14 PM UTC
All known issues to this incident have been resolved. We thank you for your patience and cooperation. Post mortem about this incident will be posted within 5 business days.
- postmortem Jun 19, 2025, 01:16 PM UTC
On the 12 of June 2025, we started observing stability issues with the new Search cluster, at the time of the incident, powering the Conversations & Contacts tabs on the Search page, as well as the Search POST endpoint of the Dixa API. Search results on the mentioned pages/endpoints were, to some degree, not updated in real time. The immediate solution was to scale up the cluster to better distribute the workloads, where the longer-term solution is to optimize affected workloads. We sincerely apologise for any inconvenience that this may have caused.