Is Dstny down?

We are currently investigating a potential incident affecting VoiPCube. 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 have identified the root cause of the incident and are currently preparing an emergency fix to address the issue. We will provide an additional update within the next 60 minutes. Thank you for your continued patience and understanding as we work to resolve this matter. Dstny Support

We are writing to inform you that an issue occurred earlier affecting VoIPCube in the EU West and Nordics regions. The incident has been fully resolved, and services have been restored. This may have caused login issues for users attempting to access the platform. 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 affecting VoIPCube login in the EU West and Nordics regions has been fully resolved. Over the past 24 hours, we have closely monitored the situation and observed no recurrence or further impact. We have identified the root cause and implemented the necessary fix to restore normal service, along with measures to prevent a similar issue occurring in the future. To provide transparency and further insight, 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

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

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

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

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

We are currently investigating a potential incident affecting Dynamic Emergency Trunk (DET) services for Call2Teams across all regions. Our teams are working to determine the scope and impact, and we will provide further updates every 60 minutes as more information becomes available. Thank you for your patience while we investigate. Dstny Support

Engineering are continuing to investigate to determine the full impact, root cause, and an appropriate resolution. We will provide a further update in 60 minutes. Thank you for your patience. Dstny Support

Service stability has improved following initial recovery actions, and we are now focusing on identifying and addressing the primary underlying cause. Engineering continue to work to determine the full impact and implement a resolution. We will provide a further update in 60 minutes. 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 now been fully resolved. Over the past 24 hours, monitoring has shown no recurrence or further impact. The root cause has been identified, and measures have been implemented to prevent recurrence. A detailed post-mortem report will be shared within the next five business days. We apologise for any inconvenience caused and thank you for your patience and understanding. If you have any further questions, please contact our Support team. Thank you, Dstny Support

**Incident Summary** From 00:37 UTC on 17th May to 12:45 UTC on 18th May 2026, DET emergency trunk calling for Call2Teams was unavailable across all regions. The issue occurred following a host restart, which prevented network traffic from reaching the emergency trunks. While the service was impacted throughout this period, investigations confirmed that no customer emergency calls were attempted while the trunks were offline. Service was fully restored at 12:45 UTC on 18th May, with stability verified. **Root Cause** During an infrastructure restart, an automated system security service unintentionally activated and blocked essential network ports. This occurred due to a configuration oversight within the automation scripts and manual setup, which failed to ensure the service remained disabled upon reboot. This resulted in the emergency trunks being unable to establish the required network connections for call processing. **Incident Resolution** Engineering teams identified that the security service was active on the affected hosts and manually stopped the process. This immediately restored network connectivity, and all emergency trunks returned to a stable state. Final verification testing was completed at 12:45 UTC on 18th May, confirming that all regions were once again able to process emergency traffic correctly. **Mitigative Actions** * Permanently remove the conflicting security software from all relevant virtual machines to ensure they are reboot-safe. * Adjust call tester alerts and notification workflows to ensure faster escalation and investigation of availability warnings. * Improve internal logging and reporting for emergency trunk traffic to allow for more rapid impact assessment.

We are currently investigating an issue affecting Call2Teams across multiple regions. At this time, the specific regions and the full extent of the impact are not yet confirmed. This issue may cause intermittent loss of audio at the start of calls or during internal call transfers, impacting both inbound and outbound calls. Our teams are actively working to identify the root cause and implement a resolution. 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 are currently investigating an issue affecting Call2Teams in the EU West region. This issue is causing one‑way or no audio at the start of calls and during internal call transfers, impacting users in the affected area. Our teams are working to identify the root cause and implement a resolution. In parallel, our Platform Engineering team is actively working on implementing an urgent fix, with further updates to follow. 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 are writing to inform you that an issue occurred earlier affecting Call2Teams in the EU region. A mitigation has now been successfully implemented, and services have been restored. This issue may have caused one‑way or no audio at the start of calls or during internal call transfers for users in the affected area. We will continue to monitor the situation closely over 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 currently investigating an issue caused by a bug within our application code. Recent changes introduced by Microsoft appear to have exacerbated the behaviour, which brought the issue to our attention. Our engineering teams are actively working to identify the root cause and implement a fix, with the aim of addressing this today where feasible. As a temporary workaround, limiting usage to a single codec should help minimise impact in the interim. We will provide further updates as more information becomes available. We apologise for any inconvenience caused and appreciate your patience. Dstny Support

Following our previous update, we have now tested a new solution that addresses the identified issue and early results are positive. The fix is currently being validated with a small number of targeted customer accounts. Subject to the outcome of this testing, we expect to provide a further update regarding a wider rollout. In the meantime, the previously shared workaround remains applicable to minimise impact. We will continue to keep you informed as we progress. Thank you for your continued patience. Dstny Support

Due to our deployment pipeline setup, the rollout is expected to take up to one hour from this point, rather than the 30 minutes previously advised. We will provide a further update once the rollout has completed. Thank you for your continued patience and understanding. Dstny Support

Our Platform team has identified the root cause and implemented corrective measures to restore normal service. Customers are not expected to have experienced any impact. A small number may have seen a brief call setup failure during deployment, which would have cleared on redial, or short‑lived re‑registrations as part of normal update behaviour. Service is now stable, and we are moving into a monitoring phase. We will continue to closely monitor availability over the next 24 hours and do not anticipate any further impact at this time. Customers may also revert to their previous codec settings if required. Thank you for your patience and understanding. Dstny Support

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 observed no recurrence or further impact. The root cause has been identified, and preventative measures have been implemented to reduce the risk of a similar issue occurring in future. To provide transparency, a detailed post‑mortem report will be shared 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. Kind regards, Dstny Support

**Incident Summary** From 13:45 UTC on 13th April 2026 until 11:29 UTC on 15th April 2026, a subset of Call2Teams customers experienced intermittent call quality issues. Reported symptoms included one‑way audio, silence at the start of calls or during internal transfers, intermittent static, and in some cases early call termination shortly after connection. While initial reports suggested a possible regional limitation, investigation confirmed that affected scenarios could occur across all regions. Following a series of targeted fixes and monitoring, full service was restored and confirmed stable by 11:29 UTC on 15th April 2026. **Root Cause** The incident was caused by an interaction between a change in Microsoft’s call setup behaviour and a previously latent issue in the Call2Teams call setup logic. Microsoft’s updated codec selection exposed a defect in how our platform handled codec ordering in certain responses, which could create mismatches between the codec signalled to customer phone systems and the codec used towards Microsoft. In parallel, G.722 was being advertised to Microsoft in line with SBC vendor guidance and earlier interoperability assumptions, leading Microsoft to select G.722 in cases where some customer PBXs did not support it. Together, these factors increased real‑time transcoding and contributed to the intermittent audio problems observed. **Incident Resolution** Engineers first reduced unnecessary transcoding by adjusting configuration so that G.722 is only offered to Microsoft when it is explicitly supported by the customer’s phone system. Outside of the standard default codecs \(PCMA and PCMU\), advertised codecs were aligned with each customer’s PBX capabilities, which immediately improved platform stability. A software update was then deployed to correct call setup handling so that codec selections negotiated with Microsoft are maintained consistently when signalled back to customer systems. Following rollout, targeted testing, and monitoring, call quality was confirmed to be stable across all affected scenarios. **Mitigative Actions** We have corrected the call setup logic to prevent incorrect codec re‑ordering from being signalled to customer systems, ensuring that codec selections negotiated with Microsoft are preserved end‑to‑end. We have also reduced unnecessary transcoding by limiting advertised codecs to standard defaults \(PCMA and PCMU\), while conditionally including other codecs, such as G.722, only where they are explicitly supported by the customer’s phone system. In addition, we are reviewing our SBC configuration and internal processes to improve early detection of, and response to, third‑party behavioural changes, strengthening overall service resilience and reducing the likelihood of similar incidents recurring. ### **Timeline**

We are writing to inform you that an issue occurred earlier affecting ConnectMe in EU-West. The incident has been fully resolved, and services have been restored. This may have caused failing outbound calls 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.

**Incident Summary** On 2nd April 2026, between 04:05 UTC and 07:37 UTC, a routine software update in the EU West region led to intermittent call failures for a subset of ConnectMe users. The issue was proactively detected, and service was fully restored after the update was rolled back at 07:37 UTC. All systems were subsequently verified as stable. **Root Cause** The incident was triggered by a routine software update aimed at enhancing service recovery within the ConnectMe platform. During deployment, the update caused an unexpected interaction within the system, leading to a key component becoming unresponsive and resulting in intermittent outbound call failures for some users. **Incident Resolution** The issue was resolved by rolling back the software update to the previous stable version at 07:37 UTC. This action restored normal service for all users. The rollback was performed promptly after the root cause was identified, and service stability was closely monitored to confirm full recovery. **Mitigative Actions** We are refining monitoring to better detect outbound call failures and reviewing the upgrade process to address identified gaps. Backend adjustments will also be made to improve stability in future deployments.