Exalate experienced a major incident on June 23, 2026 affecting Exalate.app, lasting 3h 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 23, 2026, 09:10 AM UTC
We are currently investigating an issue when trying to load the connection from the exalate.app page gets an error. The connection and syncs are not affected by the outage, they are still working, but at the moment is not possible to see or modify connection from the exalate.app page. We will be providing an update within 2 hours.
- monitoring Jun 23, 2026, 09:26 AM UTC
The issue has been resolved. Exalate Dashboard is not back online and stable. We will continue monitoring the system.
- resolved Jun 23, 2026, 12:47 PM UTC
This incident has been resolved.
- postmortem Jul 07, 2026, 08:49 AM UTC
**Duration:** 11:10 CEST - 11:26 CEST \(approximately 16 minutes\). Full stability confirmed at 14:47 CEST. **Impact:** The Exalate.app connection and dashboard pages were inaccessible during this window. Issue synchronisation was not affected - integrations continued to run normally throughout. No data was lost. **Summary:** On June 23, 2026, the Exalate.app interface became inaccessible after an internal authentication component failed to connect to its database. The failure was caused by a credential mismatch introduced during a production deployment. **Timeline:** * 11:10 CEST - Issue detected, investigation initiated * 11:26 CEST - Fix deployed, service restored * 14:47 CEST - Full stability confirmed **Root Cause:** During a production deployment on June 19, a database credential was configured independently in two systems. A subtle mismatch was introduced during a subsequent configuration update. The mismatch remained latent because the application maintained existing database connections. A routine GKE maintenance event on June 23 recycled the application, forcing new connections that exposed the mismatch. **Resolution:** The database credential was aligned and the application was restarted. Service returned to full operation with no data loss. **Preventive Measures:** * Post-deployment authentication verification checks have been added to the deployment runbook * Alerting for application database connectivity failures has been implemented * The credential configuration process is being consolidated to eliminate the dual-system mismatch risk We apologize for the disruption. We remain committed to the reliability of the Exalate platform.