Exalate incident

Synchronisation get stuck due to protocol woes

Major Resolved View vendor source →

Exalate experienced a major incident on April 8, 2022 affecting Exalate Console and Synchronisation node and 1 more component, lasting 13d 5h. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2022, 04:03 PM UTC
Resolved
Apr 21, 2022, 09:54 PM UTC
Duration
13d 5h
Detected by Pingoru
Apr 08, 2022, 04:03 PM UTC

Affected components

Exalate ConsoleSynchronisation nodeExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForce

Update timeline

  1. investigating Apr 08, 2022, 04:03 PM UTC

    Synchronisation queues are building up in case of private/public connection On the public side - many transactions are stuck in 'WAITING_REQUEST_RECEIVED' On the private side - many transactions are stuck in 'NOTIFY_REQUEST_RECEIVED' The impact is that the sync is stuck.

  2. investigating Apr 08, 2022, 04:03 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 21, 2022, 09:53 PM UTC

    The fix is available as a release candidate for Jira On Premise (server and data center)

  4. resolved Apr 21, 2022, 09:54 PM UTC

    This incident has been resolved.

  5. postmortem Apr 01, 2026, 04:16 AM UTC

    timeout