Exalate experienced a major incident on April 8, 2025 affecting Exalate Console and Synchronisation node and 1 more component, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 08, 2025, 12:58 PM UTC
We are currently tracking an issue where cloud nodes are getting errors communication with the destination side and blocking the synchronization. Resolving the errors will make the synchronization work again but another error could reappear.
- investigating Apr 08, 2025, 01:43 PM UTC
As part of our continued investigation into the recent service disruption, a number of nodes have been identified as temporarily unreachable. Our engineering teams are prioritizing node recovery and service restoration.
- identified Apr 08, 2025, 03:29 PM UTC
We have successfully identified the root cause of the recent node downtime and communication disruptions. A mitigation is now being deployed, and we will maintain continuous monitoring of the system.
- identified Apr 08, 2025, 03:36 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 08, 2025, 07:03 PM UTC
We've successfully restored 90% of the nodes, and they're now fully operational. We're actively working on the remaining systems and closely monitoring performance.
- monitoring Apr 09, 2025, 07:42 AM UTC
All Cloud nodes are working as expected. We will continue to monitor the situation.
- resolved Apr 09, 2025, 03:32 PM UTC
All affected services are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.
- postmortem Apr 01, 2026, 04:10 AM UTC
timeout