Elastic Cloud incident

AutoOps Outage in GCP us-central-1

Major Resolved View vendor source →

Elastic Cloud experienced a major incident on December 24, 2025 affecting AutoOps, lasting 18h 39m. The incident has been resolved; the full update timeline is below.

Started
Dec 24, 2025, 08:37 AM UTC
Resolved
Dec 25, 2025, 03:17 AM UTC
Duration
18h 39m
Detected by Pingoru
Dec 24, 2025, 08:37 AM UTC

Affected components

AutoOps

Update timeline

  1. investigating Dec 24, 2025, 08:37 AM UTC

    We are currently investigating an outage of AutoOps in GCP us-central-1. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

  2. investigating Dec 24, 2025, 09:37 AM UTC

    We are currently investigating an outage of AutoOps in GCP us-central-1. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

  3. identified Dec 24, 2025, 11:01 AM UTC

    We have implemented mitigations to restore AutoOps functionality in GCP us-central-1. Customer deployments in the region may still be marked as inactive and recent metrics may not be available. We are monitoring its recovery and will provide an update within an hour.

  4. identified Dec 24, 2025, 12:05 PM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available.

  5. identified Dec 24, 2025, 01:03 PM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available.

  6. identified Dec 24, 2025, 02:06 PM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available.

  7. identified Dec 24, 2025, 03:16 PM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available.

  8. monitoring Dec 24, 2025, 04:22 PM UTC

    AutoOps functionality has been restored in the GCP us-central-1 region. We are continuing to monitor the system for signs of service degradation.

  9. identified Dec 24, 2025, 05:20 PM UTC

    We are continuing to see intermittent impact in the GCP us-central-1 region, which is causing some customer deployments to be marked as inactive. We are continuing to investigate the issue and will continue to provide updates as they become available.

  10. identified Dec 24, 2025, 07:07 PM UTC

    We are continuing to investigate an issue impacting AutoOps deployments in the GCP us-central-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will continue to provide updates as they become available.

  11. identified Dec 24, 2025, 09:05 PM UTC

    We are continuing to investigate an issue impacting AutoOps deployments in the GCP us-central-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will continue to provide updates as they become available.

  12. identified Dec 24, 2025, 10:27 PM UTC

    We are continuing to see intermittent impact in the GCP us-central-1 region, which is causing some customer deployments to be marked as inactive. We are continuing to investigate the issue and will continue to provide updates as they become available.

  13. identified Dec 24, 2025, 11:26 PM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available until it is fully recovered.

  14. identified Dec 25, 2025, 12:35 AM UTC

    AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still be marked as inactive, and recent metrics may not be available until it is fully recovered.

  15. monitoring Dec 25, 2025, 02:19 AM UTC

    AutoOps functionality has been restored in the GCP us-central-1 region. We are continuing to monitor the system for signs of service degradation.

  16. resolved Dec 25, 2025, 03:17 AM UTC

    The system is operational.