Changes / Elastic Cloud / Synthetics service may not run on schedule (us-east-4)
Elastic Cloud: Major incident: Synthetics service may not run on schedule (us-east-4)
Summary
Elastic Cloud reported a major Synthetics degradation in us-east-4: some customer monitor jobs may not have run on schedule. The incident started at 2026-04-06 17:58 UTC and was resolved at 2026-04-06 20:43 UTC, lasting 2 h 45 min; Elastic stated the issue was fixed with no further customer impact.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 90%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Synthetics service may not run on schedule (us-east-4)
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-06 17:58 UTC
Before: not present
After: 2026-04-06 20:43 UTC
Before: not present
After: We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.
Before: not present
After: We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.
Before: not present
After: Issue has been fixed and there should be no more customer impact
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: Synthetics service may not run on schedule (us-east-4) (this change) Elastic Cloud reported a major Synthetics degradation in us-east-4: some customer monitor jobs may not have run on schedule. The incident started at 2026-04-06 17:58 UTC and was resolved at 2026-04-06 20:43 UTC, lasting 2 h 45 min; Elastic stated the issue was fixed with no further customer impact. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON