Get email notifications whenever TOPdesk SaaS Status page creates, updates or resolves an incident.
Get text message notifications whenever TOPdesk SaaS Status page creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever TOPdesk SaaS Status page creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
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
TOPdesk Australia
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.99
% uptime
Today
EU1 SaaS hosting location
Operational
90 days ago
99.85
% uptime
Today
NL3 SaaS hosting location
Operational
NL3 hosting location
https://www.leaseweb.com/platform/data-centers/ams-01
90 days ago
97.69
% uptime
Today
NL4 SaaS hosting location
Operational
NL4 SaaS hosting location
90 days ago
100.0
% uptime
Today
NO1 SaaS hosting location
Operational
Our hosting location in Norway
90 days ago
100.0
% uptime
Today
UK1 SaaS hosting location
Operational
90 days ago
99.78
% uptime
Today
US1 SaaS hosting location
Operational
90 days ago
99.95
% uptime
Today
My TOPdesk
Operational
The TOPdesk customer portal: https://my.topdesk.com
90 days ago
99.88
% uptime
Today
General notifications
Operational
Subscribe for general notifications regarding our SaaS hosting, like new sub processors, new features, etc.
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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Oct 5, 2023
No incidents reported today.
Oct 4, 2023
Resolved -
We would like to provide another update about the ongoing issues in our NL3 hosting location.
Over the course of the last 2 days, we have been migrating the majority of hosted production environments to our new messaging system, with positive results.
We are continuing the migration of all eligible environments as quickly as possible. This means that we will migrate all test environments this upcoming night to the new messaging system.
Our engineers are monitoring the performance of the old and the new messaging system.
The Checklists feature (TOPdesk Labs) which is used by a small subset of customers is still using the old messaging system but will be migrated in the next weeks.
We are working on phasing out the old messaging system with the highest priority and we expect to finish this in the near future.
Should you still encounter issues with the Checklists or Action Sequences, please contact TOPdesk Support.
Once the ongoing issues are successfully resolved, we will publish a Root Cause Analysis (RCA) report on the Status page (https://status.topdesk.com).
Oct 4, 16:32 CEST
Over the course of the last 2 days, we have been migrating the majority of hosted production environments to our new messaging system, with positive results.
We are continuing the migration of all eligible environments as quickly as possible. This means that we will migrate all test environments this upcoming night to the new messaging system.
Our engineers are monitoring the performance of the old and the new messaging system.
The Checklists feature (TOPdesk Labs) which is used by a small subset of customers is still using the old messaging system but will be migrated in the next weeks.
We are working on phasing out the old messaging system with the highest priority and we expect to finish this in the near future.
Should you still encounter issues with the Checklists or Action Sequences, please contact TOPdesk Support.
Once the ongoing issues are successfully resolved, we will publish a Root Cause Analysis (RCA) report on the Status page (https://status.topdesk.com).
Oct 4, 16:32 CEST
Update -
After monitoring the situation we can now conclude that the issues with our messaging system are resolved and that action sequences are operational again
Starting tonight, over the course of the next 2 days, we will migrate all eligible environments to the new messaging system.
We expect this action will mitigate the main issues with messaging and action sequences that have occurred over the past period for those environments.
We will continue to monitor the situation and keep this major open for further investigations and until mitigations has been successfully implemented.
Oct 2, 15:59 CEST
Starting tonight, over the course of the next 2 days, we will migrate all eligible environments to the new messaging system.
We expect this action will mitigate the main issues with messaging and action sequences that have occurred over the past period for those environments.
We will continue to monitor the situation and keep this major open for further investigations and until mitigations has been successfully implemented.
Oct 2, 15:59 CEST
Monitoring -
Our engineers have successfully rebooted the messaging system which is necessary for the full functionality of Action Sequences.
Messages that were sent during the disruption are stored in the queue of the message system.
We are currently processing this queue in fast pace.
We expect that Action Sequences will be processed, but in a delayed manner.
Since the messages stored in the message system are now being processed, we will start monitoring the system.
Please reach out to TOPdesk Support if you still have issues within TOPdesk
Oct 2, 11:05 CEST
Messages that were sent during the disruption are stored in the queue of the message system.
We are currently processing this queue in fast pace.
We expect that Action Sequences will be processed, but in a delayed manner.
Since the messages stored in the message system are now being processed, we will start monitoring the system.
Please reach out to TOPdesk Support if you still have issues within TOPdesk
Oct 2, 11:05 CEST
Update -
We are continuing to investigate this issue.
Oct 2, 10:38 CEST
Oct 2, 10:38 CEST
Update -
Our engineers are actively continuing their investigation of the issue.
We sincerely apologize for any inconvenience this may have caused.
Next update will be 11:00
Oct 2, 10:11 CEST
We sincerely apologize for any inconvenience this may have caused.
Next update will be 11:00
Oct 2, 10:11 CEST
Investigating -
We are currently experiencing problems with action sequences on the NL3 hosting location.
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.
E-mail updates will be sent 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 TDR23 09 7797.
Oct 2, 09:57 CEST
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.
E-mail updates will be sent 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 TDR23 09 7797.
Oct 2, 09:57 CEST
Oct 3, 2023
No incidents reported.
Oct 2, 2023
Resolved -
After monitoring the situation, we can now conclude that the issue on US1 has been resolved.
If you still experience issues, please reach out to our Support department.
Oct 2, 16:03 CEST
If you still experience issues, please reach out to our Support department.
Oct 2, 16:03 CEST
Monitoring -
Our engineers has implemented a mitigation.
The affected environments should now be back online.
We apologize for any inconvenience this issue might have caused.
We will now monitor the situation.
Oct 2, 15:40 CEST
The affected environments should now be back online.
We apologize for any inconvenience this issue might have caused.
We will now monitor the situation.
Oct 2, 15:40 CEST
Investigating -
We are currently experiencing problems on the US1 hosting location. 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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 10 337.
Oct 2, 15:18 CEST
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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 10 337.
Oct 2, 15:18 CEST
Oct 1, 2023
No incidents reported.
Sep 30, 2023
No incidents reported.
Sep 29, 2023
Resolved -
We would like to provide you with another update about the ongoing issues with Actions Sequences at our NL3 hosting location.
After closely monitoring the performance of the environments that were moved last night to the new messaging system, our engineers will continue with the phased rollout and will move a second subset of environments to this new system starting this upcoming Sunday starting at 22:30h CEST.
Our engineers monitored the performance of the current messaging system today and no issues arose. Therefore we will close this major but we'll continue to monitor the situation throughout the weekend.
Our apologies for any inconvenience.
Sep 29, 16:28 CEST
After closely monitoring the performance of the environments that were moved last night to the new messaging system, our engineers will continue with the phased rollout and will move a second subset of environments to this new system starting this upcoming Sunday starting at 22:30h CEST.
Our engineers monitored the performance of the current messaging system today and no issues arose. Therefore we will close this major but we'll continue to monitor the situation throughout the weekend.
Our apologies for any inconvenience.
Sep 29, 16:28 CEST
Monitoring -
We would like to provide you with another update about the ongoing issues with Action Sequences at our NL3 hosting location.
We've successfully migrated a subset of customers last night, that had issues with Action Sequences, to the new messaging system. Our engineers are closely monitoring the situation and we don't see any issues at the moment.
We will evaluate the situation later today and decide if we move forward with the phased rollout of the new messaging system and move another set of SaaS environments to this new messaging system.
We will keep you updated.
Sep 29, 11:50 CEST
We've successfully migrated a subset of customers last night, that had issues with Action Sequences, to the new messaging system. Our engineers are closely monitoring the situation and we don't see any issues at the moment.
We will evaluate the situation later today and decide if we move forward with the phased rollout of the new messaging system and move another set of SaaS environments to this new messaging system.
We will keep you updated.
Sep 29, 11:50 CEST
Update -
We have identified a subset of environments that were most impacted by the recent disruption and have scheduled a priority roll out to new messaging system for these environments tonight.
Our engineers updated the configuration of our current messaging system, which will also receive a restart this evening and expect a positive impact.
During the service window, we will be restarting the subset of environments that are switching to the new messaging system.
We have a rollback scenario in place for the environments that will be switched to the new messaging system.
We will keep you updated on the progress.
Sep 28, 18:20 CEST
Our engineers updated the configuration of our current messaging system, which will also receive a restart this evening and expect a positive impact.
During the service window, we will be restarting the subset of environments that are switching to the new messaging system.
We have a rollback scenario in place for the environments that will be switched to the new messaging system.
We will keep you updated on the progress.
Sep 28, 18:20 CEST
Identified -
We’ve decided to move forward with the rollout of the new messaging system for all environments that have the required version which supports the messaging system (All customers within the continuous deployment update group).
Next week we will roll out more structural improvements to our current messaging system. Even though we are adding more structural improvements, our goal is to eventually phase out this messaging system and replacing it with the new system.
We have executed a risk assessment on phasing out our current messaging system. We are currently mitigating the risks and therefore it will be a phased rollout.
We will keep you updated on the progress.
Our apologies for the inconvenience.
Sep 28, 15:42 CEST
Next week we will roll out more structural improvements to our current messaging system. Even though we are adding more structural improvements, our goal is to eventually phase out this messaging system and replacing it with the new system.
We have executed a risk assessment on phasing out our current messaging system. We are currently mitigating the risks and therefore it will be a phased rollout.
We will keep you updated on the progress.
Our apologies for the inconvenience.
Sep 28, 15:42 CEST
Update -
We would like to give a general update on what has been going on with the messaging system and where we are currently at:
This morning our messaging system, which is responsible for sending action sequences, was restarted.
During the restart, the queue within the messaging system increased. The system is designed so things will eventually be executed, but because of a backlog of messages this took longer than expected. We improved the capacity for forwarding messages, which should mitigate the backlog.
We are aware of certain drawbacks of our messaging system. Therefore we have a new system ready to be rolled out, but due to old TOPdesk versions this can not be done seamlessly.
If we want to do this seamlessly we need a few more weeks to implement the structural improvements to our infrastructure.
Today we'll discuss whether we want to shorten this timeline, accepting the downsides that this has for customers on older versions.
For now, our engineers are working with the highest priority to mitigate this issue.
Our apologies for the inconvenience.
Sep 28, 11:33 CEST
This morning our messaging system, which is responsible for sending action sequences, was restarted.
During the restart, the queue within the messaging system increased. The system is designed so things will eventually be executed, but because of a backlog of messages this took longer than expected. We improved the capacity for forwarding messages, which should mitigate the backlog.
We are aware of certain drawbacks of our messaging system. Therefore we have a new system ready to be rolled out, but due to old TOPdesk versions this can not be done seamlessly.
If we want to do this seamlessly we need a few more weeks to implement the structural improvements to our infrastructure.
Today we'll discuss whether we want to shorten this timeline, accepting the downsides that this has for customers on older versions.
For now, our engineers are working with the highest priority to mitigate this issue.
Our apologies for the inconvenience.
Sep 28, 11:33 CEST
Investigating -
We are currently experiencing problems with action sequences on the NL3 hosting location.
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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 09 7797.
Sep 28, 10:15 CEST
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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 09 7797.
Sep 28, 10:15 CEST
Resolved -
The services have been restored.
Sep 29, 07:29 CEST
Sep 29, 07:29 CEST
Update -
Our engineers are still working on this outage.
A new status update will follow if anything changes.
Sep 29, 06:57 CEST
A new status update will follow if anything changes.
Sep 29, 06:57 CEST
Investigating -
We are currently experiencing problems on the UK1C03 hosting location. 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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 09 8108.
Sep 29, 06:13 CEST
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. We aim to update this status page every 30 minutes until the issue has been resolved.
E-mail updates will be sent 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 TDR23 09 8108.
Sep 29, 06:13 CEST
Sep 28, 2023
Resolved -
After a full day of monitoring the situation our engineers have concluded that this issue is resolved.
Therefore we will close this incident.
If you still experience any issues relating the Checklists or Action Sequences within your TOPdesk environment, please reach out to TOPdesk Support.
A postmortem will follow once the evaluation is completed.
Sep 28, 09:18 CEST
Therefore we will close this incident.
If you still experience any issues relating the Checklists or Action Sequences within your TOPdesk environment, please reach out to TOPdesk Support.
A postmortem will follow once the evaluation is completed.
Sep 28, 09:18 CEST
Update -
Our engineers do not see any issues with our messaging system and Action Sequences are fully operational.
We will continue to monitor the situation.
Please reach out to TOPdesk Support if you still have issues within TOPdesk
Sep 27, 11:09 CEST
We will continue to monitor the situation.
Please reach out to TOPdesk Support if you still have issues within TOPdesk
Sep 27, 11:09 CEST
Monitoring -
Our engineers have been monitoring the situation and all issues seem to be mitigated.
The restart of the messaging system has been scheduled for 21:00 CEST, this evening.
Once this restart has concluded, all TOPdesk environments will be restarted during the Service Window tonight.
Please reach out to TOPdesk Support if you still have issues within TOPdesk after the restart.
We will continue to monitor the situation.
Sep 26, 16:44 CEST
The restart of the messaging system has been scheduled for 21:00 CEST, this evening.
Once this restart has concluded, all TOPdesk environments will be restarted during the Service Window tonight.
Please reach out to TOPdesk Support if you still have issues within TOPdesk after the restart.
We will continue to monitor the situation.
Sep 26, 16:44 CEST
Update -
Our engineers have investigated the messaging queue system and have concluded that all issues should be mitigated.
Any new issues will be investigated separately by our Support team.
This evening we will be restarting the messaging system to force changes made by our engineers. This might cause a delay within the messaging system.
Once the messaging system has rebooted, all environments will get a restart during the Service Window tonight.
Our apologies for the inconvenience.
Sep 26, 12:07 CEST
Any new issues will be investigated separately by our Support team.
This evening we will be restarting the messaging system to force changes made by our engineers. This might cause a delay within the messaging system.
Once the messaging system has rebooted, all environments will get a restart during the Service Window tonight.
Our apologies for the inconvenience.
Sep 26, 12:07 CEST
Update -
We are still getting reports from customers that Action Sequences and the Checklists are encountering issues.
The scheduled restart of the TOPdesk environments last night has helped clear most of the messages in the queue.
Our engineers are working on this issue with the highest priority.
Please reach out to TOPdesk Support if you still have issues with Action Sequences or Checklists within TOPdesk.
Sep 26, 09:23 CEST
The scheduled restart of the TOPdesk environments last night has helped clear most of the messages in the queue.
Our engineers are working on this issue with the highest priority.
Please reach out to TOPdesk Support if you still have issues with Action Sequences or Checklists within TOPdesk.
Sep 26, 09:23 CEST
Update -
The ongoing issues are currently only affecting the Checklists (Lab Feature) subsystem within TOPdesk. The issues with Action Sequences should be mitigated. If you still encounter issues with the Action Sequences please reach out to TOPdesk Support.
To address the problems with the Checklists feature, we will schedule a restart of the TOPdesk environments we suspect difficulties (messages in the queue) with this subsystem during our Service Window tonight.
We will provide another update tomorrow morning.
Sep 25, 16:34 CEST
To address the problems with the Checklists feature, we will schedule a restart of the TOPdesk environments we suspect difficulties (messages in the queue) with this subsystem during our Service Window tonight.
We will provide another update tomorrow morning.
Sep 25, 16:34 CEST
Update -
Our engineers have successfully rebooted the messaging system which is necessary for the full functionality of Action Sequences. We see a subset of messages still in the queue, indicating that a small group of customers are still facing issues.
Please reach out to TOPdesk Support if you still have issues with Action Sequences or Checklists within TOPdesk.
Sep 25, 14:08 CEST
Please reach out to TOPdesk Support if you still have issues with Action Sequences or Checklists within TOPdesk.
Sep 25, 14:08 CEST
Update -
We are currently reaching the limit of our internal message system which is crucial for communicating and processing of Action Sequences within TOPdesk.
Last weekend we rebooted the internal message system for all TOPdesk environments in our NL3 hosting location, which mitigated the issue for the majority of our customers. Due to peak load the issue persists in some TOPdesk environments. Our engineers are currently restarting this message system, but in a staged manner to prevent peak load again.
Messages that were sent during the disruption are stored in the queue of the message system. We are currently processing this queue in fast pace. We expect that Action Sequences will be processed, but in a delayed manner.
At the same time, we are implementing a more reliable and future proof message system in a staged roll-out.
Our apologies for the inconvenience. We will provide an update around 2:00 PM CEST.
Sep 25, 12:05 CEST
Last weekend we rebooted the internal message system for all TOPdesk environments in our NL3 hosting location, which mitigated the issue for the majority of our customers. Due to peak load the issue persists in some TOPdesk environments. Our engineers are currently restarting this message system, but in a staged manner to prevent peak load again.
Messages that were sent during the disruption are stored in the queue of the message system. We are currently processing this queue in fast pace. We expect that Action Sequences will be processed, but in a delayed manner.
At the same time, we are implementing a more reliable and future proof message system in a staged roll-out.
Our apologies for the inconvenience. We will provide an update around 2:00 PM CEST.
Sep 25, 12:05 CEST
Update -
We are still experiencing intermittent issues with Action Sequences or Checklists (Labs feature) at our NL3 hosting location. Our engineers are working on this issue with the highest priority.
Our apologies for the inconvenience.
Sep 25, 09:50 CEST
Our apologies for the inconvenience.
Sep 25, 09:50 CEST
Update -
We are still investigating the issue.
We apologize for any inconvenience.
Next update: 16:30
Sep 22, 15:31 CEST
We apologize for any inconvenience.
Next update: 16:30
Sep 22, 15:31 CEST
Update -
We are still investigating the issue.
We apologize for any inconvenience.
Next update: 15:00
Sep 22, 14:17 CEST
We apologize for any inconvenience.
Next update: 15:00
Sep 22, 14:17 CEST
Update -
We are continuing to investigate this issue.
Sep 22, 13:29 CEST
Sep 22, 13:29 CEST
Update -
Our engineers are still investigating the issue.
We sincerely apologize for any inconvenience.
Next update will be 14:00
Sep 22, 12:52 CEST
We sincerely apologize for any inconvenience.
Next update will be 14:00
Sep 22, 12:52 CEST
Update -
We are still investigating the issue.
We apologize for any inconvenience.
Next update will be 12:30
Sep 22, 11:42 CEST
We apologize for any inconvenience.
Next update will be 12:30
Sep 22, 11:42 CEST
Update -
We are continuing the investigation.
Next update will be at 11:30
Sep 22, 11:00 CEST
Next update will be at 11:30
Sep 22, 11:00 CEST
Update -
Our engineers are actively continuing their investigation of the issue.
We sincerely apologize for any inconvenience this may have caused.
Next update will be 11:00
Sep 22, 10:16 CEST
We sincerely apologize for any inconvenience this may have caused.
Next update will be 11:00
Sep 22, 10:16 CEST
Investigating -
We are currently experiencing issues with action sequences not triggering at our NL3 hosting location
We are aware of the problem and are investigating.
Our apologies for the inconvenience. We aim to update this status blog at least every 30 minutes until the issue has been resolved.
To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR23 09 6210.
Sep 22, 09:56 CEST
We are aware of the problem and are investigating.
Our apologies for the inconvenience. We aim to update this status blog at least every 30 minutes until the issue has been resolved.
To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR23 09 6210.
Sep 22, 09:56 CEST
Sep 27, 2023
Resolved -
A fix has been implemented.
MyTOPdesk is now available.
Our apologies for the inconvenience.
Sep 27, 14:44 CEST
MyTOPdesk is now available.
Our apologies for the inconvenience.
Sep 27, 14:44 CEST
Identified -
MyTOPdesk is currently unavailable due to a network issue.
Our engineers have identified the issue and are implementing a fix.
In the meantime, please contact us via e-mail until this issue is fixed.
Our apologies for the inconvenience.
Sep 27, 13:31 CEST
Our engineers have identified the issue and are implementing a fix.
In the meantime, please contact us via e-mail until this issue is fixed.
Our apologies for the inconvenience.
Sep 27, 13:31 CEST
Update -
MyTOPdesk is currently unavailable due to a network issue.
Our engineers are still working on a fix.
In the meantime, please contact us via e-mail until this issue is fixed.
Our apologies for the inconvenience.
Sep 27, 12:41 CEST
Our engineers are still working on a fix.
In the meantime, please contact us via e-mail until this issue is fixed.
Our apologies for the inconvenience.
Sep 27, 12:41 CEST
Investigating -
MyTOPdesk is currently unavailable due to a network issue.
Our engineers are currently working on a fix.
Our apologies for the inconvenience.
Sep 27, 12:13 CEST
Our engineers are currently working on a fix.
Our apologies for the inconvenience.
Sep 27, 12:13 CEST
Sep 26, 2023
Sep 25, 2023
Sep 24, 2023
No incidents reported.
Sep 23, 2023
Completed -
The scheduled maintenance has been completed.
Sep 23, 12:00 CEST
Sep 23, 12:00 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 23, 09:00 CEST
Sep 23, 09:00 CEST
Scheduled -
Due to system updates, the MyTOPdesk customer portal will be unavailable for some time in the morning.
The updates will take place between 09:00 CEST and 12:00 CEST.
This maintenance work will not affect the availability of SaaS environments.
Sep 18, 15:49 CEST
The updates will take place between 09:00 CEST and 12:00 CEST.
This maintenance work will not affect the availability of SaaS environments.
Sep 18, 15:49 CEST
Sep 22, 2023
Resolved -
After monitoring the situation, we can now conclude that the issue on UK1C05 has been resolved.
If you still experience issues, please reach out to our Support department.
Sep 22, 14:02 CEST
If you still experience issues, please reach out to our Support department.
Sep 22, 14:02 CEST
Monitoring -
We are maintaining continuous monitoring of the situation.
Sep 22, 13:47 CEST
Sep 22, 13:47 CEST
Update -
We have identified the problem, implemented a fix, and are currently monitoring the situation.
Sep 22, 13:42 CEST
Sep 22, 13:42 CEST
Update -
We are currently investigating an issue within the database cluster
Sep 22, 13:24 CEST
Sep 22, 13:24 CEST
Investigating -
We are currently experiencing problems on UK1C05 as a result your TOPdesk environment may not be available.
We are aware of the problem and are working on a solution.
To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR23 09 6356.
Sep 22, 13:12 CEST
We are aware of the problem and are working on a solution.
To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR23 09 6356.
Sep 22, 13:12 CEST
Sep 21, 2023
Resolved -
The fix is working as intended and queued actions have been processed.
We apologize for any inconvenience this issue may have caused.
Sep 21, 14:43 CEST
We apologize for any inconvenience this issue may have caused.
Sep 21, 14:43 CEST
Monitoring -
The fix has been implemented.
As it will take a while until the queued actions will all have been processed, delays can still be experienced for some time.
We'll monitor the situation at least for the next hour.
Sep 21, 13:52 CEST
As it will take a while until the queued actions will all have been processed, delays can still be experienced for some time.
We'll monitor the situation at least for the next hour.
Sep 21, 13:52 CEST
Update -
The fix has been implemented.
As it will take a while until the queued actions will all have been processed, delays can still be experienced for some time.
We'll monitor the situation at least for the next hour.
Sep 21, 13:36 CEST
As it will take a while until the queued actions will all have been processed, delays can still be experienced for some time.
We'll monitor the situation at least for the next hour.
Sep 21, 13:36 CEST
Update -
A fix is being implemented
Sep 21, 12:09 CEST
Sep 21, 12:09 CEST
Update -
We found the issue the messaging service is facing and are working on it
Sep 21, 11:14 CEST
Sep 21, 11:14 CEST
Identified -
We pinpointed the issue to a problem with the messaging service, not delivering the triggers to the action service.
Sep 21, 10:37 CEST
Sep 21, 10:37 CEST
Investigating -
We are currently experiencing issues with action sequences not triggering at our NL3 hosting location
We are aware of the problem and are investigating.
Our apologies for the inconvenience. We aim to update this status blog at least every 30 minutes until the issue has been resolved.
Sep 21, 10:18 CEST
We are aware of the problem and are investigating.
Our apologies for the inconvenience. We aim to update this status blog at least every 30 minutes until the issue has been resolved.
Sep 21, 10:18 CEST