AutoOps deployments marked as Inactive in AWS us-east-1 region
Mar 27, 04:33 UTCMar 27, 07:23 UTC
Duration
2h 50m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
AutoOpsGlobal services - AutoOps
Final update
AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.
Timeline
- 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.
- 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.
- 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.
- 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 historymOLTP PrivateLink connectivity issuelasted 13h 28mElastic Support Portal is unavailablelasted 2h 29m403 error when trying to access Autoops in newly created serverless projectslasted 9h 31mElastic Cloud scaling issues in Azurelasted 6h 57mDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)lasted 15h 3mDelayed or Unavailable project operation in GCP us-central1lasted 8h 12m