Exalate incident

Database instability

Major Resolved View vendor source →

Exalate experienced a major incident on November 22, 2023 affecting Exalate Console and Exalate for Azure DevOps and 1 more component, lasting 6d. The incident has been resolved; the full update timeline is below.

Started
Nov 22, 2023, 03:38 PM UTC
Resolved
Nov 28, 2023, 04:37 PM UTC
Duration
6d
Detected by Pingoru
Nov 22, 2023, 03:38 PM UTC

Affected components

Exalate ConsoleExalate for Azure DevOpsExalate for ServiceNow in Exalate CloudExalate for GitHubExalate for SalesForceconnect.exalate.cloud

Update timeline

  1. identified Nov 22, 2023, 03:38 PM UTC

    Current Status: Partial Service Disruption Issue Description: -Database services on Exalate cloud got into resourcing constraints as a spike in usage resulted in instabilities leading to a partial service disruption. Actions Taken: -Our team is actively investigating the root cause of the issue. -Immediate steps are being taken to mitigate the impact on possible affected nodes. Ongoing Mitigation: -We are working to extend the resources of the Exalate Cloud to alleviate the usage constraint. -Continuous monitoring is in place to ensure the stability of the affected nodes. We understand the inconvenience this may cause and appreciate your patience as we work to resolve the issue promptly. Further updates will be provided as we make progress towards a complete resolution. Thank you for your understanding

  2. monitoring Nov 23, 2023, 09:09 AM UTC

    A strategy has been formulated to address the repercussions of the database instability. Validation of this approach will be conducted throughout the morning, with node recovery scheduled for later today.

  3. monitoring Nov 24, 2023, 09:19 AM UTC

    The fix has been applied and our Engineering and Cloud teams are monitoring the results. There are still a number of nodes where additional actions need to be taken from our side. We will keep you updated on any new developments.

  4. resolved Nov 28, 2023, 04:37 PM UTC

    This incident has been resolved.

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

    timeout