Apr 18, 16:36 UTC
Identified - We have identified the issue and are working on rolling out a fix.
Apr 18, 14:28 UTC
Investigating - We are aware that some users may be receiving a 404 error when trying to open AutoOps deployment status pages. If you experience this error, you can work around it by opening the page in a new tab.
Apr 18, 14:28 UTC
Investigating - We are aware that some users may be receiving a 404 error when trying to open AutoOps deployment status pages. If you experience this error, you can work around it by opening the page in a new tab.
Apr 17, 15:09 UTC
Resolved - This incident has been resolved.
Apr 17, 00:57 UTC
Monitoring - We have deployed a fix for this issue and are monitoring to verify 7.x Elasticsearch deployments are properly reporting memory and disk usage both on cloud.elastic.co and via the deployments API.
Apr 16, 20:28 UTC
Identified - We've identified the issue and have begun deploying the fix into several regions. We anticipate to resolve the issue in the remaining regions within the next hour.
Apr 16, 18:00 UTC
Investigating - We've determined that some customers running 7.x Elasticsearch deployments may have issues seeing Instance memory and disk usage on cloud.elastic.co and through the deployments API. We're continuing to investigate the issue.
Apr 17, 14:55 UTC
Resolved - This incident has been resolved.
Apr 17, 08:59 UTC
Monitoring - The root cause has been identified and addressed. We are currently monitoring the system to ensure stability and performance.
Apr 16, 20:47 UTC
Update - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We have also determined that time shifts in lens may be incorrect.
Additionally, if you are using Elasticsearch directly and are using a filters aggregation, have a top level query, but have not turned on the "other_bucket", your results may be incorrect.
We have identified a fix for the issue and are validating the change before deploying to Elastic Cloud Serverless.
Apr 16, 19:33 UTC
Investigating - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We are continuing to investigate the issue.
Apr 17, 08:59 UTC
Monitoring - The root cause has been identified and addressed. We are currently monitoring the system to ensure stability and performance.
Apr 16, 20:47 UTC
Update - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We have also determined that time shifts in lens may be incorrect.
Additionally, if you are using Elasticsearch directly and are using a filters aggregation, have a top level query, but have not turned on the "other_bucket", your results may be incorrect.
We have identified a fix for the issue and are validating the change before deploying to Elastic Cloud Serverless.
Apr 16, 19:33 UTC
Investigating - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We are continuing to investigate the issue.
Apr 17, 00:57 UTC
Monitoring - We have deployed a fix for this issue and are monitoring to verify 7.x Elasticsearch deployments are properly reporting memory and disk usage both on cloud.elastic.co and via the deployments API.
Apr 16, 20:28 UTC
Identified - We've identified the issue and have begun deploying the fix into several regions. We anticipate to resolve the issue in the remaining regions within the next hour.
Apr 16, 18:00 UTC
Investigating - We've determined that some customers running 7.x Elasticsearch deployments may have issues seeing Instance memory and disk usage on cloud.elastic.co and through the deployments API. We're continuing to investigate the issue.
Apr 16, 22:38 UTC
Resolved - GCP has mitigated the Procurement API outage. We are working to reconcile any state updates that were attempted during the outage window, including new customer signups. If any further outage of the API occurs, we will create a new incident.
Apr 16, 21:05 UTC
Update - We're continuing to work with GCP towards resolution. Further updates will be posted as information becomes available.
Apr 16, 19:25 UTC
Update - We're working with GCP on mitigating the incident by rolling back access controls that were applied to their Procurement API. We will provide an update in 1 hour or upon mitigation.
Apr 16, 15:02 UTC
Investigating - We are currently investigating issues with our access to GCP's Procurement API, which is blocking new customer signups via GCP Marketplace. We will provide an update in 3 hours, or sooner if appropriate.
Apr 16, 21:05 UTC
Update - We're continuing to work with GCP towards resolution. Further updates will be posted as information becomes available.
Apr 16, 19:25 UTC
Update - We're working with GCP on mitigating the incident by rolling back access controls that were applied to their Procurement API. We will provide an update in 1 hour or upon mitigation.
Apr 16, 15:02 UTC
Investigating - We are currently investigating issues with our access to GCP's Procurement API, which is blocking new customer signups via GCP Marketplace. We will provide an update in 3 hours, or sooner if appropriate.
Apr 16, 20:47 UTC
Update - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We have also determined that time shifts in lens may be incorrect.
Additionally, if you are using Elasticsearch directly and are using a filters aggregation, have a top level query, but have not turned on the "other_bucket", your results may be incorrect.
We have identified a fix for the issue and are validating the change before deploying to Elastic Cloud Serverless.
Apr 16, 19:33 UTC
Investigating - We have determined that some customers on Elastic Cloud Serverless may see incorrect anomaly counts on anomaly detection jobs and some detection rules using filters may not be working correctly. We are continuing to investigate the issue.
Apr 16, 20:28 UTC
Identified - We've identified the issue and have begun deploying the fix into several regions. We anticipate to resolve the issue in the remaining regions within the next hour.
Apr 16, 18:00 UTC
Investigating - We've determined that some customers running 7.x Elasticsearch deployments may have issues seeing Instance memory and disk usage on cloud.elastic.co and through the deployments API. We're continuing to investigate the issue.