All Systems Operational

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

Uptime over the past 90 days. View historical uptime.
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
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.

No incidents or maintenance related to this downtime.

Jun 26, 2026

No incidents reported today.

Jun 25, 2026
RESOLVED: CA1 datacenter + ‘404 NGINX'
Postmortem - Read details
Jun 26, 17:46 CEST
Resolved - 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.
Jun 25, 18:03 CEST
Investigating - 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.
Jun 25, 17:31 CEST
Jun 24, 2026

No incidents reported.

Jun 23, 2026
RESOLVED: Major Incident: Can't save incident/Empty image
Resolved - Dear Customers,

as communicated before, a fix for the not savable incidents issue has been released.
Due to the TOPdesk release cycle, it took some time to ensure that all environments were updated to the required version.
We are pleased to confirm that version 16.06.008 has now been deployed to all TOPdesk environments.

This update resolves the issue that prevented operators from saving incidents that contain broken images.

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
Jun 23, 15:26 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 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, 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, 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, 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 9, 17:06 CEST
Jun 22, 2026
RESOLVED: Major - Unable to log in
Postmortem - Read details
Jun 24, 16:39 CEST
Resolved - 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
Jun 22, 09:37 CEST
Monitoring - 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.
Jun 19, 09:48 CEST
Update - 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.
Jun 19, 09:14 CEST
Investigating - 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.
Jun 19, 08:11 CEST
Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026
RESOLVED: Major - Cannot save incident card with empty action fields
Resolved - Dear customer,

The issue where some incidents with empty action fields cannot be saved has been fixed.
The fixed version is 16.06.007 and has been released to all customer environments.

This issue will be thoroughly evaluated to prevent these issues in the future.

Our apologies for the inconvenience and thank you for you patience.
Jun 19, 10:19 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, 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, 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, 09:38 CEST
Jun 18, 2026

No incidents reported.

Jun 17, 2026
RESOLVED: Major - Operator Login fails due to Adobe Plugin
Resolved - Dear Customers,

As communicated last week, a fix for the Adobe Plugin issue has been released.
Due to the TOPdesk release cycle, it took some time to ensure that all environments were updated to the required version.
We are pleased to confirm that version 16.06.004 has now been deployed to all TOPdesk environments.

This update resolves the issue that prevented operators from logging in when the Adobe Plugin was enabled.
You may now safely re-enable the Adobe Plugin.

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
Jun 17, 09:56 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, 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 5, 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 3, 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 3, 08:53 CEST
Jun 16, 2026

No incidents reported.

Jun 15, 2026

No incidents reported.

Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage