Update - Dear customer,

The issue where "broken images" in incidents action fields prevent you from saving the incident card has been fixed by development.
The version for this fix is 16.06.008.

A work around is available for this bug.

Work around:
⒈Locate the broken images in the action fields of the progress trail.
The broken image will look like a square box with a border around it.
⒉Delete the broken images
⒊Submit the correcte action field
⒋Repeat if more action fields are affected
⒌Save the card

Our apologies for the inconvenience. At the time of writing the fix is part of our release cycle. 
We cannot yet say when exactly the release will be available. Expected release is by the end of week 25.

Jun 11, 2026 - 14:38 CEST
Update - Dear customer,
The issue where "broken images" in incidents action fields prevent you from saving the incident card has been fixed by development.
The version for this fix has yet to be announced. 
We expect this to be known tomorrow.

Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk.

We will try to keep you updated where possible.

Jun 10, 2026 - 15:59 CEST
Update - We are currently experiencing disruptions with saving incident cards.
It may occur that Incident cards that contain a "broken image" cannot be saved.

An error pops up stating to check the log files.
To see if you are affected by this disruption, check if your Incident contains action fields with "broken images"
These images look like an empty box with gray border.

The logs files state the following error:
'The given index must be of a Image token'

The error was introduced in version 16.06.001

A work around is also available for this bug.
Work around:
⒈Locate the broken images in the action fields
⒉Delete the broken images
⒊Save the card


Development is actively investigating the issue and will produce a fix as soon as possible.

Our apologies for the inconvenience

Jun 10, 2026 - 11:16 CEST
Investigating - We are currently experiencing disruptions with incidents that cannot be saved due to empty images in the action field.

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 this will be solved.

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

Jun 09, 2026 - 17:06 CEST
Update - Dear customer,

The issue where some incidents with empty action fields cannot be saved has been fixed.
The fix will be available in version 16.06.007

A work around is available for this bug.

Work around:
⒈Locate the empty action fields of the progress trail.
⒉Fill the field with a dummy value
⒊Submit the correcte action field
⒋Delete the corrected action field
⒌Repeat if more action fields are affected
⒍Save the card

The fix will be available in version 16.06.007
Our apologies for the inconvenience. At the time of writing the fix is part of our release cycle. 
We cannot yet say when exactly the release will be available. Expected release is start of week 25.

Jun 11, 2026 - 12:42 CEST
Update - Dear customer,
The issue where some incidents with empty action fields cannot be saved has been fixed.
The fix will be available in version 16.06.007

Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk.

We will try to keep you updated where possible.

Jun 10, 2026 - 15:57 CEST
Investigating - We are currently experiencing disruptions with saving incident cards.
It may occur that Incident cards that contain an empty action field cannot be saved.

An error pops up stating to check the log files.
To see if you are affected by this disruption, check if your Incident contains empty action fields, or check the logs for the following error:
'plainText is marked non-null but is null'

Development has created a fix that will be introduced in version 16.06.007.

A work around is also available for this bug.
Work around:
⒈Locate the empty action field
⒉Delete it
⒊If deletion is not yet possible, fill the empty field and then delete or save the card.

Our apologies for the inconvenience

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

Jun 10, 2026 - 09:38 CEST
Update - Dear customers,
As announced last week, the fix for the Adobe Plugin issue was announced.

Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk.
Hopefully most/all update groups will have the correct version on Friday.

We will try to keep you updated where possible.

Jun 10, 2026 - 16:01 CEST
Update - The issue where Operators where unable to use TOPdesk who had the Adobe Extension active in Chrome, is tested and ready.
Our fix will be introduced in TOPdesk version 16.06.004.

When your TOPdesk has reached this version, you can turn the Extension on again in the Chrome Extension.

Our apologies for the inconvenience.

Jun 05, 2026 - 09:54 CEST
Update - Update: a workaround has been implemented, and the fix will be rolled out with the next release.
The next version will usually be release within the next week.

Jun 03, 2026 - 13:42 CEST
Investigating - We are currently experiencing disruptions with the Adobe PDF plugin version 26.5.2.0 
Customers experience issues login in as an Operator. The page will infinitely buffer.

Turning off the browser plugin/extension and restarting your browser will resolve the issue for now.
We will investigate further and will update you on the fix.

Our apologies for the inconvenience. 
Please find the latest updates on our TOPdesk Status Page: https://status.topdesk.com

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

Jun 03, 2026 - 08:53 CEST

About This Site

This page shows the current status of our TOPdesk SaaS infrastructure.
You can subscribe for updates for your relevant hosting locations at the top right of the page. To see which hosting location is used for your environment, see the SaaS hosting details on My TOPdesk.

This page displays disruptions affecting groups of customers. For detailed information regarding your TOPdesk SaaS environment, see the My TOPdesk monitoring page.

Also see
TOPdesk Support contact details | TOPdesk SaaS information website | TOPdesk product release notes

AU1 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
BR1 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
CA1 SaaS hosting location Operational
90 days ago
99.92 % uptime
Today
EU1 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
EU2 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
EU3 SaaS hosting location Operational
90 days ago
99.73 % uptime
Today
EU4 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
EU5 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
EU6 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
NO1 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
UK2 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
US2 SaaS hosting location Operational
90 days ago
100.0 % uptime
Today
My TOPdesk Operational
90 days ago
99.98 % uptime
Today
Functionality malfunction Partial Outage
General notifications Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jun 14, 2026

No incidents reported today.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026

Unresolved incidents: Major - Cannot save incident card with empty action fields, Major Incident: Can't save incident/Empty image.

Jun 10, 2026
Resolved - The issue has been resolved, and all affected services are operating normally again. Thank you for your patience and understanding. If you have any questions, our Support team is happy to help.
Jun 10, 13:18 CEST
Investigating - We are currently experiencing connectivity issues affecting our Delft office. As a result, myTOPdesk.com and our Support telephone line are currently unavailable.

We are investigating the issue and working to restore these services as quickly as possible.

We apologize for the inconvenience and will provide updates as more information becomes available.

Jun 10, 12:15 CEST
Jun 9, 2026
Resolved - The access to my.topdesk has been restored. The issues caused by the maintenance on the 6th-7th of June have been resolved.
The cause will be evaluated to prevent similar issues in the future.


We apologize again for any inconvenience and thank you for your patience.

Jun 9, 15:23 CEST
Investigating - We are currently experiencing disruptions with access to my.topdesk.com

Over the weekend (June 6th to 7th), we scheduled maintenance to update our AD FS and MiM systems. During this process, we encountered several issues that we have not yet resolved. We are actively working to restore access to My TOPdesk as swiftly as possible.

Currently, login to My TOPdesk is temporarily unavailable

If you would like to register an incident with support, please send an email to support@topdesk.com

Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when My TOPdesk 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.

Jun 8, 10:11 CEST
Jun 8, 2026
Jun 7, 2026

No incidents reported.

Jun 6, 2026
Postmortem - Read details
Jun 12, 11:30 CEST
Resolved - This incident has been resolved.
Jun 6, 22:23 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 6, 22:23 CEST
Update - All environments are accessible again. Root cause analysis will be published within a week.
Jun 6, 22:19 CEST
Update - We have identified an issue in the load balancer for the services cluster. We are working on resolving this issue.
Jun 6, 22:04 CEST
Update - We are continuing to investigate this issue.
Jun 6, 21:51 CEST
Update - We are continuing to investigate this issue.
Jun 6, 21:17 CEST
Update - We are continuing to investigate this issue.
Jun 6, 20:40 CEST
Update - We are currently investigation the cause of this outage. We will keep you updates every 30 minutes
Jun 6, 20:28 CEST
Update - We are continuing to investigate this issue.
Jun 6, 20:27 CEST
Investigating - TOPdesk environment unreachable for hosting location in Canada
Jun 6, 20:26 CEST
Jun 5, 2026
Jun 4, 2026

No incidents reported.

Jun 3, 2026
Jun 2, 2026

No incidents reported.

Jun 1, 2026
Resolved - We have continued to monitor the import services following the reported issues and have not observed any further occurrences. Everything is operating as expected.

As no additional problems have been identified, we will proceed with closing this major.

Jun 1, 14:12 CEST
Monitoring - We have restarted the import service and are seeing improvements in the performance.
Imports can now executed again.

We will continue to monitor the situation.

Jun 1, 13:12 CEST
Investigating - We are currently experiencing a disruption to the import service on EU1.

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 039.

Jun 1, 09:15 CEST
May 31, 2026
Completed - The scheduled maintenance has been completed.
May 31, 14:00 CEST
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
May 31, 13:58 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 31, 12:00 CEST
Scheduled - We will perform maintenance on one of our internal tools. During this time, automated jobs like the restart of your TOPdesk may be delayed or might not work. The availability of your TOPdesk environment will not be affected.
May 22, 20:38 CEST