Dstny experienced a major incident on August 10, 2026 affecting AP and AUS and 1 more component, lasting 3d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 10, 2026, 11:15 AM UTC
We are currently investigating a potential incident affecting the Call2Teams platform. At this time, multiple customers are experiencing registration failures, however the specific affected Edge SBCs and regions have not yet been confirmed. Our engineering teams are actively investigating the issue to determine the scope and impact, and we will provide updates every 60 minutes as more information becomes available. Thank you for your patience as we work to address this matter. Dstny Support
- investigating Aug 10, 2026, 12:28 PM UTC
We continue to investigate the issue affecting the Call2Teams platform, where multiple customers are experiencing registration failures. The affected Edge SBCs and regions are still being assessed. Engineering teams remain actively engaged and are working on mitigation measures to restore service as quickly as possible. We will continue to provide updates every 60 minutes or sooner if significant new information becomes available. Thank you for your patience. Dstny Support
- investigating Aug 10, 2026, 01:34 PM UTC
We have identified that the EU region is affected by the ongoing Call2Teams incident, with customers experiencing registration failures. Our Engineering teams remain actively engaged and are continuing to investigate the underlying cause, overall scope, and any additional affected regions or Edge SBCs. Work is ongoing to determine the appropriate mitigation and restore service as quickly as possible.
- monitoring Aug 10, 2026, 03:39 PM UTC
Service has now been restored in the affected EU region, and Call2Teams registrations have returned to normal. Our Engineering teams have taken mitigation actions and are continuing to monitor the platform to ensure service remains stable.
- monitoring Aug 11, 2026, 03:56 PM UTC
Service remains stable following the restoration activities, and no further customer impact has been observed at this time. Our Engineering teams are continuing to investigate the underlying root cause of the incident and are maintaining enhanced monitoring while this work is completed. Although we do not currently anticipate any further impact, the incident will remain under review until the root cause has been fully understood and any additional preventative actions have been identified. Thank you for your patience. Dstny Support.
- monitoring Aug 12, 2026, 02:47 PM UTC
Service remains stable following the restoration activities, and no further customer impact has been observed in the affected EU and US regions. Our Platform team has identified the root cause of the issue and implemented corrective measures to restore application services. Monitoring has been enhanced and additional operational safeguards have been introduced to improve visibility and support rapid response should similar conditions occur in future. Although reports from the US region were only identified later in the investigation, services have since been restored and both affected regions are now considered resolved and operating normally. We will continue to closely monitor service availability for the next 24 hours and do not anticipate any further impact at this time. Thank you for your patience. Dstny Support.
- resolved Aug 13, 2026, 02:19 PM UTC
We are pleased to confirm that this incident has been fully resolved. Following the restoration activities and an extended period of enhanced monitoring, no further customer impact or recurrence has been observed across the affected EU and US regions. Our Platform and Engineering teams have completed their investigation, identified the root cause, and implemented corrective and preventative measures to reduce the likelihood of similar incidents occurring in future. Additional monitoring and operational safeguards have also been introduced to improve visibility and support rapid response should similar conditions arise. A detailed post-mortem report will be published within the next 5 business days to provide further transparency into the incident, its cause, and the actions taken. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding throughout this incident. Should you have any questions or concerns, please contact our Support team. Thank you, Dstny Support
- postmortem Aug 26, 2026, 11:35 AM UTC
**Incident Summary** From 20:05 UTC on 9th August until 20:50 UTC on 15th August 2026, a subset of customers in Europe and the US were unable to receive inbound calls via Microsoft Teams due to a failure in the Call2Teams platform’s ability to manage customer connections. The issue was reactively identified following customer reports on 10th August, with initial recovery for European services achieved by 15:00 UTC that day. However, intermittent connectivity issues persisted for US-based users until a final service restart and the implementation of enhanced monitoring on 15th August, with all services verified as stable. **Root Cause** The investigation identified a software defect within the service responsible for managing user connections. This defect prevented the system from correctly releasing resources when processing certain errors. Over time, these unreleased resources accumulated in the platform's in-memory database until it reached its maximum capacity. Once this limit was hit, the system could no longer process new connection requests, leading to a loss of connectivity for multiple users during the incident. **Incident Resolution** Technical teams restored service by manually reassigning affected customers to alternative connection points and performing targeted restarts of the impacted software components and in-memory databases. To ensure long-term stability, engineering teams implemented new alerting and monitoring dashboards to provide better visibility into resource consumption. The incident was considered fully resolved once these proactive monitoring tools were in place and service stability was confirmed across all regions. **Mitigative Actions** * Implement software updates to improve resource management and error handling within the connection service. * Enhance platform monitoring and alerting to provide earlier visibility into system resource utilisation. * Optimise system logging configurations to improve diagnostic capabilities and data management. * Conduct a comprehensive review of platform alerting logic to ensure more proactive detection of service degradations. **Timeline** * 09 Aug 2026, 20:05 - Initial service disruption begins for a subset of users in the European region. * 10 Aug 2026, 08:00 - Service disruption begins for a subset of users in the US region. * 10 Aug 2026, 11:06 - A Major Incident is formalised following reports of connectivity issues. * 10 Aug 2026, 11:40 - Technical teams begin migrating affected users to alternative connection points. * 10 Aug 2026, 13:45 - Restoration activities commence for impacted European services. * 10 Aug 2026, 15:00 - European services are restored and enter a period of monitoring. * 12 Aug 2026, 07:00 - Further connectivity issues are identified affecting users in the US region. * 12 Aug 2026, 15:19 - Enhanced monitoring and dashboards are deployed to improve visibility. * 15 Aug 2026, 20:50 - Final service restarts are completed in the US, resolving all remaining impact. * 15 Aug 2026, 21:30 - All services are verified as stable across all regions.