TOPdesk incident

UK1 disruption

Notice Resolved View vendor source →

TOPdesk experienced a notice incident on June 17, 2024 affecting UK1 SaaS hosting location, lasting 54m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2024, 08:55 AM UTC
Resolved
Jun 17, 2024, 09:49 AM UTC
Duration
54m
Detected by Pingoru
Jun 17, 2024, 08:55 AM UTC

Affected components

UK1 SaaS hosting location

Update timeline

  1. investigating Jun 17, 2024, 08:55 AM UTC

    We are currently experiencing problems on our UK1 hosting location. As a result, outgoing mails may be impacted and and some users could also experience performance issues. 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. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com

  2. identified Jun 17, 2024, 09:19 AM UTC

    Our engineers have identified the cause and a fix is being implemented. We will post another update as soon as possible.

  3. resolved Jun 17, 2024, 09:49 AM UTC

    After careful monitoring following the applied solution, we are pleased to inform you that the issue has been completely resolved. We will proceed to evaluate this issue internally. Upon its completion, a Root Cause Analysis (RCA) will be posted on our status page for your reference. If you continue to experience any issues, kindly reach out to our support team for assistance. We appreciate your patience and understanding in this matter.

  4. postmortem Sep 20, 2024, 03:22 PM UTC

    On the morning of June 17th, 2024, at approximately 10:15 CET, we began receiving reports from our customers about being unable to send emails. Additionally, some customers reported experiencing degraded performance. All of these reports originated from SaaS environments hosted in the UK1 data center. Upon receiving these reports, our engineers immediately began an investigation and quickly identified the cause: long-running queries on the SQL server. A fix was implemented at 11:15 CET, leading to an immediate improvement. We are pleased to report that the main issue was fully resolved by 11:50 CET. The entire disruption, from the initial report to the final resolution, lasted approximately one hour.