Exalate Outage History

The issue has been identified and a fix is being implemented.

Following up on an unadverted change in the application name which causes the proxy user to be shown with the full name of the application instead of just "Exalate". This is already notified to Atlassian and we are awaiting the required action on their end to revert the change. Impact: Updates made by Exalate will display "Exalate Classic Connector for Jira (Two-way Sync)" as the user making the change.

We continue to investigate the best approach to solve this issue with the help of Atlassian support.

We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible.

We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible. We will be providing the next update within 6 hours or as soon as we have any relevant information.

We will be actioning a change on Exalate Cloud to improve stability. The impact on your node will be that limited to a restart with the node being unavailable for a couple of min. The inconvenience is regretted.

The rolling restart of the nodes is in progress. You will experience a brief restart on JCloud nodes. We will keep you posted with our progress.

The restart is still in progress and is going without any issues. We will update you as soon as it is completed.

Our cloud team has identified the root cause and is actively engaged in rectifying it.

affected nodes are recovering while our cloud team continues to work on the issue.

The issue was identified and we are currently working on restoring the nodes as soon as possible. Next update within 2 hours or as soon as we have any relevant updates

We continue with the restoration efforts. Some nodes are already available. Next update will be within 2 hours or as soon as we have any relevant update.

We have identified an issue when trying to access the SyncRoom page, caused by a significant increase in DNS traffic originating from an external problem between Hostinger and Cloudflare. This external issue is currently impacting our service and is preventing the SyncRoom page and the community from loading Important Note: This issue does not affect the core Exalate functionality. Synchronization is continuing to work as expected. We are actively working to resolve this and will provide an update within the next two hours. Thank you for your patience.

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.

We are continuing to work on a fix for this issue.

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.

Integration services to Salesforce are affected by a major service interruption on the Salesforce side Check here - https://status.salesforce.com/products/Salesforce_Services We are monitoring the situation and will be handling it as new information from Salesforce is provided.

We are currently experiencing an incident affecting a limited number of nodes in our system. Current situation: We've identified the root cause and a mitigation has started, some nodes are back online.

We are continuing to work on resolving the outage. Currently, 80% of the affected nodes have been restored and are fully operational.