NL4 degraded performance

We are pleased to announce that, following a few hours of close observation, the system has shown consistent stability. We apologize for any inconvenience this may have caused and thank you for your patience and understanding.

The major incident will now be closed, and an internal evaluation will be conducted. Once the evaluation is complete, a detailed root cause analysis will be published.

We are pleased to inform you that our engineers have not detected any further issues this morning. The system is currently stable, and we will continue to monitor it closely.
We are still awaiting a response from Leaseweb regarding the investigation into the host machine.

If you experience any signs of degraded performance with TOPdesk, please do not hesitate to contact our Support department.

We will provide further updates as soon as more information becomes available.
Thank you for your patience and understanding.

While we have made some progress, the root cause has not yet been identified. Our investigation is ongoing as we carefully examine various potential factors that could be contributing to this issue. We are working closely with Leaseweb to ensure a comprehensive analysis.

For now, we will continue to monitor the situation and provide further updates as soon as more information becomes available.

Thank you for your patience and understanding.

Our team is actively working to determine the cause of the significantly higher CPU usage observed today compared to last week.

Concurrently, Leaseweb is conducting a thorough investigation of the affected Virtual Machines.

We appreciate your patience and understanding. Further updates will be provided as soon as more information becomes available.

We have identified a potential cause for the disruption: a significant number of API calls were being made, which coincided with the period of high CPU usage.
Once these API calls ceased, the CPU usage on the affected application server dropped significantly, and the CPU usage on other application servers also returned to stable levels.

While this finding is promising, we are continuing to investigate and will be reaching out to relevant parties to gather more information to confirm if this is indeed the root cause.

We appreciate your patience and will provide further updates as soon as we have more details.

Our engineers are continuing to investigate the issue with degraded performance on NL4.

Around 11:55 CET, we observed a significant drop in CPU usage on several application servers, and the system has appeared more stable since then.

We will remain in close contact with Leaseweb and continue to closely monitor the situation.

The next update will be posted as soon as we have more information.

Leaseweb is currently conducting an internal investigation on the affected machines.

While a few customers have reported that their TOPdesk is stable again, we cannot guarantee that this stability will persist until we identify and completely resolve the root cause of the issue.

We appreciate your patience and will continue to provide updates as we make progress.

Our engineers are actively investigating the cause of the unresponsiveness in TOPdesk environments on NL4. To mitigate the impact, we have re-allocated resources.

Additionally, we have reached out to Leaseweb to review the affected Virtual Machines.

We will continue to monitor closely and provide another update as soon as possible.

We are currently experiencing issues at the NL4 hosting location, which may result in your TOPdesk environment being slower than usual or temporarily unavailable.

We are aware of the problem and are working on a solution.

Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. We aim to update this status page every 30 minutes until the issue has been resolved.

E-mail updates will be sent when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates.

To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR24 09 2495.