Dstny experienced a major incident on June 4, 2026 affecting EU, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 04, 2026, 11:06 AM UTC
We are currently investigating a potential incident affecting Call Recording in the EU West region. Our teams are actively working to determine the scope and impact. Updates will be provided every 60 minutes as further information becomes available. Thank you for your patience while we address this issue. Dstny Support
- monitoring Jun 04, 2026, 11:39 AM UTC
Impact: Users were unable to log in to the Premium Call Recording portal in the EU West region. Our Platform team has identified the root cause and implemented corrective measures to restore services. We have tested and can confirm that login to the portal is now working as expected. We will continue to monitor service availability over the next 24 hours and do not anticipate any further impact at this time. Thank you for your patience while we addressed this issue. Dstny Support
- resolved Jun 05, 2026, 12:17 PM UTC
We are pleased to confirm that this incident has now been fully resolved. Over the past 24 hours, we have closely monitored the service and have seen no recurrence or further impact. The root cause has been identified, and measures have been implemented to prevent a reoccurrence. A detailed post‑incident report will be shared within the next five working days to provide full transparency. We apologise for any inconvenience caused and thank you for your patience during this time. If you have any questions or concerns, please contact our Support team. Kind regards, Dstny Support
- postmortem Jun 12, 2026, 03:56 PM UTC
**Incident Summary** From 11:33 UTC until 13:30 UTC on 4th June 2026, the Premium Call Recording service for users in the Netherlands and France was unavailable. Impacted users were unable to log into the recording portal or retrieve existing recordings. The issue was identified as a storage platform instability following a network failover. Service was fully restored at 13:30 UTC, with all services verified as stable. **Root Cause** The incident was caused by a hidden software fault within a core router, which was triggered during a routine network configuration update. This fault caused the primary router to fail, forcing traffic to a backup system. Because the backup system had inconsistent configuration settings, the storage platform became unstable and entered a protective "read-only" state. In this state, the system could not process the data required for user logins or recording retrieval. **Incident Resolution** Engineering teams identified the configuration discrepancies on the backup system and used automation tools to redeploy the correct settings. Once the network paths were aligned, the storage platform was successfully restored to full operation. Following the fix, a controlled reboot of the primary router was performed during a later maintenance window to ensure the underlying software fault was cleared. Service was confirmed as stable at 13:30 UTC. **Mitigative Actions** * Perform an emergency software reload on the affected routing hardware to resolve the identified software fault. * Review the Premium Call Recording architecture and storage setup to improve resilience against network failover events. ### **Timeline**