Skip to content
Elastic · Data and observabilityMar 27, 2026, 04:33 UTC

AutoOps deployments marked as Inactive in AWS us-east-1 region

MajorNot disclosedUpdated 19h ago
Mar 27, 04:33 UTCMar 27, 07:23 UTC
Duration
2h 50m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
27 incidents
Affected
AutoOpsGlobal services - AutoOps
Status page

Final update

AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.

Timeline

  1. Resolved · Mar 27, 07:23 UTC
    AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.
  2. Monitoring · Mar 27, 07:13 UTC
    We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved.
  3. Monitoring · Mar 27, 05:37 UTC
    We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.
  4. Investigating · Mar 27, 04:33 UTC
    We are currently investigating an outage of AutoOps in AWS us-east-1 region. 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.

More from Elastic

Full history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.