Exalate experienced a major incident on April 15, 2026 affecting Exalate.app, lasting 3h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 15, 2026, 09:03 AM UTC
We are currently investigating an issue where the workspaces page is not loading. The sync is not affected, only the UI of New Exalate is not loading.
- identified Apr 15, 2026, 09:04 AM UTC
We have identified the root cause of the issue and are currently working on a fix.
- monitoring Apr 15, 2026, 10:16 AM UTC
The technical issues have been fully resolved and the app is up and running now. We are closely monitoring the situation.
- resolved Apr 15, 2026, 12:16 PM UTC
The application has been running smoothly without any issues and we do not see any anomalies. A post-mortem will be provided in due course.
- postmortem Jul 07, 2026, 12:41 PM UTC
**Incident:** Exalate.app Not Loading Workspaces - April 15, 2026 **Duration:** 11:03 CEST – 12:16 CEST \(approximately 73 minutes\). **Impact:** The Exalate.app UI was inaccessible during this window. Issue synchronisation was not affected. No data was lost. **Summary:** On April 15, 2026, the Exalate.app interface became inaccessible following a planned infrastructure credential update. A secondary configuration dependency was not updated as part of the change, preventing the application from connecting to its database. **Timeline:** * 11:03 CEST - Issue detected, investigation initiated * 11:04 CEST - Root cause identified * 12:16 CEST - Fix deployed, service restored **Root Cause:** A configuration dependency missed during a credential update left the application unable to authenticate to its database. This was related to the April 6 incident; the additional dependency has now been identified and incorporated into the rotation procedure. **Resolution:** The affected configuration was regenerated and the application was restarted. Service returned to full operation with no data loss. **Preventive Measures:** * All credential dependencies have been fully mapped and the rotation procedure updated to cover them as a single atomic operation We apologize for the disruption. We remain committed to the reliability of the Exalate platform.