Exalate incident

JiraCloud nodes experiencing some instablility

Minor Resolved View vendor source →

Exalate experienced a minor incident on July 16, 2026 affecting Synchronisation node, lasting 5h 50m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 11:28 AM UTC
Resolved
Jul 16, 2026, 05:18 PM UTC
Duration
5h 50m
Detected by Pingoru
Jul 16, 2026, 11:28 AM UTC

Affected components

Synchronisation node

Update timeline

  1. investigating Jul 16, 2026, 11:28 AM UTC

    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.

  2. identified Jul 16, 2026, 12:03 PM UTC

    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.

  3. identified Jul 16, 2026, 01:38 PM UTC

    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.

  4. identified Jul 16, 2026, 03:15 PM UTC

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

  5. monitoring Jul 16, 2026, 03:57 PM UTC

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

  6. resolved Jul 16, 2026, 05:18 PM UTC

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