Is Exalate down?

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.

The proxy user name was reverted back to Exalate. We are considering the incident as resolved.

Some Jira Cloud nodes are experiencing instability over the past 30mins. The problem is limited and only affects some customers. We will be providing an update shortly.

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.

All nodes are back to normal operation. We continue to monitor the situation closely.

After close monitoring, the issue is considered as fully resolved. We will be posting a RCA here in due course.

We've received multiple reports of syncs looping after update to the new Jira Cloud forge app. Our initial investigation leads us to believe this is happening due to the change in the Proxy User account. We are actively working on determining the root cause and applying a fix.

We continue to investigate this issue with our engineers to determine the root cause.

The root cause has been identified and we are working on a fix. Please expect another update within an hour.

The fix is currently being validated to find the best approach forward. We will provide another update within the hour.

Unfortunately, the testing of the fix revealed an unexpected issue and we are now fine tuning the fix in order ensure that it incorporates all possible use cases. We will have an update for you in an hour.

The new fix has been created and initial tests are promising. We are deep in QA with the new fix and will provide an update within the hour about the results. The inconvenience is regretted.

We are still testing the fix and results are still good. We are close to finalizing it. Next update will be within the hour.

The fix is ready and we are working on the deployment approach with minimal impact for customers. It will be systematically rolled out to all clients. We will provide an update in the next hour about the deployment.

We have deployed the fix to a few select customers and validated results further. The mass rollout is being planned right now. We will update you within the next hour about progress.

We are still on course for the patch deployment and the release is going through additional QA validation now (required for a full production deployment). We expect to have the next update within an hour.

The QA and testing is taking slightly longer than expected, but we expect to start the deployment within the next hour. We will update you before starting this.

The deployment of the hotfix: Exalate Classic 5.35.4 - Jira Cloud, in underway (https://community.exalate.com/t/jira-cloud-version-5-35-4/8215). The deployment is being closely monitored for any anomalies. We will update you in an hour.

The deployment continues uninterrupted. We will update you in due course as soon as it is fully completed.

The deployment was completed successfully and the issue reported stands fully resolved. A detailed RCA will be published in due course.

**Impact:** Some Classic Exalate for Jira Cloud connections experienced repeated, duplicated synchronisations following an infrastructure migration to Atlassian's Forge platform. On affected connections customers saw: * **Duplicate activity** — the same update, comment, or field change applied to an issue over and over as the sync looped. * **Reopened / resurrected issues** — issues that had been closed being reopened, and other status or field values being overwritten back and forth between the paired issues. * **Distorted dashboards and reports** driven by the volume of duplicate changes. * **Broken automations and workflow validations** — because the integration user's name \(and underlying ID\) changed, customer-side Jira Automation rules and workflow validators that referenced the "Exalate" user by name stopped behaving as configured. * **Stuck or failed syncs**, and in some cases a connection going down, requiring manual retries or recovery. * Increased **manual effort** for teams to unstick syncs and correct affected issues. Not all customers were affected — impact depended on connection configuration. The most exposed were local connections and issues that had previously been created or updated under the original "Exalate" identity and were then touched under the renamed one. **Summary:** As part of moving Classic Exalate for Jira Cloud to Atlassian's Forge platform, the name shown for Exalate's integration user inside Jira changed \(from "Exalate" to a longer variant\). Exalate used that name to recognise its own updates and avoid re-synchronising them. Once the name changed, the app no longer recognised its own writes on affected connections and re-processed them as if they were new external changes — each write triggering another sync, producing loops. The same identity change also broke customer automations and validations that referenced the "Exalate" user by name. **Resolution:** A patch \(5.35.4\) that recognises Exalate's own updates by a stable user identifier rather than the display name was validated on affected customer environments and deployed across the Jira Cloud fleet. Synchronisation returned to normal once deployment completed. Atlassian has since restored and confirmed the integration user's name as "Exalate", and it is now stable — repairing automations that reference it by name. Where loops created duplicate or reopened items, we are working with affected customers to identify and correct the affected issues. **Preventive measures:** Loop-prevention no longer depends on a changeable display name; we are adding an impact-review and notification step around platform-driven changes and app updates, and automated detection of synchronisation loops and database saturation so recovery does not depend on customer reports. We apologise for the disruption and remain committed to the reliability of the Exalate platform.

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.

The issue has been resolved. Exalate Dashboard is not back online and stable. We will continue monitoring the system.

This incident has been resolved.

**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.

We have reports of some Exlate cloud nodes being unavailable. Our team is currently investigating the issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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.

All nodes are operational, our cloud team continues to review the affected cluster and work on its maintenance.

The system has been under close observation and it has been stable. We will provide a post-mortem to the incident in due course.