Elasticsearch outage: Synthetics service may not run on schedule (us-east-4)

1. resolvedApr 6, 2026, 20:43 UTC

   Issue has been fixed and there should be no more customer impact

2. identifiedApr 6, 2026, 19:16 UTC

   We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.

3. investigatingApr 6, 2026, 17:58 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Elasticsearch's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• LaunchDarkly: Delayed processing of Session Replay and Error dataMinor · Apr 6, 2026, 17:58 UTC
• Amplitude: Users Unable to Sign In with External ToolsMinor · Apr 6, 2026, 19:53 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 23 incidents in the last 90 days, 20 of them major or critical. A typical incident lasted 3h 35m. See Elasticsearch's uptime and incident history