- 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 →
- Detected by Pingoru
- May 26, 2026, 09:35 PM UTC
- Resolved
- May 26, 2026, 09:35 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- May 22, 2026, 04:54 AM UTC
- Resolved
- May 22, 2026, 04:54 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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 →
- Detected by Pingoru
- May 08, 2026, 06:10 PM UTC
- Resolved
- May 09, 2026, 01:01 AM UTC
- Duration
- 6h 50m
Timeline · 3 updates
-
investigating May 08, 2026, 06:10 PM UTC
We are currently investigating reports that some customers may be facing issues with email alerts.
-
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.
-
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 →
- 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
-
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.
-
monitoring Apr 30, 2026, 10:18 PM UTC
This issue has now been resolved and we are continuing to monitor the system.
-
resolved Apr 30, 2026, 10:36 PM UTC
This issue has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 02:46 PM UTC
- Resolved
- Apr 28, 2026, 06:40 PM UTC
- Duration
- 3h 53m
Timeline · 5 updates
-
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.
-
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.
-
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.
-
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.
-
resolved Apr 28, 2026, 06:40 PM UTC
The system has recovered and functionality has returned to normal.
Read the full incident report →