Delayed AutoOps Metrics in AWS us-east-1
Apr 30, 21:46 UTCApr 30, 22:36 UTC
Duration
51m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
AutoOpsGlobal services - AutoOps
Final update
This issue has now been resolved.
Timeline
- Resolved · Apr 30, 22:36 UTC
This issue has now been resolved.
- Monitoring · Apr 30, 22:18 UTC
This issue has now been resolved and we are continuing to monitor the system.
- Identified · Apr 30, 21:46 UTC
We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
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