TOPdesk experienced a minor incident on June 19, 2026 affecting Functionality malfunction, lasting 3d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 19, 2026, 06:11 AM UTC
We are currently experiencing disruptions in one of our services. As a result logging in to your TOPdesk environment may not be possible. 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 next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. Log in is currently not working To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 6038.
- investigating Jun 19, 2026, 07:14 AM UTC
We are currently investigating the cause of this issue. We will provide an update as soon as more information becomes available, and no later than 3 hours from now.
- monitoring Jun 19, 2026, 07:48 AM UTC
We have identified the issue and implemented a fix. You should now be able to log in to your TOPdesk environment as expected. If you are still experiencing login issues, please contact our support team and let us know. We will continue to closely monitor the situation to ensure the service remains stable.
- resolved Jun 22, 2026, 07:37 AM UTC
Dear Customer, Over the weekend no further issues have been observed and all services have been operating normally. We therefor close the major. The root cause of this disruption has been identified and a Root Cause Analysis will be posted as soon as this becomes available. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team
- postmortem Jun 24, 2026, 01:43 PM UTC
**Root Cause Analysis:** During a planned service routing migration, a required configuration update for one service was missed. As a result, traffic for that service was routed incorrectly. Because other services remained unaffected and the overall configuration appeared valid, existing monitoring did not detect the issue. The root cause was human error during the configuration update process. **Preventive Measures:** To reduce the risk of similar issues, we will consistently apply the four-eyes principle to all configuration changes and introduce a mandatory post-implementation verification step to ensure all intended updates have been applied correctly before a change is considered complete.