- Detected by Pingoru
- Feb 26, 2026, 11:29 AM UTC
- Resolved
- Feb 26, 2026, 05:07 PM UTC
- Duration
- 5h 37m
Affected: Elastic Cloud HostedElastic Cloud Serverless
Timeline · 3 updates
-
investigating Feb 26, 2026, 11:29 AM UTC
We're seeing some errors from fleet-server in Elastic Cloud that are affecting new incoming connections for some projects. We will provide an update within the next 2 hours.
-
monitoring Feb 26, 2026, 12:24 PM UTC
We have identified the root cause of those sporadic errors observed and have successfully mitigated the issue. We continue to observe the situation and provide an update within the next 2 hours.
-
resolved Feb 26, 2026, 05:07 PM UTC
This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 02:33 PM UTC
- Resolved
- Feb 25, 2026, 02:38 PM UTC
- Duration
- 5m
Affected: Elastic website - elastic.co
Timeline · 2 updates
-
investigating Feb 25, 2026, 02:33 PM UTC
We currently investigating an issue causing intermittent 404 errors when visiting the elastic.co webpage. We will provide additional updates as they become available.
-
resolved Feb 25, 2026, 02:38 PM UTC
404 errors have been resolved on the elastic.co webpage.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 05:56 PM UTC
- Resolved
- Feb 18, 2026, 07:12 PM UTC
- Duration
- 1h 15m
Affected: Elastic Cloud Hosted
Timeline · 2 updates
-
investigating Feb 18, 2026, 05:56 PM UTC
We are currently aware of and investigating an issue causing failure to provision new capacity in Elastic Cloud Hosted Azure regions. We will provide additional updates as they become available.
-
resolved Feb 18, 2026, 07:12 PM UTC
This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 06:21 PM UTC
- Resolved
- Feb 13, 2026, 12:46 AM UTC
- Duration
- 6h 25m
Timeline · 2 updates
-
identified Feb 12, 2026, 06:21 PM UTC
We've identified an issue on the billing usage pages where some hosted deployments might be showing incorrect usage. We're working on a fix and will update again in 6 hours.
-
resolved Feb 13, 2026, 12:46 AM UTC
We have identified and fixed an issue on the billing usage pages that resulted in the pages showing incorrect billing totals. There should be no more customer impact.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 06:35 PM UTC
- Resolved
- Feb 10, 2026, 10:51 PM UTC
- Duration
- 4h 16m
Timeline · 3 updates
-
investigating Feb 10, 2026, 06:35 PM UTC
We are investigating a degradation in BYOK deployment creation in Azure regions. We will update again in one hour.
-
identified Feb 10, 2026, 07:49 PM UTC
We have identified a misconfiguration in our Azure set up and working on pushing out the fix. Will update soon once it has been released.
-
resolved Feb 11, 2026, 01:01 PM UTC
This issue has been resolved, and BYOK deployment creation has been confirmed as fully functional.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 04:53 PM UTC
- Resolved
- Feb 10, 2026, 10:22 AM UTC
- Duration
- 17h 29m
Timeline · 3 updates
-
investigating Feb 09, 2026, 04:53 PM UTC
We've noticed a degradation in the `openai-gpt-oss-120b` model in EIS, we're investigating the root cause and we'll update again in 2 hours
-
investigating Feb 09, 2026, 07:35 PM UTC
We've identified the issue and have merged a fix. We are in the process of rolling this out but are blocked by a GitHub degradation. Will update as soon as we have some progress on the deploy.
-
resolved Feb 10, 2026, 10:22 AM UTC
We have completed our work to restore access to`openai-gpt-oss-120b` model in EIS.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 01:56 AM UTC
- Resolved
- Feb 06, 2026, 04:22 AM UTC
- Duration
- 2h 26m
Timeline · 3 updates
-
investigating Feb 06, 2026, 01:56 AM UTC
We are currently investigating an issue that has resulted in provisioning delays affecting the creation of new Elastic Cloud Serverless projects within the AWS us-east-1 region. While existing projects remain operational and unaffected, customers may encounter errors or extended wait times when attempting to spin up new projects in this specific region. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will provide further updates as more information becomes available.
-
identified Feb 06, 2026, 02:43 AM UTC
We have successfully identified the root cause of the provisioning delays in the AWS us-east-1 region and are now beginning the remediation phase. A fix has been developed and validated through internal testing, and we are currently rolling out the fix across the affected infrastructure. Customers may still see intermittent failures for a short period as the fix propagates.
-
resolved Feb 06, 2026, 04:22 AM UTC
The issues affecting Elastic Cloud Serverless project creation in the AWS us-east-1 region have been resolved. Our engineering team identified a DNS configuration error as the root cause; once the records were corrected and propagated, service functionality returned to normal. All systems are now operating as expected, and customers should no longer experience delays or errors when creating new projects. We appreciate your patience while we worked to clear this up.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 11:01 PM UTC
- Resolved
- Feb 03, 2026, 10:42 AM UTC
- Duration
- 11h 41m
Timeline · 5 updates
-
monitoring Feb 02, 2026, 11:01 PM UTC
We are aware of an active incident involving Microsoft Azure infrastructure that is impacting Elastic Serverless and Elastic Hosted services. Customers may experience failures or significant delays when attempting to provision new Serverless projects, create new Hosted deployments, or perform scaling operations on existing clusters. Our engineering team is closely monitoring the situation. Existing, steady-state deployments in Azure remain operational. There is also no impact to projects or deployments in other cloud providers. We will provide further updates as more information becomes available.
-
monitoring Feb 03, 2026, 12:26 AM UTC
We are continuing to monitor an open incident on the Microsoft Azure side. At this time, we are not aware of any further active impact to Elastic customers or services; however, we will remain in a monitoring state until Azure provides official confirmation that the incident is fully resolved on their end.
-
monitoring Feb 03, 2026, 03:52 AM UTC
There is no new information to report at this time. We are still awaiting a final resolution from Microsoft Azure regarding their ongoing incident. As soon as Azure confirms the issue is resolved on their side, we will provide a final update.
-
monitoring Feb 03, 2026, 07:37 AM UTC
We are closely monitoring the situation as we await Microsoft Azure's final resolution regarding their ongoing incidents. Currently, we are not aware of any additional impact on Elastic customers or services. However, we will maintain a very close monitoring status until Azure provides official confirmation that the incident is fully resolved.
-
resolved Feb 03, 2026, 10:42 AM UTC
The incidents affecting us have been resolved on Azure's side. All Elastic services are fully operational and no further impact was observed during the past 4 hours. Hence, we mark this incident as resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 01:10 AM UTC
- Resolved
- Jan 23, 2026, 07:31 AM UTC
- Duration
- 6h 20m
Timeline · 3 updates
-
monitoring Jan 23, 2026, 01:10 AM UTC
Some Elastic Cloud customers may be experiencing issues with receiving emails for account verification and MFA due to an upstream third-party incident. We are actively monitoring this and will post periodic updates or as new information becomes available.
-
monitoring Jan 23, 2026, 03:55 AM UTC
We are continuing to monitor the status of the upstream provider's incident. We will continue to post periodic updates or as new information becomes available.
-
resolved Jan 23, 2026, 07:31 AM UTC
We have completed our work to restore service to Elastic Cloud email and MFA services. The upstream third-party incident that was affecting account verification and MFA emails has been resolved, and all systems are now operating normally. We have confirmed that email delivery has returned to expected levels.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 12:37 AM UTC
- Resolved
- Jan 23, 2026, 03:51 AM UTC
- Duration
- 3h 14m
Timeline · 3 updates
-
investigating Jan 23, 2026, 12:37 AM UTC
Customers may observe some data delay in AutoOps functionality for Elastic Cloud Hosted clusters in GCP US Central. We're actively investigating this.
-
monitoring Jan 23, 2026, 12:56 AM UTC
We've determined that AutoOps functionality has fully recovered for Elastic Cloud Hosted clusters in GCP US Central.
-
resolved Jan 23, 2026, 03:51 AM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 24, 2025, 08:37 AM UTC
- Resolved
- Dec 25, 2025, 03:17 AM UTC
- Duration
- 18h 39m
Affected: AutoOps
Timeline · 16 updates
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2025, 03:29 AM UTC
- Resolved
- Dec 23, 2025, 05:29 AM UTC
- Duration
- 2h
Affected: AutoOps
Timeline · 4 updates
-
investigating Dec 23, 2025, 03:29 AM UTC
We are currently investigating a partial 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.
-
identified Dec 23, 2025, 04:24 AM UTC
We have identified the underlying cause of the issue and are applying a fix. We will post another update as it becomes available or within an hour, whichever is first.
-
monitoring Dec 23, 2025, 04:47 AM UTC
We are seeing recovery in the system with the deployed fix, and are continuing to monitor the health of the system.
-
resolved Dec 23, 2025, 05:29 AM UTC
The system is operational.
Read the full incident report →
Critical December 17, 2025 - Detected by Pingoru
- Dec 17, 2025, 12:10 PM UTC
- Resolved
- Dec 17, 2025, 12:49 PM UTC
- Duration
- 38m
Timeline · 2 updates
-
identified Dec 17, 2025, 12:10 PM UTC
We're aware of delays affecting emails being sent for customers, such as password reset requests, receiving billing invoices and adding users to organisations. Our team is investigating the issue and we will provide updates on our progress.
-
resolved Dec 17, 2025, 12:49 PM UTC
Our teams have resolved an issue with the mail system, which caused delays for emails being sent for customers such as password reset requests, receiving billing invoices and adding users to organisations.
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 04:50 PM UTC
- Resolved
- Dec 11, 2025, 08:23 PM UTC
- Duration
- 3h 33m
Affected: AutoOps
Timeline · 4 updates
-
identified Dec 11, 2025, 04:50 PM UTC
We are aware of an issue impacting deployments created after December 3rd that causes the AutoOps button to appear greyed out. Affected AWS regions are af-south-1, ap-east-1, ap-northeast-2, aws-ap-southeast-2, ca-central-1, me-south-1, sa-east-1, eu-north-1, eu-south-1, eu-west-3, us-west-1, eu-central-2. The us-central-1 GCP region is also affected. Our engineers have been engaged and are currently working on a resolution. We will provide an update within 1 hour, or sooner if appropriate
-
identified Dec 11, 2025, 05:58 PM UTC
Our engineers have deployed a change and new deployments will be able to use AutoOps. We are still working on fixing the affected deployments between December 3 and today. We will provide an update within 1 hour, or sooner if appropriate.
-
monitoring Dec 11, 2025, 06:56 PM UTC
We have completed the roll out of the fix and are monitoring to confirm resolution. We will post an update in an hour or sooner.
-
resolved Dec 11, 2025, 08:23 PM UTC
The fix is working as expected. This issue is resolved
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 08:29 PM UTC
- Resolved
- Dec 04, 2025, 10:31 PM UTC
- Duration
- 2h 1m
Timeline · 3 updates
-
identified Dec 04, 2025, 08:29 PM UTC
We are aware of issues where system emails are not being delivered. We are investigating and will provide an update in two hours or earlier on our investigation.
-
monitoring Dec 04, 2025, 08:59 PM UTC
We've identified the issue and have started processing the backlog of emails. We will continue to monitor the situation until the backlog is cleared.
-
resolved Dec 04, 2025, 10:31 PM UTC
This incident is now resolved as the backlog of emails has been cleared.
Read the full incident report →
- Detected by Pingoru
- Nov 28, 2025, 10:42 PM UTC
- Resolved
- Nov 29, 2025, 11:25 AM UTC
- Duration
- 12h 43m
Timeline · 8 updates
-
investigating Nov 28, 2025, 10:42 PM UTC
We are currently investigating an increase in HTTP 502 errors affecting Serverless projects running in Azure regions.
-
investigating Nov 29, 2025, 12:02 AM UTC
We are continuing our investigation into the intermittent 5xx errors in Azure Serverless projects. We will update again in an hour.
-
identified Nov 29, 2025, 01:24 AM UTC
We have identified a potential fix that we are in the process of rolling out. We anticipate this to be complete in approximately 3-4 hours. We will update when this process is complete.
-
identified Nov 29, 2025, 05:20 AM UTC
We are continuing the rollout of the potential fix. We will update again in an hour
-
identified Nov 29, 2025, 06:50 AM UTC
We are continuing the rollout of the potential fix. We will update again in an hour
-
identified Nov 29, 2025, 07:50 AM UTC
We are continuing the rollout of the potential fix. We will update again in an hour
-
monitoring Nov 29, 2025, 10:08 AM UTC
We have completed the roll out of the fix and are monitoring to confirm resolution. We will post an update in an hour or sooner.
-
resolved Nov 29, 2025, 11:25 AM UTC
The fix is working as expected. This issue is resolved
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 04:52 AM UTC
- Resolved
- Nov 21, 2025, 06:09 AM UTC
- Duration
- 1h 16m
Affected: Managed Intake Service AvailabilityManaged OTLP Endpoint
Timeline · 4 updates
-
investigating Nov 21, 2025, 04:52 AM UTC
We are aware of ingestion problems in Managed OTLP Endpoint & Managed Intake Service for GCP us-central1 region since 0338 UTC. Other regions remain unaffected. We are currently investigating the problem. We will publish more information as it becomes available. Next update in 1 hr
-
investigating Nov 21, 2025, 05:11 AM UTC
We are continuing to investigate this issue.
-
monitoring Nov 21, 2025, 05:48 AM UTC
Ingestion rates are back to normal, we're currently monitoring the situation.
-
resolved Nov 21, 2025, 06:09 AM UTC
Ingestion rates are normal, the incident is resolved
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 01:46 PM UTC
- Resolved
- Nov 18, 2025, 06:35 PM UTC
- Duration
- 4h 48m
Affected: Elastic website - elastic.co
Timeline · 3 updates
-
monitoring Nov 18, 2025, 01:46 PM UTC
We are seeing intermittent 404s/500s on elastic.co. This is due to an outage with one of our providers. Our team is monitoring and will update as we know more.
-
monitoring Nov 18, 2025, 03:28 PM UTC
The underlying outage with our provider is reported as resolved. We will continue monitoring to ensure our service is fully operational.
-
resolved Nov 18, 2025, 06:35 PM UTC
The situation has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 16, 2025, 09:12 PM UTC
- Resolved
- Nov 17, 2025, 12:52 AM UTC
- Duration
- 3h 39m
Timeline · 3 updates
-
investigating Nov 16, 2025, 09:12 PM UTC
We are currently investigating an issue with Elastic Cloud Hosted in the eu-west-1 region of AWS. Customers may be experiencing issues with upgrades, new deployments, and vacates in that region.
-
investigating Nov 16, 2025, 10:33 PM UTC
We are actively investigating the root cause of the incident and are working towards a full resolution. The next update will be provided as soon as significant progress is made or a preliminary resolution timeframe is established.
-
resolved Nov 17, 2025, 12:52 AM UTC
The issue has been successfully mitigated and full service has been restored to the AWS region; the root cause involved an internal provisioning system temporarily preventing the application of new hosted plans, which has now been corrected. We will continue to monitor the system closely.
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 06:20 AM UTC
- Resolved
- Nov 14, 2025, 07:11 AM UTC
- Duration
- 50m
Affected: Elastic Cloud Serverless
Timeline · 4 updates
-
investigating Nov 14, 2025, 06:20 AM UTC
We are currently investigating an issue that prevents creating new Serverless projects. Our team is working to find the cause, and we will provide a status update as soon as more information becomes available.
-
identified Nov 14, 2025, 06:23 AM UTC
We have identified the root cause of the issue affecting the creation of new Serverless projects. Our team is currently preparing a patch to restore full functionality. We will provide another update once the fix is deployed.
-
monitoring Nov 14, 2025, 06:32 AM UTC
We have deployed a fix for the issue affecting the creation of new Serverless projects. The service is operating as expected, and we are monitoring the system to ensure stability. We will provide a final update once the incident is fully resolved.
-
resolved Nov 14, 2025, 07:11 AM UTC
The issue affecting the creation of new Serverless projects has been fully resolved. The service is functioning normally, and no further impact is expected.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 08:47 PM UTC
- Resolved
- Nov 12, 2025, 10:38 PM UTC
- Duration
- 1h 50m
Timeline · 4 updates
-
investigating Nov 12, 2025, 08:47 PM UTC
We are aware of an issue impacting all serverless regions interacting with the Synthetics service. We will provide an update when more information is available or in one hour, whichever is sooner.
-
investigating Nov 12, 2025, 09:51 PM UTC
We are continuing to investigate this issue. We will share an update when one is available or one hour from now, whichever comes first.
-
monitoring Nov 12, 2025, 10:21 PM UTC
We have identified the cause of this issue and are currently applying a fix. We are seeing recovery in the system and will continue to monitor.
-
resolved Nov 12, 2025, 10:38 PM UTC
This issue has been resolved, and system operations returned to normal.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 04:44 PM UTC
- Resolved
- Nov 12, 2025, 05:34 PM UTC
- Duration
- 50m
Affected: Elasticsearch connectivity: AWS us-east-1Kibana connectivity: AWS us-east-1Elastic Cloud Serverless
Timeline · 3 updates
-
monitoring Nov 12, 2025, 04:44 PM UTC
We recently detected intermittent network latency in the AWS us-east-1 region, which may have briefly caused connection timeouts for some Serverless projects. Our monitoring indicates that service health has returned to normal. We are continuing to actively monitor the situation to ensure continued stability. Expect next update in 60 mins or as soon as we have any updates to share.
-
monitoring Nov 12, 2025, 04:49 PM UTC
We recently investigated intermittent network latency in the AWS us-east-1 region, which may have briefly caused connection timeouts for some Serverless projects and Elastic Cloud Hosted deployments. Our monitoring indicates that service health has returned to normal. We are continuing to actively monitor the situation to ensure continued stability. Expect next update in 60 mins or as soon as we have any updates to share.
-
resolved Nov 12, 2025, 05:34 PM UTC
We can confirm no connectivity or latency issues in the last 60 minutes. We consider this resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 04:59 PM UTC
- Resolved
- Oct 30, 2025, 01:19 AM UTC
- Duration
- 8h 19m
Timeline · 2 updates
-
investigating Oct 29, 2025, 04:59 PM UTC
We are currently investigating an issue with Azure impacting some of our services, specifically Managed OTLP and MIS.
-
resolved Oct 30, 2025, 01:19 AM UTC
We are currently investigating an issue with Azure impacting some of our services, specifically Managed OTLP and MIS.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 11:22 AM UTC
- Resolved
- Oct 22, 2025, 12:44 PM UTC
- Duration
- 1h 22m
Affected: APM connectivity: AWS us-east-1
Timeline · 3 updates
-
investigating Oct 22, 2025, 11:22 AM UTC
We are experiencing an issue with new Deployments taking longer than expected to create in AWS us-east-1. We'll post an update on this within the hour
-
monitoring Oct 22, 2025, 12:05 PM UTC
This issue has been mitigated and new Deployments are coming up as expected. We are continuing to monitor.
-
resolved Oct 22, 2025, 12:44 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 09:46 AM UTC
- Resolved
- Oct 22, 2025, 12:11 PM UTC
- Duration
- 2h 25m
Affected: APM connectivity: GCP us-central1
Timeline · 3 updates
-
investigating Oct 22, 2025, 09:46 AM UTC
We are aware of issues impacting the display of deployment metrics in Elastic Cloud Hosted GCP us-central1 region, we are working to resolve this
-
monitoring Oct 22, 2025, 11:35 AM UTC
The issue has been resolved and a backlog of metrics is being processed which should clear in the next hour.
-
resolved Oct 22, 2025, 12:11 PM UTC
The issue has been fully resolved.
Read the full incident report →