Exalate incident
Some Exalate nodes down (specially on Jira Cloud)
Exalate experienced a major incident on October 4, 2025 affecting Synchronisation node, lasting 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 04, 2025, 06:18 AM UTC
We are investigating reports of users unable to access the Exalate console on some systems. We will be providing an update soon.
- monitoring Oct 04, 2025, 06:30 AM UTC
The problem has been identified and the fix has been put in place.
- resolved Oct 04, 2025, 06:54 AM UTC
The issue is fully resolved and all nodes are operational. A post-mortem will be provided here in due course.
- postmortem Nov 14, 2025, 12:23 PM UTC
## **Summary** On October 4, 2025, Exalate Cloud experienced an issue that caused some Exalate nodes to become temporarily inaccessible at 04:00 CEST. This resulted in UI access issues and potential synchronization interruptions for part of our customer base. All services were fully restored by 09:00 CEST. ## **Impact** Customers using Exalate cloud nodes experienced: * Inability to access nodes * Sync failures or delays * Temporary disruption of workflow automations No data loss occurred. ## **Root Cause** There was an error in the certification renewal process. This prevented affected nodes from completing required secure connections, making them temporarily unreachable. ## **Resolution** After identifying the cause, the certificate was renewed and deployed. Services began recovering immediately and full functionality was validated shortly thereafter. ## **Preventive Measures** We are implementing several improvements to prevent recurrence, including: * Expanded automated monitoring for certificate validity * Additional service health checks, including customer-facing endpoints * Automated renewal processes for critical certificates * Strengthened operational procedures around certificate lifecycle management