Exalate experienced a critical incident on January 23, 2026 affecting Exalate.app, lasting 2h 18m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 23, 2026, 09:59 AM UTC
We have identify an incident with exalate.app that is currently not loading. We are currently investigating the issue and will be providing updates within the hour. This is not affecting the sync of issues but the UI for exalate is currently unavailable.
- monitoring Jan 23, 2026, 10:18 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 23, 2026, 12:18 PM UTC
This incident has been resolved.
- postmortem Mar 31, 2026, 09:43 AM UTC
**Incident:** Exalate Application Unavailability — January 23, 2026 **Duration:** 10:59 CET – 11:18 CET \(approximately 19 minutes\) **Impact:** The Exalate UI was inaccessible during this window. Issue synchronisation was not affected — integrations continued to run normally throughout. No data was lost. **Summary:** On January 23, 2026, our monitoring detected a service outage affecting the Exalate application. The root cause was a deployment configuration change that unintentionally removed an active compute resource from the production environment. **Timeline:** * 10:59 CET — Issue detected, investigation initiated * 11:18 CET — Fix deployed, service restored * 13:18 CET — Full stability confirmed **Root Cause:** A deployment configuration change targeted the wrong resource section, resulting in an active production compute resource being removed and the application becoming inaccessible. **Resolution:** The affected resource was recreated and all services returned to full operation with no data loss. **Preventive Measures:** * Infrastructure-as-code changes must be validated in a non-production environment before production deployment * Peer review steps introduced to verify configuration targets prior to execution