Is Dstny down?

Dstny has been made aware of two recently disclosed critical security vulnerabilities affecting PHP, a programming language commonly used for web based applications. As a precautionary security measure, Dstny has temporarily restricted access to certain applications and services that may be affected while our technical teams assess the exposure and implement the appropriate security updates and mitigations. This action is preventive. At this time, we have no indication that these vulnerabilities have been successfully exploited as part of this event. The temporary unavailability of affected services is a deliberate measure to minimize potential security risk while remediation activities are carried out. Dstny continues to monitor developments closely and will restore affected services once the necessary security measures have been implemented and validated. Dstny Support

We are continuing to investigate this issue.

Services not impacted As stated in our previous update, we have no indication that the vulnerabilities involved in this event were successfully exploited. We can confirm that the following services are not affected by these vulnerabilities and remained fully operational throughout: Core SMP Connect Me Analytics Call Recording Call2Teams Softphone BMP VoipCube CRM Connect Teams Connect Zone We will continue to monitor the situation and will share further updates here as soon as more information is available.

Moving to monitoring As stated in our previous updates, we have no indication that the vulnerabilities involved in this event were successfully exploited. We can confirm that we still see no impact on our services. We are therefore moving this incident to the monitoring state. We will continue to monitor the situation and will post here if anything changes. If you have questions in the meantime, please contact Dstny Support.

Dstny was made aware of two recently disclosed critical security vulnerabilities affecting PHP, a programming language commonly used for web-based applications. As a precautionary measure, we temporarily restricted access to certain applications and services while our technical teams assessed the exposure and implemented the appropriate security updates and mitigations. Outcome We found no indication that the vulnerabilities were successfully exploited at any point during this event, and we observed no impact on our services during the monitoring period. The following services were not affected and remained fully operational throughout: Core, SMP, Connect Me, Analytics, Call Recording, Call2Teams, Softphone, BMP, VoipCube, CRM Connect, Teams Connect, Zone, Carrier Automate, and Mobile Apps. Next steps No action is required from customers. We will continue to follow security developments closely and apply updates as needed to keep our services secure. If you have any questions, please contact Dstny Support.

Our Platform team has identified the root cause of the issue and implemented corrective measures to restore application services. We will continue to monitor service availability for the next 24 hours. and do not anticipate any further impact at this time. Thank you. Dstny Support.

Our Platform team has identified the root cause of the issue and implemented corrective measures to restore application services. We will continue to monitor service availability for the next 24 hours. and do not anticipate any further impact at this time. Thank you. Dstny Support.

We are writing to inform you that an issue occurred earlier, affecting our Core calling platform, including desktop clients and desk phones, in the Nordics region. The incident has been fully resolved, and services have been restored. This caused inbound calls to fail when answered by an IVR for users in the affected areas. Our Platform team identified the root cause of the issue and implemented corrective measures to restore application services. We will continue to monitor service availability for the next 24 hours to ensure there is no further impact. We do not anticipate any further impact at this time. We apologise for any inconvenience caused, thank you for your understanding, and appreciate your continued patience. If you have any questions or concerns, please do not hesitate to contact our support team. Dstny Support

We are pleased to confirm that this incident has been fully resolved. Over the past 24 hours, we have closely monitored the situation and observed no recurrence or further impact. We have determined the root cause and have implemented measures to prevent future occurrences. To provide transparency and insight into the incident, a detailed post-mortem report will be made available within the next 5 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 feel free to reach out to our support team. Thank you, Dstny Support

**Incident Summary** Between 14:50 UTC and 15:12 UTC on 19th October 2026, calls to certain numbers in the Nordics region that rely on recorded messages or menus were unable to connect as expected, including automated menus, voicemail and call queues. Multiple partners reported the issue to our Support team. Our engineers quickly located the fault and took corrective action on the affected servers, and normal call handling resumed at 15:12 UTC, with all services verified as stable. **Root Cause** Following planned maintenance on 7th October 2026, new media servers were brought into service. During this work, a process error meant the storage configuration and monitoring safeguards were not applied as intended. As a result, storage capacity on these servers gradually filled over the following days without any alert being raised. By 19th October 2026, capacity was exhausted and the servers could no longer play audio content. **Incident Resolution** Our operations team identified the cause and freed up storage capacity on the affected servers. Service was restored at 15:12 UTC, and normal operation of audio prompts and menus resumed. Monitoring was also introduced at the same time to provide early warning should a similar situation arise. **Mitigative Actions** * Rebuild the affected media servers to a corrected, standardised configuration. * Update installation and setup documentation to reduce the risk of configuration errors. * Enable storage monitoring and alerting across the affected production and test environments. **Timeline** * 07 Oct 2026, 19:00 - Planned maintenance completed and new media servers brought into service. * 19 Oct 2026, 14:50 - Storage capacity was exhausted and affected calls began to fail. * 19 Oct 2026, 14:53 - Our operations team began investigating following partner reports to Support. * 19 Oct 2026, 15:08 - The cause was identified. * 19 Oct 2026, 15:09 - Major incident declared. * 19 Oct 2026, 15:12 - Storage capacity was cleared and normal call handling resumed, with monitoring added to provide early warning of any recurrence.

We are currently investigating an issue affecting ConnectMe in the Nordics region. This is causing intermittent inbound and outbound call failures. Our teams are working to identify the root cause and implement a resolution. A fix is currently being deployed to the affected platform, and the rollout is under close monitoring. This will prevent new occurrences, but some users may still be affected by outdated data. If you experience any issues, logging out and back in again should resolve the problem. In the meantime, we are working to correct the affected user data on our side. Updates will be provided every 60 minutes as we learn more. We apologise for any inconvenience caused and appreciate your patience during this time. Dstny Support

We have identified the root cause of the incident and have prepared an emergency fix. Deployment of the hotfix began from 13:00 UTC and is progressing as planned. We expect the deployment to be completed by 15:00 UTC. Once it has completed, we will let you know so that you can retest straight away. In the meantime, if you experience any issues, logging out and back in again should resolve the problem. We will provide an additional update following the deployment, or sooner if necessary. Thank you for your continued patience and understanding as we work to resolve this matter. Dstny Support

We have identified the root cause of the incident and have prepared an emergency fix. Deployment of the hotfix began from 13:00 UTC and is progressing as planned. The update is still in progress; new ETA expected 16:00 UTC. Once it has completed, we will let you know so that you can retest straight away. In the meantime, if you experience any issues, logging out and back in again should resolve the problem. We will provide an additional update following the deployment, or sooner if necessary. Thank you for your continued patience and understanding as we work to resolve this matter. Dstny Support

Our Platform team has identified the root cause of the issue and implemented corrective measures to restore application services. The hotfix deployment completed at 17:00 UTC. You are welcome to retest now. If you encounter any further problems after the deployment, please raise them with Dstny Support so that we can investigate promptly. Should you still experience issues, logging out and back in again should resolve the problem. We will continue to monitor service availability for the next 24 hours and do not anticipate any further impact at this time. Thank you. Dstny Support

We are pleased to confirm that this incident has been fully resolved. Over the past 24 hours, we have closely monitored the situation and observed no recurrence or further impact. We have determined the root cause and have implemented measures to prevent future occurrences. To provide transparency and insight into the incident, a detailed post-mortem report will be made available within the next 5 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 feel free to reach out to our support team. Thank you, Dstny Support

**Incident Summary** ConnectMe users experienced two separate periods of disruption. In the Nordics region, from 10:28 UTC on 1st October until 16:21 UTC on 2nd October 2026, a subset of users were unable to make or receive calls. A similar issue affected a subset of users in the EU West region from 08:22 UTC until 19:00 UTC on 6th October 2026. The first issue was identified proactively by our operations team after monitoring flagged unhealthy call-handling services, before any customer reports were received. The second was reported to our Support team. Service in the Nordics was restored through additional capacity and a software fix on 1st and 2nd October, and the second occurrence was contained with further capacity and a temporary workaround. A permanent fix was then applied across both production environments at 19:00 UTC on 6th October, with all services verified as stable. **Root Cause** A software defect in the way users were allocated across backend servers caused users to be reassigned far more often than intended. Some servers incorrectly reported that they had no remaining capacity, and some users were reassigned again at login despite already having been moved. In the Nordics region, the resulting volume of reassignments placed excessive strain on the supporting database, causing a lock-up. This prevented the call-handling services from completing their routine health checks, so they were taken out of service and users were unable to make or receive calls. The same underlying defect, in which servers incorrectly reported themselves as full, was the cause of the second period of disruption in the EU West region. **Incident Resolution** For the Nordics region, our engineering teams rolled back a recent software release and added further server capacity to spread the load. A software fix was then deployed on 2nd October to resolve the database lock-up, and records that could not be updated during the incident were resynchronised. On 5th October, our development teams identified the cause of the servers incorrectly reporting that they were full. When the same behaviour was reported in the EU West region on 6th October, additional capacity and a temporary workaround were applied to restore service. A permanent fix was built and deployed to both affected production environments at 19:00 UTC on 6th October, and subsequent checks confirmed stable service. **Mitigative Actions** * Refine the user allocation logic to prevent unnecessary reassignment of users. * Strengthen database handling within the call-handling service to prevent lock-ups from affecting service health. * Correct the way backend servers report their available capacity. * Roll out the fixes to all remaining production regions. ### **Timeline** * 01 Oct 2026, 10:28 - Some backend servers reached capacity and began moving users to other servers. The additional activity caused a lock-up in a supporting database, and outgoing calls failed for some of the users who had been moved. * 01 Oct 2026, 11:13 - Our engineering teams convened an incident response and rolled back a recent software release. This reduced the impact but did not fully resolve it. Additional server capacity was also added to spread the load. * 01 Oct 2026, 12:16 - Service stabilised. * 02 Oct 2026, 16:21 - A software fix was deployed to resolve the database lock-up, and records that could not be updated during the incident were resynchronised. * 04 Oct 2026 - The scheduled weekend restart redistributed users more evenly across servers. * 05 Oct 2026 - Our development teams identified why some servers were incorrectly reporting that they were full. * 06 Oct 2026, 08:22 - The same capacity reporting issue was reported in this region. Additional capacity was added and a temporary workaround was applied to restore service. * 06 Oct 2026, 19:00 - A permanent fix was deployed to both the Nordics and EU West production environments, with all services verified as stable.

We are currently investigating a potential incident affecting SMP. 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 SMP in the EU West region. The incident has been fully resolved, and services have been restored. This may have caused black screens, performance issues, pages not loading, and slow speeds 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

We are pleased to confirm that this incident has been fully resolved. Over the past 24 hours, we have closely monitored the situation and observed no recurrence or further impact. We have determined the root cause and have implemented measures to prevent future occurrences. In the interest of transparency, a detailed post-mortem report 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

**Incident Summary** Between 30th September and 1st October 2026, some users and administrators in the EU West region experienced slow performance and intermittent loading problems when using SMP, with the impact building gradually beforehand. The first customer reports were received on 30th September. Service was restored at 08:04 UTC on 1st October once corrective action was taken, with all services verified as stable. **Root Cause** A subset of the servers supporting SMP in EU West ran short of memory, which reduced the capacity available to process customer requests and caused the intermittent slowness. This followed an increase in the temporary data held by the application. Investigations into the origin of this increase are ongoing. **Incident Resolution** Corrective action was taken on the affected servers, which returned the service to normal operation. Service remained stable following the recovery, and the teams continue to review the service to support long-term stability. **Mitigative Actions** * Review how alerts for memory-related issues are allocated and routed, so they reach the correct teams promptly. * Improve logging and monitoring capabilities to speed up the identification and diagnosis of future issues. * Address memory-handling issues within the application that were identified during the investigation. **Timeline** * 29 Sept 2026 - A gradual increase in memory usage was observed on the affected servers, with no customer impact reported. * 30 Sept 2026, 12:30 - Customers first reported slowness and loading problems when using SMP. * 01 Oct 2026, 06:30 - Some users continued to experience intermittent performance issues. * 01 Oct 2026, 06:50 - Further reports were received as additional customers and partners were affected. * 01 Oct 2026, 07:20 - Urgent support cases were raised, prompting a wider review of the service. * 01 Oct 2026 - Investigations linked the issue to memory pressure on a subset of the servers. * 01 Oct 2026, 08:00 - Corrective action was taken on the affected servers. * 01 Oct 2026, 08:04 - Service was restored to normal operation. * 01 Oct 2026, 11:00 - One related report was received after recovery, and reports then tapered off. * 02 Oct 2026, 06:00 - The incident was formally closed, and work continued to establish the origin of the increase in memory usage.

We are currently investigating an issue affecting Call2Teams services across the EU and APAC regions. Users in the affected areas may experience issues when making outbound calls. Our teams are actively working to identify the root cause and implement a resolution as quickly as possible. Updates will be provided every 60 minutes as more information becomes available. We apologize for any inconvenience caused and appreciate your patience and understanding during this time. Dstny Support

We have identified the root cause of the incident and have prepared an emergency fix. The hotfix is scheduled for deployment on 25/09/2026 between 8pm and 10pm UTC Time. We will provide an additional update following the deployment or sooner if necessary. Thank you for your continued patience and understanding as we work to resolve this matter. Dstny Support

Our Platform team has identified the root cause of the issue and implemented corrective measures to restore application services. We will continue to monitor service availability for the next 24 hours. and do not anticipate any further impact at this time. Thank you. Dstny Support.

We are pleased to confirm that this incident has been fully resolved. Following the successful deployment of a hotfix, services have remained stable, and over the past 24 hours we have closely monitored the platform with no recurrence of the issue or further customer impact observed. We have identified the root cause of the incident and implemented corrective measures to prevent a similar occurrence in the future. To provide further transparency and insight into the incident, a detailed post-mortem report 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

**Incident Summary** Between 07:00 UTC on 21st September and 21:00 UTC on 25th September 2026, customers using Dstny Call2Teams in all regions experienced intermittent failures when making outbound calls, with some attempts timing out during call set-up. The issue was first reported by a customer at 08:00 UTC on 22nd September and became more frequent once the maintenance rollout completed on 24th September. A corrective change was applied in stages once the cause was identified, and outbound calling was fully restored at 21:00 UTC on 25th September, with all services verified as stable. **Root Cause** A performance-related configuration change, introduced during planned maintenance on 21st September, proved incompatible with how Call2Teams handles outbound calls. An incorrect default setting applied the change more widely than intended, leaving some call-handling components without the security certificates needed to complete call set-up. Calls routed through those components timed out, while others connected normally, which is why the failures were intermittent. The incompatibility was not identified during pre-release testing. **Incident Resolution** Engineering teams disabled the affected performance feature and restarted the relevant services to apply the change. To limit disruption, the fix was deployed outside normal hours, starting with the US, followed by the EU and APAC. Outbound calling was restored at 21:00 UTC on 25th September, and subsequent checks confirmed stable operation across all regions. **Mitigative Actions** * Restore and improve the access needed for configuration synchronisation testing, supporting earlier detection of similar issues. ### **Timeline** * 21 Sept 2026, 07:00 - Planned maintenance rollout begins; intermittent outbound call failures start. * 22 Sept 2026, 08:00 - A customer reports the issue. * 24 Sept 2026, 20:00 - Rollout completes; failures become more frequent. * 25 Sept 2026, 00:00 - Automated monitoring begins alerting on outbound call failures. * 25 Sept 2026, 10:00 - Further alerts received; engineering investigation intensifies. * 25 Sept 2026, 13:00 - Cause identified and a corrective change prepared. * 25 Sept 2026, 14:00 - Corrective change begins rolling out in the US. * 25 Sept 2026, 20:00 - Corrective change begins rolling out in the EU. * 25 Sept 2026, 21:00 - Outbound calling fully restored, with all services verified as stable.