Exalate incident

Some nodes are down due to cluster issue

Major Resolved View vendor source →

Exalate experienced a major incident on February 19, 2025 affecting Exalate Console and Synchronisation node and 1 more component, lasting 1d 20h. The incident has been resolved; the full update timeline is below.

Started
Feb 19, 2025, 06:07 PM UTC
Resolved
Feb 21, 2025, 02:59 PM UTC
Duration
1d 20h
Detected by Pingoru
Feb 19, 2025, 06:07 PM UTC

Affected components

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

Update timeline

  1. investigating Feb 19, 2025, 06:07 PM UTC

    We're currently experiencing an outage impacting some nodes due to an issue on a cluster. Our team is actively investigating and working to restore service as quickly as possible. We apologize for any inconvenience and appreciate your patience.

  2. identified Feb 19, 2025, 06:23 PM UTC

    We have identified and we currently working on restoring the nodes.

  3. monitoring Feb 19, 2025, 07:32 PM UTC

    All nodes are back online, we will keep monitoring and will be providing further updates.

  4. monitoring Feb 19, 2025, 07:32 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Feb 20, 2025, 08:16 AM UTC

    Some nodes are currently down due. We are currently investigating and working to restore the service as soon as possible.

  6. monitoring Feb 20, 2025, 11:11 AM UTC

    incident has been mitigated, we are currently monitoring.

  7. monitoring Feb 20, 2025, 01:29 PM UTC

    Some nodes are currently down due. We are currently investigating and working to restore the service as soon as possible.

  8. monitoring Feb 20, 2025, 02:35 PM UTC

    incident has been mitigated, we are currently monitoring.

  9. resolved Feb 21, 2025, 02:59 PM UTC

    This incident has been resolved. We will be providing an RCA next week.

  10. postmortem Apr 01, 2026, 04:11 AM UTC

    timeout