Exalate incident

Some nodes are down due to DB problem in one cluster

Major Resolved View vendor source →

Exalate experienced a major incident on April 29, 2024 affecting connect.exalate.net (mapper) and connect.exalate.cloud, lasting 7h 2m. The incident has been resolved; the full update timeline is below.

Started
Apr 29, 2024, 07:08 AM UTC
Resolved
Apr 29, 2024, 02:11 PM UTC
Duration
7h 2m
Detected by Pingoru
Apr 29, 2024, 07:08 AM UTC

Affected components

connect.exalate.net (mapper)connect.exalate.cloud

Update timeline

  1. identified Apr 29, 2024, 07:08 AM UTC

    We're currently experiencing an outage impacting some nodes due to a database issue in one 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. monitoring Apr 29, 2024, 08:15 AM UTC

    Update: A fix has been deployed, and affected nodes are now gradually coming back online. We're continuing to monitor closely to ensure full recovery. Thank you for your patience and understanding.

  3. resolved Apr 29, 2024, 02:11 PM UTC

    The incident has been resolved. All nodes are operational.

  4. postmortem Apr 01, 2026, 04:12 AM UTC

    timeout