Resolved after 10 hours 20 minutes, affecting Synchronisation node, on July 24, 2026.
The proxy user name was reverted back to Exalate. We are considering the incident as resolved.
Affected components
Update timeline
- identified Jul 24, 2026, 06:12 AM UTC
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.
- identified Jul 24, 2026, 09:15 AM UTC
We continue to investigate the best approach to solve this issue with the help of Atlassian support.
- identified Jul 24, 2026, 12:39 PM UTC
We are actively working with Atlassian support to determine the best resolution for this issue as soon as possible.
- identified Jul 24, 2026, 03:47 PM UTC
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.
- resolved Jul 24, 2026, 04:33 PM UTC
The proxy user name was reverted back to Exalate. We are considering the incident as resolved.
Your product runs on more than Exalate
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services