Elastic Cloud Outage History

Elastic Cloud major outage · 1 active incident View live status →

Elastic Cloud had 66 outages in the last 2 years totaling 335h 14m of downtime — averaging 2.7 incidents per month.

There were 66 Elastic Cloud outages since July 27, 2025 totaling 335h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.elastic.co

Major June 17, 2026

Issues with creating/updating Deployments in several regions

Detected by Pingoru
Jun 17, 2026, 03:52 PM UTC
Resolved
Jun 17, 2026, 05:35 PM UTC
Duration
1h 42m
Affected: Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west4Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-2Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-1Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-2Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-central-1Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southafricanorth
Timeline · 3 updates
  1. identified Jun 17, 2026, 03:52 PM UTC

    We are currently investigating an issue when creating/updating Deployments in several regions. We've identified the issue and working on applying a fix. We will provide an update when one is available or within the hour, whichever comes first.

  2. monitoring Jun 17, 2026, 04:53 PM UTC

    We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.

  3. resolved Jun 17, 2026, 05:35 PM UTC

    This issue has been resolved.

Read the full incident report →

Major June 16, 2026

Ingestion issues for Managed OTLP and Managed Intake Service endpoints in the Azure Australia East region

Detected by Pingoru
Jun 16, 2026, 10:54 PM UTC
Resolved
Jun 17, 2026, 12:59 AM UTC
Duration
2h 4m
Affected: Managed Intake Service Availability
Timeline · 3 updates
  1. identified Jun 16, 2026, 10:54 PM UTC

    We are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.

  2. identified Jun 17, 2026, 12:02 AM UTC

    This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.

  3. resolved Jun 17, 2026, 12:59 AM UTC

    This issue is resolved.

Read the full incident report →

Major June 16, 2026

Failure to authenticate to Kibana with SSO

Detected by Pingoru
Jun 16, 2026, 10:57 AM UTC
Resolved
Jun 16, 2026, 11:16 AM UTC
Duration
18m
Affected: Elastic Cloud Hosted
Timeline · 1 update
  1. identified Jun 16, 2026, 10:57 AM UTC

    We have detected an issue with the Kibana authentication flow. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution. We will post an update in 30 minutes, or sooner if there is a change in status.

Read the full incident report →

Major June 16, 2026

Issue with Kibana authentication flow

Detected by Pingoru
Jun 16, 2026, 10:57 AM UTC
Resolved
Jun 16, 2026, 11:36 AM UTC
Duration
38m
Affected: Cloud console
Timeline · 3 updates
  1. investigating Jun 16, 2026, 10:57 AM UTC

    We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution. Our team is currently identifying the root cause to resolve the issue. We will share another update in the next hour.

  2. investigating Jun 16, 2026, 11:21 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 16, 2026, 11:36 AM UTC

    We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.

Read the full incident report →

Major June 15, 2026

Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1

Detected by Pingoru
Jun 15, 2026, 05:31 PM UTC
Resolved
Jun 15, 2026, 07:13 PM UTC
Duration
1h 42m
Affected: Elastic Cloud Serverless
Timeline · 3 updates
  1. investigating Jun 15, 2026, 05:31 PM UTC

    We are currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1. We will continue to update status as we learn more.

  2. monitoring Jun 15, 2026, 06:00 PM UTC

    This issue has been mitigated, and we are continuing to monitor the situation.

  3. resolved Jun 15, 2026, 07:13 PM UTC

    This issue has been resolved.

Read the full incident report →

Major June 4, 2026

Customers may see delays with creating Azure serverless projects

Detected by Pingoru
Jun 04, 2026, 01:51 AM UTC
Resolved
Jun 04, 2026, 09:20 AM UTC
Duration
7h 28m
Timeline · 4 updates
  1. investigating Jun 04, 2026, 01:51 AM UTC

    Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are currently investigating the issue.

  2. monitoring Jun 04, 2026, 03:44 AM UTC

    Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. Recovery has started and we will provide further updates as we progress.

  3. monitoring Jun 04, 2026, 06:21 AM UTC

    Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are seeing increased recovery across as we monitor the situation. Services are being restored. Monitoring is continuing, and we will provide further updates as we progress.

  4. resolved Jun 04, 2026, 09:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Missing Metrics in Cloud Console - Azure North Europe

Detected by Pingoru
Jun 02, 2026, 01:25 PM UTC
Resolved
Jun 02, 2026, 07:50 PM UTC
Duration
6h 25m
Affected: Cloud console
Timeline · 3 updates
  1. investigating Jun 02, 2026, 01:25 PM UTC

    Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour

  2. investigating Jun 02, 2026, 03:02 PM UTC

    We are seeing some signs of recovery, and have taken action to mitigate the impact and speed up recovery. Some users will still see seeing missing metrics visualizations in the Cloud console, for deployments in the Azure North Europe region. We are actively investigating and will provide another update within 1 hour

  3. resolved Jun 02, 2026, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 29, 2026

Issue creating new projects in AWS ap-southeast-2

Detected by Pingoru
May 29, 2026, 06:00 PM UTC
Resolved
May 29, 2026, 06:36 PM UTC
Duration
35m
Timeline · 2 updates
  1. investigating May 29, 2026, 06:00 PM UTC

    We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.

  2. resolved May 29, 2026, 06:36 PM UTC

    This issue has been resolved.

Read the full incident report →

Major May 29, 2026

Upstream Azure Outage Causing Service Degradation

Detected by Pingoru
May 29, 2026, 06:32 AM UTC
Resolved
May 31, 2026, 09:33 PM UTC
Duration
2d 15h
Affected: Elasticsearch connectivity: Azure azure-westus2Azure Infrastructure HealthKibana connectivity: Azure azure-westus2Azure Infrastructure health: azure-westus2APM connectivity: Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2
Timeline · 9 updates

Read the full incident report →

Major May 26, 2026

Missing Metrics in Cloud Console - Azure Southeast Asia

Detected by Pingoru
May 26, 2026, 09:35 PM UTC
Resolved
May 26, 2026, 09:35 PM UTC
Duration
Timeline · 1 update
  1. resolved May 26, 2026, 09:35 PM UTC

    Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We have already stabilized the situation.

Read the full incident report →

Major May 22, 2026

Delayed Execution For Synthetic Monitors in Europe Germany

Detected by Pingoru
May 22, 2026, 04:54 AM UTC
Resolved
May 22, 2026, 04:54 AM UTC
Duration
Timeline · 1 update
  1. resolved May 22, 2026, 04:54 AM UTC

    Synthetics browser monitors running in Europe-Germany region (GCP europe-west3) for some of the users were experiencing delayed executions results and some of them being stopped. The issue affected both Elastic Cloud Hosted and Elastic Cloud Serverless in that region and other regions were not impacted.

Read the full incident report →

Notice May 20, 2026

AutoOps Login Issues for New Customers

Detected by Pingoru
May 20, 2026, 03:29 PM UTC
Resolved
May 27, 2026, 01:06 PM UTC
Duration
6d 21h
Affected: AutoOps
Timeline · 4 updates
  1. investigating May 20, 2026, 03:29 PM UTC

    We are investigating an issue that prevents new Elastic Cloud customers, including trial users, from accessing AutoOps across all regions. Impact: New customers and trial accounts are currently unable to access the AutoOps dashboard. Existing Customers: Service is unaffected. AutoOps continues to function normally for all existing deployments. Our team is actively working to identify the root cause. We will provide our next update within the next hour or as soon as more information becomes available.

  2. monitoring May 20, 2026, 03:48 PM UTC

    We have mitigated the issue preventing new Elastic Cloud customers and trial users from accessing AutoOps by restarting a backend service. We are actively monitoring to confirm the fix remains stable and that all new user logins are functioning as expected. We will provide a final update once we have confirmed full resolution.

  3. monitoring May 22, 2026, 04:19 PM UTC

    We continue to actively monitor the implemented mitigation actions. All new user logins are functioning as expected. A permanent resolution is scheduled to be implemented early next week. Our next update will be once the resolution actions are complete, or sooner if the situation changes.

  4. resolved May 27, 2026, 01:06 PM UTC

    The permanent resolution has been implemented, thus concluding our resolution actions. This incident is resolved.

Read the full incident report →

Major May 11, 2026

Temporarily unavailability of Serverless Projects Functionality

Detected by Pingoru
May 11, 2026, 08:00 AM UTC
Resolved
May 11, 2026, 11:11 AM UTC
Duration
3h 11m
Affected: Elasticsearch Availability
Timeline · 2 updates
  1. monitoring May 11, 2026, 10:07 AM UTC

    We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable. The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.

  2. resolved May 11, 2026, 11:11 AM UTC

    We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.

Read the full incident report →

Major May 8, 2026

Issues with Email Alerts

Detected by Pingoru
May 08, 2026, 06:10 PM UTC
Resolved
May 09, 2026, 01:01 AM UTC
Duration
6h 50m
Timeline · 3 updates
  1. investigating May 08, 2026, 06:10 PM UTC

    We are currently investigating reports that some customers may be facing issues with email alerts.

  2. monitoring May 08, 2026, 11:11 PM UTC

    A solution has been implemented, and email delivery has resumed. We are continuing to track the situation closely and will provide another update once considered resolved.

  3. resolved May 09, 2026, 01:01 AM UTC

    This issue is now resolved. Email delivery has been successful with no monitored issues.

Read the full incident report →

Major April 30, 2026

Delayed AutoOps Metrics in AWS us-east-1

Detected by Pingoru
Apr 30, 2026, 09:46 PM UTC
Resolved
Apr 30, 2026, 10:36 PM UTC
Duration
50m
Affected: AutoOps
Timeline · 3 updates
  1. identified Apr 30, 2026, 09:46 PM UTC

    We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.

  2. monitoring Apr 30, 2026, 10:18 PM UTC

    This issue has now been resolved and we are continuing to monitor the system.

  3. resolved Apr 30, 2026, 10:36 PM UTC

    This issue has now been resolved.

Read the full incident report →

Major April 28, 2026

Missing Metrics in Cloud Console — US East (us-east-1)

Detected by Pingoru
Apr 28, 2026, 02:46 PM UTC
Resolved
Apr 28, 2026, 06:40 PM UTC
Duration
3h 53m
Timeline · 5 updates
  1. investigating Apr 28, 2026, 02:46 PM UTC

    Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the us-east-1 (US East) region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 30 minutes.

  2. investigating Apr 28, 2026, 03:57 PM UTC

    Our investigation is ongoing. Some early signs of stabilisation have been observed, but metrics visualizations in the Cloud console remain impacted. We will provide a further update within 30 minutes.

  3. investigating Apr 28, 2026, 04:32 PM UTC

    Our investigation is ongoing. We continue to see early signs of stabilization, but metrics visualizations in the Cloud console remain impacted. We will provide a further update in 1 hour, or when there is a change in status.

  4. identified Apr 28, 2026, 05:39 PM UTC

    We are continuing to see signs of stabilization and monitoring as the system recovers, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.

  5. resolved Apr 28, 2026, 06:40 PM UTC

    The system has recovered and functionality has returned to normal.

Read the full incident report →

Major April 27, 2026

Elevated Error Rates and Latency — EU West Region

Detected by Pingoru
Apr 27, 2026, 11:49 AM UTC
Resolved
Apr 27, 2026, 12:40 PM UTC
Duration
51m
Affected: Elasticsearch connectivity: AWS eu-west-3Kibana connectivity: AWS eu-west-3APM connectivity: AWS eu-west-3
Timeline · 4 updates
  1. identified Apr 27, 2026, 11:49 AM UTC

    We are currently investigating connectivity issues affecting a subset of customers in our EU West (Paris) region. Some requests may be experiencing elevated latency or failures. Our team is actively investigating, and we are working with our cloud infrastructure provider on the underlying issue. Other regions are not affected at this time. We will provide updates as the situation develops.

  2. identified Apr 27, 2026, 11:57 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Apr 27, 2026, 12:08 PM UTC

    Our monitoring system reports that AWS EU West 3 (Paris) region ingress layer traffic has recovered to normal levels as of 11:36 UTC and our SLO alerts have resolved. We are continuing to monitor and will update once we are confident the issue is fully resolved.

  4. resolved Apr 27, 2026, 12:40 PM UTC

    The connectivity issues affecting a subset of customers in our AWS EU West (Paris) region have been resolved. Failed probes recovered at 11:36 UTC following remediation of an issue with our underlying cloud infrastructure provider. We are no longer observing any elevated error rates or latency in the region. We apologise for any inconvenience caused and will conduct a post-incident review.

Read the full incident report →

Major April 20, 2026

EIS elevated 5xx error rates for model google-gemini-embedding-001

Detected by Pingoru
Apr 20, 2026, 06:37 AM UTC
Resolved
Apr 20, 2026, 10:41 AM UTC
Duration
4h 4m
Affected: Elastic Inference Service
Timeline · 3 updates
  1. investigating Apr 20, 2026, 06:37 AM UTC

    We're seeing elevated 5xx error rates for the Gemini Embedding v1 model in EIS. The following default inference endpoint is affected: - .google-gemini-embedding-001 We're investigating and will update again in 2 hours or if there's a change in status.

  2. investigating Apr 20, 2026, 09:50 AM UTC

    Errors are coming from the provider API (Google). The incident has been escalated to them, and we are still waiting for a response.

  3. resolved Apr 20, 2026, 10:41 AM UTC

    An incident with an upstream service provider has been resolved, and access to the model is now restored.

Read the full incident report →

Major April 9, 2026

Privatelink hostnames reported by API are incorrect

Detected by Pingoru
Apr 09, 2026, 08:46 PM UTC
Resolved
Apr 10, 2026, 07:54 PM UTC
Duration
23h 7m
Timeline · 4 updates
  1. identified Apr 09, 2026, 08:46 PM UTC

    A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.

  2. identified Apr 09, 2026, 10:44 PM UTC

    We have merged a fix and are working on deploying it to production

  3. identified Apr 10, 2026, 12:18 PM UTC

    We are still working on moving the fix to production as we experienced some testing issues.

  4. resolved Apr 10, 2026, 07:54 PM UTC

    We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience.

Read the full incident report →

Major April 9, 2026

Connection issue to Kibana via the Cloud UI SSO

Detected by Pingoru
Apr 09, 2026, 03:37 PM UTC
Resolved
Apr 10, 2026, 11:51 AM UTC
Duration
20h 14m
Timeline · 5 updates
  1. investigating Apr 09, 2026, 03:37 PM UTC

    We are aware of an issue when connecting to Kibana through the Elastic Cloud UI via SAML SSO, impacting hosted Cloud deployments. Our team is actively investigating. We will post an update to this status within the next hour.

  2. investigating Apr 09, 2026, 04:21 PM UTC

    We have identified that only PrivateLink customers are impacted and no other Hosted Cloud Deployments should see any issues.

  3. investigating Apr 09, 2026, 04:41 PM UTC

    We have identified the issue and are working on a fix. We will update again in 3 hours or earlier.

  4. investigating Apr 09, 2026, 07:50 PM UTC

    We have rolled out the fix and there should be no more customer impact

  5. resolved Apr 10, 2026, 11:51 AM UTC

    We have confirmed no further impact from this incident, and are now marking it as resolved.

Read the full incident report →

Major April 6, 2026

Synthetics service may not run on schedule (us-east-4)

Detected by Pingoru
Apr 06, 2026, 05:58 PM UTC
Resolved
Apr 06, 2026, 08:43 PM UTC
Duration
2h 45m
Timeline · 3 updates
  1. investigating Apr 06, 2026, 05:58 PM UTC

    We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.

  2. identified Apr 06, 2026, 07:16 PM UTC

    We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.

  3. resolved Apr 06, 2026, 08:43 PM UTC

    Issue has been fixed and there should be no more customer impact

Read the full incident report →

Major March 30, 2026

Elevated error rates for Claude Sonnet 4.5 EIS inference endpoints

Detected by Pingoru
Mar 30, 2026, 06:46 PM UTC
Resolved
Mar 30, 2026, 07:57 PM UTC
Duration
1h 10m
Affected: Elastic Inference Service
Timeline · 2 updates
  1. investigating Mar 30, 2026, 06:46 PM UTC

    We're seeing elevated 5xx error rates for the Claude Sonnet 4.5 model in EIS. The following default inference endpoints are affected: - .anthropic-claude-4.5-sonnet-chat_completion - .anthropic-claude-4.5-sonnet-completion - .gp-llm-v2-chat_completion - .gp-llm-v2-completion We're investigating and will update again in 2 hours or if there's a change in status.

  2. resolved Mar 30, 2026, 07:57 PM UTC

    Endpoints are operating normally

Read the full incident report →

Major March 27, 2026

AutoOps deployments marked as Inactive in AWS us-east-1 region

Detected by Pingoru
Mar 27, 2026, 04:33 AM UTC
Resolved
Mar 27, 2026, 07:23 AM UTC
Duration
2h 49m
Affected: AutoOps
Timeline · 4 updates
  1. investigating Mar 27, 2026, 04:33 AM UTC

    We are currently investigating an outage of AutoOps in AWS us-east-1 region. 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. monitoring Mar 27, 2026, 05:37 AM UTC

    We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.

  3. monitoring Mar 27, 2026, 07:13 AM UTC

    We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved.

  4. resolved Mar 27, 2026, 07:23 AM UTC

    AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.

Read the full incident report →

Major March 26, 2026

Issue creating new projects in GCP europe-west3

Detected by Pingoru
Mar 26, 2026, 10:51 AM UTC
Resolved
Mar 26, 2026, 05:42 PM UTC
Duration
6h 51m
Affected: Project Orchestration (Create/Edit/Restart/Delete)Elastic Cloud Serverless
Timeline · 3 updates
  1. identified Mar 26, 2026, 10:51 AM UTC

    We are aware of problems creating new Serverless projects in the GCP europe-west3 region. The engineering team has identified the problem and we are working on mitigating it. We will post the next updated in 2 hours.

  2. identified Mar 26, 2026, 01:06 PM UTC

    The engineering team is validating the fix to restore project creation in the GCP europe-west3 region. We will post another update in 2 hours or sooner if needed

  3. resolved Mar 26, 2026, 05:42 PM UTC

    This issue is resolved. Customers are now able to create new Serverless projects in the GCP europe-west3 region

Read the full incident report →

Minor March 9, 2026

GCP us-central1 hosting problems

Detected by Pingoru
Mar 09, 2026, 11:32 AM UTC
Resolved
Mar 09, 2026, 08:29 PM UTC
Duration
8h 57m
Affected: Deployment orchestration (Create/Edit/Restart/Delete): GCP us-central1Elastic Docker Registry
Timeline · 5 updates
  1. investigating Mar 09, 2026, 11:32 AM UTC

    We have identified an issue impacting the provisioning of kibana resources for new projects. This may delay or fail requests for new projects. We are investigating the root cause, and will post updates shortly.

  2. investigating Mar 09, 2026, 11:46 AM UTC

    Further investigations has indentified additional impact across services hosted in the GCP us-central1 region. We are working internally, and with our hosting providers to determine the root cause.

  3. identified Mar 09, 2026, 12:05 PM UTC

    The issue has been identified, and we are working with our hosting providers to reach a solution. Users may see an impact with the availability of the elastic docker registry (browsing, and pulling images) Users may see an impact with the orchestration of their hosted Serverless projects, leading to slower provisioning and scaling tasks.

  4. monitoring Mar 09, 2026, 01:16 PM UTC

    We have seen an improvement regarding this service disruption. The docker registry is available, and project orchestration has been restored. We will continue to monitor the situation, and ensure a full service recovery.

  5. resolved Mar 09, 2026, 08:29 PM UTC

    This incident has been resolved.

Read the full incident report →