- Detected by Pingoru
- Aug 20, 2026, 08:22 PM UTC
- Resolved
- Aug 20, 2026, 10:13 PM UTC
- Duration
- 1h 50m
Timeline · 4 updates
-
investigating Aug 20, 2026, 08:22 PM UTC
We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. Our team is actively investigating the root cause. We will provide an update within 30 minutes.
-
investigating Aug 20, 2026, 08:53 PM UTC
We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. We will provide an update within 1 hour.
-
identified Aug 20, 2026, 09:59 PM UTC
We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline. Based on our investigation, customer workloads were not affected.
-
resolved Aug 20, 2026, 10:13 PM UTC
This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 12:48 PM UTC
- Resolved
- Aug 20, 2026, 04:22 PM UTC
- Duration
- 3h 34m
Affected: Elastic Cloud Serverless
Timeline · 3 updates
-
investigating Aug 20, 2026, 12:48 PM UTC
An issue affecting the creation of new Serverless projects in Azure's eastus region has been identified. Our team is actively investigating to determine the root cause. We will provide a follow-up status update within the next hour or as soon as the root cause is established, whichever occurs first.
-
monitoring Aug 20, 2026, 02:05 PM UTC
We have determined that the issue stems from an upstream problem with Azure's storage component. Upon examination, the impact is limited strictly to new project initialization times, resulting in longer creation times for Serverless projects in the Azure eastus region. We will provide a further update once the issue has been resolved.
-
resolved Aug 20, 2026, 04:22 PM UTC
Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 09:22 AM UTC
- Resolved
- Aug 20, 2026, 05:09 PM UTC
- Duration
- 6d 7h
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 08:32 AM UTC
- Resolved
- Aug 17, 2026, 11:40 AM UTC
- Duration
- 4d 3h
Timeline · 4 updates
-
investigating Aug 13, 2026, 08:32 AM UTC
We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating
-
investigating Aug 13, 2026, 02:45 PM UTC
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
-
monitoring Aug 13, 2026, 06:26 PM UTC
Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.
-
resolved Aug 17, 2026, 11:40 AM UTC
The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 03:57 AM UTC
- Resolved
- Aug 13, 2026, 08:40 AM UTC
- Duration
- 4h 42m
Affected: Elastic Cloud Serverless
Timeline · 4 updates
-
investigating Aug 13, 2026, 03:57 AM UTC
We are investigating failures with Serverless project creation.
-
investigating Aug 13, 2026, 05:28 AM UTC
We're currently investigating an issue affecting Serverless project creation and modifications. You may experience delays or failures when creating new projects or updating existing project settings. What's affected: - Creating new Serverless projects - Modifying project settings in the Cloud UI or over the API What's not affected: - Running Serverless projects continue to operate normally - Existing project workloads are unimpacted We'll provide an update within 2 hours, or sooner if the situation changes.
-
monitoring Aug 13, 2026, 06:04 AM UTC
We've identified and resolved the issue affecting Serverless project creation and modifications. Our fix has been deployed, and all services are operating normally. Current status: - Creating and modifying Serverless projects is fully operational - All systems are performing as expected We're continuing to monitor closely for any recurrence.
-
resolved Aug 13, 2026, 08:40 AM UTC
We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 05:41 PM UTC
- Resolved
- Aug 06, 2026, 05:41 PM UTC
- Duration
- —
Affected: Elasticsearch connectivity: GCP asia-south1
Timeline · 1 update
-
resolved Aug 06, 2026, 05:41 PM UTC
On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 10:59 PM UTC
- Resolved
- Aug 12, 2026, 08:59 AM UTC
- Duration
- 6d 10h
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 02:24 PM UTC
- Resolved
- Jul 22, 2026, 11:14 PM UTC
- Duration
- 1d 8h
Timeline · 4 updates
-
investigating Jul 21, 2026, 02:24 PM UTC
We have identified an issue with our metering of Instance Capacity for Hosted Deployments that affects a subset of customers. We currently believe the impact to be limited to a small number of customers but are still working to identify and correct all occurrences of this issue. We will proactively issue billing corrections where necessary.
-
investigating Jul 21, 2026, 11:15 PM UTC
We are still investigating the metering issue impacting a small number of customers. We will proactively issue billing corrections where necessary. We'll provide another update when new information is available.
-
investigating Jul 22, 2026, 10:49 AM UTC
We are still investigating the metering issue impacting a small number of customers. We'll provide a further update when new information is available.
-
resolved Jul 22, 2026, 11:14 PM UTC
All metering errors have been corrected. We will be issuing refunds to the small number of affected customers.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 01:45 PM UTC
- Resolved
- Jul 21, 2026, 02:21 PM UTC
- Duration
- 35m
Affected: AutoOps
Timeline · 2 updates
-
identified Jul 21, 2026, 01:45 PM UTC
RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe. Note this incident has already been resolved, and is being posted retroactively.
-
resolved Jul 21, 2026, 02:21 PM UTC
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 09:36 AM UTC
- Resolved
- Jul 23, 2026, 04:37 PM UTC
- Duration
- 2d 7h
Timeline · 5 updates
-
investigating Jul 21, 2026, 09:36 AM UTC
We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code. Available Workarounds: - Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn). - Authenticate using the "Log in with Google" social login button. Note: API Key access to your projects and deployments remains fully operational. We are actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
-
investigating Jul 21, 2026, 10:56 AM UTC
Update: This incident is still ongoing and we are continuing to investigate. We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code. Available Workarounds: - Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn). - Authenticate using the "Log in with Google" social login button. Note: API Key access to your projects and deployments remains fully operational. We are actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
-
investigating Jul 21, 2026, 02:25 PM UTC
Update: This incident is still ongoing and we are continuing to investigate.
-
monitoring Jul 21, 2026, 11:10 PM UTC
Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
-
resolved Jul 23, 2026, 04:37 PM UTC
Delivery delays have been resolved, MFA email delivery is fully functional for all customers.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 12:15 AM UTC
- Resolved
- Jul 15, 2026, 01:12 AM UTC
- Duration
- 56m
Affected: Cloud console
Timeline · 3 updates
-
investigating Jul 15, 2026, 12:15 AM UTC
We are investigating errors with our cloud console affecting access to create, update, delete and view Elastic Cloud Hosted deployments. Our team is actively investigating the cause so that they can mitigate and restore the service.
-
monitoring Jul 15, 2026, 12:31 AM UTC
The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
-
resolved Jul 15, 2026, 01:12 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 12:15 PM UTC
- Resolved
- Jul 13, 2026, 12:19 PM UTC
- Duration
- 3m
Affected: Cloud console
Timeline · 2 updates
-
investigating Jul 13, 2026, 12:15 PM UTC
We are investigating a problem that prevents customers from authenticating against Elastic Cloud using their Microsoft login credentials
-
resolved Jul 13, 2026, 12:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 12:54 AM UTC
- Resolved
- Jul 02, 2026, 03:00 AM UTC
- Duration
- 2h 5m
Timeline · 3 updates
-
investigating Jul 02, 2026, 12:54 AM UTC
We have identified continued impact for a subset of affected customers using EIS. Our team is investigating an issue with the previous remediation and is working to ensure all affected environments are fully restored.
-
monitoring Jul 02, 2026, 02:24 AM UTC
The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.
-
resolved Jul 02, 2026, 03:00 AM UTC
The incident impacting a subset of customers with EIS in EMEA regions has been resolved. Services have been fully restored and the team has confirmed stability.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 10:43 PM UTC
- Resolved
- Jul 01, 2026, 11:05 PM UTC
- Duration
- 21m
Timeline · 4 updates
-
investigating Jul 01, 2026, 10:43 PM UTC
We are currently investigating a partial outage affecting the Elastic Integration Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
-
investigating Jul 01, 2026, 10:44 PM UTC
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
-
investigating Jul 01, 2026, 10:45 PM UTC
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
-
resolved Jul 01, 2026, 11:05 PM UTC
The issue affecting EIS for Elastic Cloud customers with projects or deployments on GCP and Azure in EMEA regions has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 03:39 PM UTC
- Resolved
- Jul 01, 2026, 08:23 PM UTC
- Duration
- 4h 43m
Affected: Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus
Timeline · 4 updates
-
investigating Jul 01, 2026, 03:39 PM UTC
We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual. What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions. What's not affected: Your deployments and projects are running normally. Data ingestion and all functionality remain unimpacted besides lacking some monitoring data on the Elastic Cloud UI. We're actively investigating the root cause and will provide an update within the next 2 hours.
-
identified Jul 01, 2026, 04:50 PM UTC
We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.
-
monitoring Jul 01, 2026, 07:50 PM UTC
The system has recovered and we are continuing to monitor the situation.
-
resolved Jul 01, 2026, 08:23 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 04:32 PM UTC
- Resolved
- Jun 29, 2026, 04:58 PM UTC
- Duration
- 26m
Timeline · 3 updates
-
identified Jun 29, 2026, 04:32 PM UTC
We have identified an issue with our ability to deliver certain static assets to our products. We have identified and are working to implement a fix.
-
identified Jun 29, 2026, 04:33 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Jun 29, 2026, 04:58 PM UTC
This issue has been resolved.
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Jun 17, 2026, 05:35 PM UTC
This issue has been resolved.
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Jun 17, 2026, 12:59 AM UTC
This issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 10:57 AM UTC
- Resolved
- Jun 16, 2026, 11:22 AM UTC
- Duration
- 24m
Affected: Elastic Cloud Hosted
Timeline · 1 update
-
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 →
- 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
-
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.
-
investigating Jun 16, 2026, 11:21 AM UTC
We are continuing to investigate this issue.
-
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 →
- 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
-
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.
-
monitoring Jun 15, 2026, 06:00 PM UTC
This issue has been mitigated, and we are continuing to monitor the situation.
-
resolved Jun 15, 2026, 07:13 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 01:51 AM UTC
- Resolved
- Jun 04, 2026, 09:20 AM UTC
- Duration
- 7h 28m
Timeline · 4 updates
-
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.
-
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.
-
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.
-
resolved Jun 04, 2026, 09:20 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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
-
resolved Jun 02, 2026, 07:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 06:00 PM UTC
- Resolved
- May 29, 2026, 06:36 PM UTC
- Duration
- 35m
Timeline · 2 updates
-
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.
-
resolved May 29, 2026, 06:36 PM UTC
This issue has been resolved.
Read the full incident report →
- 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 →