Performance degradation on the DE cluster on 7 Oct 2026 21:08:11 (UTC+02:00)
Completed
Oct 7, 2026, 21:06 CEST (UTC+2)
The incident affecting the DE cluster has been resolved. All systems are back within normal operating range, and the DE cluster is performing as expected. The issue was caused by a problem with our Redis cache.
We apologize for any inconvenience this may have caused.
Oct 7, 2026, 21:06 CEST (UTC+2)
The incident affecting the DE cluster has been resolved. All systems are back within normal operating range, and the DE cluster is performing as expected. The issue was caused by a problem with our Redis cache.
We apologize for any inconvenience this may have caused.
Performance degradation on the DE cluster on 6 Oct 2026 12:40:56 (UTC+02:00)
Resolved
Oct 6, 2026, 12:40 CEST (UTC+2)
The issue affecting the DE cluster has been resolved, and systems are now operating largely normally. We are continuing to closely monitor the situation to ensure stable performance.
We will provide a final update once we have confirmed that the service is fully stable.
Oct 6, 2026, 12:40 CEST (UTC+2)
The issue affecting the DE cluster has been resolved, and systems are now operating largely normally. We are continuing to closely monitor the situation to ensure stable performance.
We will provide a final update once we have confirmed that the service is fully stable.
Performance degradation on the DE cluster on 6 Oct 2026 12:13:53 (UTC+02:00)
Investigating
Oct 6, 2026, 12:13 CEST (UTC+2)
We have identified the cause of the performance issues on the DE cluster as a problem with our Redis cache. Affected users may continue to experience slow load times, request timeouts, or difficulties logging in to DOC.
Our team is working on resolving the Redis issue and restoring normal performance. We will provide a further update as soon as we have more information.
Oct 6, 2026, 12:13 CEST (UTC+2)
We have identified the cause of the performance issues on the DE cluster as a problem with our Redis cache. Affected users may continue to experience slow load times, request timeouts, or difficulties logging in to DOC.
Our team is working on resolving the Redis issue and restoring normal performance. We will provide a further update as soon as we have more information.
Performance degradation on the DE cluster on 6 Oct 2026 10:41:52 (UTC+02:00)
Investigating
Oct 6, 2026, 10:41 CEST (UTC+2)
We are currently investigating performance issues affecting the DE cluster. Affected users may experience slow load times, request timeouts, or difficulties logging in to DOC.
Our team is actively analyzing the root cause and is taking mitigation measures to restore normal performance as quickly as possible. We will provide an update as soon as we have more information.
Oct 6, 2026, 10:41 CEST (UTC+2)
We are currently investigating performance issues affecting the DE cluster. Affected users may experience slow load times, request timeouts, or difficulties logging in to DOC.
Our team is actively analyzing the root cause and is taking mitigation measures to restore normal performance as quickly as possible. We will provide an update as soon as we have more information.
SSO login issue on 12 Feb 2026 14:17:13 (UTC+02:00)
Monitoring
13:15 CET - The backend services that were part of the error have been restarted. SSO login is possible again. We are monitoring the situation.
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
13:15 CET - The backend services that were part of the error have been restarted. SSO login is possible again. We are monitoring the situation.
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
SSO login issue on 12 Feb 2026 14:17:09 (UTC+02:00)
Completed
13:15 CET - The backend services that were part of the error have been restarted. SSO login is possible again. We are monitoring the situation.
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
13:15 CET - The backend services that were part of the error have been restarted. SSO login is possible again. We are monitoring the situation.
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
SSO login issue on 12 Feb 2026 14:04:57 (UTC+02:00)
In progress
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
SSO login issue on 12 Feb 2026 14:04:53 (UTC+02:00)
Investigating
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
13:01 CET - A backend component has been identified as the cause of sporadic SSO malfunction.
we work to restart the related services
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
SSO login issue on 12 Feb 2026 13:49:55 (UTC+02:00)
Investigating
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
SSO login issue on 12 Feb 2026 13:48:24 (UTC+02:00)
Investigating
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
12:47 CET - Currently we are facing issues loging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
DriveLock 2025.2 Patch 1 is online! on 12 Feb 2026 13:47:56 (UTC+02:00)
Investigating
12:47 CET - Currently we are facing issues logging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
12:47 CET - Currently we are facing issues logging in via SSO
If you want to find out more about our latest release: https://t1p.de/ReleaseNotes
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
Routine Infrastructure Update on 6 Feb 2026 12:04:15 (UTC+02:00)
Update on 6 Feb 2026 14:14:52 (UTC+02:00)
✅Routine backend maintenance finished successfully.
Thank you very much for your patience.
Kind regards,
DriveLock Cloud Operations Team
✅Routine backend maintenance finished successfully.
Thank you very much for your patience.
Kind regards,
DriveLock Cloud Operations Team
In progress on 6 Feb 2026 12:04:15 (UTC+02:00)
We are currently performing routine backend maintenance to ensure optimal performance.
This work is unrelated to any DriveLock services and does not affect our security offerings.
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
We are currently performing routine backend maintenance to ensure optimal performance.
This work is unrelated to any DriveLock services and does not affect our security offerings.
If you need assistance, please contact cloud.opsmgmt@drivelock.com.
Kind regards,
DriveLock Cloud Operations Team
✅ Maintenance completed on 6 Feb 2026 11:55:56 (UTC+02:00)
✅ US: maintenance completed
✅ APAC: maintenance completed
✅ DE: maintenance completed
Latest release notes: https://t1p.de/ReleaseNotes
📢 Important note: If you encounter problems using the temporary unlock feature, please check the permissions.
In addition to the temp unlock permission, the "Show Tenant Settings" permission is required with the update to 25.2.
Users may experience temporary downtime during maintenance.
If you encounter any issues with the agent communication to the DES or have questions, please don't hesitate to contact our support team.
- Email: cloud.opsmgmt@drivelock.com
We're here to assist you promptly.
Thank you for choosing our services.
Kind regards,
DriveLock Cloud Operations Team
✅ APAC: maintenance completed
✅ DE: maintenance completed
Latest release notes: https://t1p.de/ReleaseNotes
📢 Important note: If you encounter problems using the temporary unlock feature, please check the permissions.
In addition to the temp unlock permission, the "Show Tenant Settings" permission is required with the update to 25.2.
Users may experience temporary downtime during maintenance.
If you encounter any issues with the agent communication to the DES or have questions, please don't hesitate to contact our support team.
- Email: cloud.opsmgmt@drivelock.com
We're here to assist you promptly.
Thank you for choosing our services.
Kind regards,
DriveLock Cloud Operations Team