TOPdesk incident

RESOLVED: CA1 datacenter + ‘404 NGINX'

Major Resolved View vendor source →

TOPdesk experienced a major incident on June 25, 2026 affecting Functionality malfunction, lasting 32m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 03:31 PM UTC
Resolved
Jun 25, 2026, 04:03 PM UTC
Duration
32m
Detected by Pingoru
Jun 25, 2026, 03:31 PM UTC

Affected components

Functionality malfunction

Update timeline

  1. investigating Jun 25, 2026, 03:31 PM UTC

    We are currently experiencing problems on our CA1 datacenter. As a result your TOPdesk environment may not be available. 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. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 8482.

  2. resolved Jun 25, 2026, 04:03 PM UTC

    The issue has been resolved, and all instances should be reachable again. We will publish an RCA as soon as this matter has been evaluated internally. Our apologies for the inconveniences.

  3. postmortem Jun 26, 2026, 03:46 PM UTC

    As part of planned infrastructure improvements to our Canada environment, a previously postponed configuration change was unintentionally applied during a routine service update. Because this change depended on infrastructure that had not yet been deployed in the Canada environment, customer traffic could not be routed correctly, resulting in service interruptions. Once the issue was identified, the configuration change was immediately rolled back, restoring normal service. We have also updated our deployment process to prevent postponed configuration changes from being applied unintentionally in the future.