Elastic.io incident
AutoOps button disabled for some deployments created after December 3
Elastic.io experienced a major incident on December 11, 2025 affecting AutoOps, lasting 3h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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