Changes / Elastic Cloud / Delayed AutoOps Metrics in AWS us-east-1
Elastic Cloud: Major incident: Delayed AutoOps Metrics in AWS us-east-1
Summary
Elastic Cloud reported a major degradation causing delayed AutoOps metrics for customers in AWS us-east-1, starting 2026-04-30 21:46 UTC and lasting 50 min until resolution at 2026-04-30 22:36 UTC. The vendor reported the issue fixed and under monitoring at 04-30 22:18 UTC; no cause or specific fix was stated.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Delayed AutoOps Metrics in AWS us-east-1
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-30 21:46 UTC
Before: not present
After: 2026-04-30 22:36 UTC
Before: not present
After: AutoOps, Global services - AutoOps
Before: not present
After: We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
Before: not present
After: This issue has now been resolved and we are continuing to monitor the system.
Before: not present
After: This issue has now been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Delayed AutoOps Metrics in AWS us-east-1 (this change) Elastic Cloud reported a major degradation causing delayed AutoOps metrics for customers in AWS us-east-1, starting 2026-04-30 21:46 UTC and lasting 50 min until resolution at 2026-04-30 22:36 UTC. The vendor reported the issue fixed and under monitoring at 04-30 22:18 UTC; no cause or specific fix was stated. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON