Is Dstny down?

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.

We are writing to inform you that an issue occurred earlier affecting the ConnectMe service within the Eu-West-Bru Production region. Both UAT and Production environments were affected. The incident has now been fully resolved, and services have been restored. During the incident, Easybell, and ODOS BE and Flexfone DK customers may have experienced an inability to access or use the ConnectMe service. We will continue to monitor the platform for the next 24 hours to ensure service stability and confirm there is no further impact. Thank you for your understanding and patience. If you have any questions or concerns, please do not hesitate to contact our Support team. Kind regards, Dstny Support

**Incident Summary** On 3rd August 2026, between 08:55 UTC and 10:11 UTC, the ConnectMe application became unavailable for customers in Germany, Belgium and Denmark. Both the production and staging environments were affected. Users were unable to log in to the application, while those already logged in were disconnected when refreshing their session. The incident was identified through a combination of automated alerting and customer reports, and engineering teams were engaged promptly to investigate and restore service. Full service was confirmed as restored at 10:11 UTC, with both production and staging services verified as stable. **Root Cause** The incident was caused by a historical configuration issue within the underlying storage infrastructure. During previous infrastructure changes, a critical platform setting was not identified for review, leaving the environment unable to accommodate certain internal workload changes. When one of these changes occurred, the storage service became unavailable, which caused the content delivery service relied upon by ConnectMe to fail. As a result, ConnectMe was unavailable for the duration of the incident. **Incident Resolution** Once the root cause was identified as a storage infrastructure issue, the relevant infrastructure team was engaged to restore the affected storage platform. Following recovery of the storage service, the dependent services recovered automatically, and ConnectMe returned to normal operation. Full service was confirmed as restored at 10:11 UTC on 3rd August 2026. **Mitigative Actions** * **Review and update storage platform configuration** to reduce the risk of similar service disruptions occurring in future. * **Assess monitoring and alerting capabilities** to improve the early detection of infrastructure issues. * **Conduct a broader review of storage platform dependencies** to identify and address any related configuration risks. **Timeline** * 03 Aug 2026, 08:55 - Automated monitoring detected a potential service issue and alerted the support team. * 03 Aug 2026, 09:00 - Initial investigation began to determine the scope and cause of the disruption. * 03 Aug 2026, 09:08 - Early recovery actions were carried out while the investigation continued. * 03 Aug 2026, 09:20 - Customer impact was confirmed and the Major Incident process was initiated. * 03 Aug 2026, 09:27 - Relevant engineering teams were engaged and a coordinated incident response was established. * 03 Aug 2026, 09:35 - Further remediation activities were undertaken based on investigation findings. * 03 Aug 2026, 09:45 - Infrastructure specialists joined the investigation after the issue was traced to the underlying storage platform. * 03 Aug 2026, 10:04 - The affected storage services were restored.The affected storage services were restored. * 03 Aug 2026, 10:10 - ConnectMe services were confirmed as operational following recovery of the underlying infrastructure. * 03 Aug 2026, 10:11 - Service restoration was fully verified and the incident was declared resolved.

We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact.

Microsoft: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration This message was last updated at 18:47 UTC on 23 July 2026

On July 23, 2026, a routine device maintenance required isolating specific network paths. Our maintenance process converts these requests into system-readable requests and verifies that at least one of the two redundant paths remains healthy. Before maintenance begins, these requests undergo safety checks to confirm the work will be impact-less. In this case, a bug in the request conversion system incorrectly marked additional devices as a part of the maintenance event and caused a set of IP routes to be removed from more devices than intended. The routes were removed between our datacenter and wide-area network, impacting traffic entering or exiting the region. At 14:44 UTC, customers started experiencing impact and the engineering team was engaged immediately. The issue initially presented as large-scale route churn in our Wide-Area Network (WAN). It was later found that route removal was from a datacenter in the West US region. Once confirmed, engineers began roll back at 17:45 UTC. By 18:26 UTC, the network was restored and healthy, and all impacted services had fully recovered by 19:41 UTC.

**Incident Summary** From 13:49 UTC on 23rd July until 17:37 UTC on 28th July 2026, a subset of users in the US West region experienced intermittent issues registering to Edge SBCs, which impacted the ability to place or receive calls. The issue was proactively detected by our internal monitoring at 14:49 UTC on 23rd July, which identified connectivity failures to specific hosts. Investigation confirmed that the root cause was a regional network outage within the Azure infrastructure. While the primary service impact was mitigated by 18:37 UTC on 23rd July following a vendor-initiated rollback of network changes, the incident remained under observation until final verification was completed on 28th July, with all services verified as stable. **Root Cause** The incident was caused by an external third-party dependency failure. A regional network outage within Microsoft Azure’s US West infrastructure prevented registration traffic from reaching the Edge SBC hosts. This connectivity gap was the result of a network change implemented by the vendor within their environment, which inadvertently disrupted access to multiple hosts in that region. **Incident Resolution** The issue was resolved following a rollback of the problematic network changes by Azure engineering teams. Dstny engineers monitored the restoration of connectivity and confirmed that SSH and registration traffic returned to normal parameters. Throughout the event, the Call2Teams high-availability architecture allowed many customers to transparently fail over to secondary Edge SBCs, significantly limiting the total number of affected users. Final stability checks were performed across the affected region to ensure full service restoration. **Mitigative Actions** Our monitoring and alerting on the SBC platform functioned as intended and enabled the issue affecting our service to be identified and responded to promptly. As part of our continuous improvement activities, we will review opportunities to further enhance visibility of issues affecting external service providers and dependencies, recognising that some vendor-side infrastructure events may not currently be detectable through our existing monitoring capabilities. ### **Timeline** * 23 Jul 2026, 13:49 - Estimated start of service impact. * 23 Jul 2026, 14:49 - Call test alert triggered for US West host; engineering began investigation. * 23 Jul 2026, 15:12 - Affected host taken out of service and restarted to attempt recovery. * 23 Jul 2026, 16:30 - Engineering confirmed multiple hosts in the region were affected by a broader Azure network issue. * 23 Jul 2026, 16:40 - Official vendor notification received regarding US West connectivity issues. * 23 Jul 2026, 17:45 - Vendor initiated a rollback of recent network changes. * 23 Jul 2026, 18:37 - Call test alerts cleared and primary service impact concluded. * 28 Jul 2026, 17:37 - Incident officially closed following extended monitoring and verification.