Is Dstny down?

We are currently investigating reports of intermittent access issues affecting Dstny services in Sweden (SE). This is impacting access to both production and staging environments for some users due to a DNS-related issue affecting dstny.com and dstny.se. The underlying issue has been resolved by our GIS Cloud team. However, due to DNS propagation and caching across internet service providers and local networks, some customers may continue to experience intermittent connectivity or access issues while DNS records are refreshed. Our teams are actively monitoring the situation and will continue to provide updates every 60 minutes or sooner if significant new information becomes available. We apologise for any inconvenience caused and appreciate your patience during this time. Dstny Support

The DNS-related issue affecting dstny.com and dstny.se has been resolved by our GIS Cloud team. However, some customers may continue to experience intermittent access issues to Dstny production and staging environments while DNS changes propagate across internet service providers and local networks. If you are still experiencing connectivity issues, we recommend first clearing your local DNS cache. Customers who are familiar with their network settings may also temporarily switch to a public DNS provider such as Cloudflare (1.1.1.1) or Google DNS (8.8.8.8), both of which have been confirmed to have the correct DNS records. We continue to actively monitor the situation and will provide further updates as required. Dstny Support

We are pleased to confirm that the service issues reported under these two related incidents have now been fully resolved. Over the past 24 hours, we have closely monitored the affected services and have observed no further recurrence or impact. Our investigation determined that this incident and the related incident affecting Dstny Zone were both caused by the same underlying issue. Corrective measures have since been implemented to address the root cause and reduce the likelihood of recurrence. To provide transparency and insight into what occurred, a detailed post-mortem report covering the incident, its impact and the actions taken will be made available within the next five business days. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding throughout this incident. Should you have any further questions or concerns, please do not hesitate to contact our Support team. Thank you, Dstny Support

We are currently investigating a potential incident affecting DstnyZone. At this time, the specific regions and the extent of the impact are not yet confirmed. Our teams are actively working to identify the scope of the issue and we will provide updates every 60 minutes as we gather more information. Thank you for your patience as we work to address this matter. Dstny Support

We are writing to inform you that an issue occurred earlier affecting DstnyZone in all regions. The incident has been fully resolved, and services have been restored. This may have caused DstnyZone to be unaccessible for users in the affected areas. We will continue to monitor the situation for the next 24 hours to ensure there is no further impact. Thank you for your understanding, and we appreciate your continued patience. If you have any questions or concerns, please don’t hesitate to contact our support team. Dstny Support

Following our investigation, we have confirmed that the service disruption reported under this incident was related to the previously communicated incident, "Ongoing DNS Propagation Causing Intermittent Access to Dstny Services", and both were caused by the same underlying issue. As a result, these incidents have been consolidated and are being managed as a single event. Resolution details, corrective actions and post-mortem information will be communicated under the DNS propagation incident update to avoid duplication and ensure all relevant information is provided in one place. We are pleased to confirm that the issue has been fully resolved, and no further impact has been observed during ongoing monitoring. Thank you for your patience and understanding. Dstny Support

We are currently investigating an issue affecting Call2Teams certificate provisioning, which may impact calling functionality for some customers. We will provide a further update once we have confirmed progress or additional information.

As a precautionary security measure, the Forgot Password functionality has been temporarily disabled while we implement and test a security update. This does not affect normal access for users who already know their credentials. However, password resets will be unavailable until the update has been completed and validated. We are actively working to restore this functionality as quickly as possible. We apologise for any inconvenience and will provide further updates as they become available.

As a precautionary security measure, the Forgot Password functionality has been temporarily disabled across affected Dstny applications in all regions, including ConnectMe, SMP, CRM Connect, Teams Connect and Dstny Zone. This only affects users who need to reset their password. Users who already know their password can continue to log in and use services as normal. We are actively working to restore this functionality and will provide further updates as they become available.

Our engineering teams are continuing work to restore the Forgot Password functionality across the remaining affected Dstny services. Forgot Password has now been restored for Dstny Zone. Work is ongoing for the remaining applications, and we will provide a further update once there is confirmed progress.

Progress has been made towards restoring the Forgot Password functionality across the remaining affected Dstny services. The updated solution has successfully completed initial testing, with no issues identified. Deployment to our staging environments is now progressing so that we can complete further validation and performance testing before proceeding with the production rollout. We will provide a further update as the rollout progresses.

The Forgot Password functionality has now been fully restored across all affected Dstny applications, including ConnectMe, SMP, CRM Connect, Teams Connect and Dstny Zone. Users can now reset their passwords as usual. No further action is required. Our teams will continue to monitor the service closely to confirm stability. We apologise for the inconvenience caused while the security update was implemented and validated, and thank you for your patience throughout.

This incident has been resolved.

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

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

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.

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.

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.

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.

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

**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.