Changes / Elastic Cloud / Temporarily unavailability of Serverless Projects Functionality
Elastic Cloud: Major incident: Temporarily unavailability of Serverless Projects Functionality
Summary
Elastic Cloud reported a major outage affecting multiple Serverless projects, including AWS - N.Virginia (us-east-1) Elasticsearch Availability. Search, Ingest and EIS may have been unavailable from 08:00 UTC to 09:40 UTC on May 11. The incident started at 2026-05-11 08:00 UTC and was resolved at 2026-05-11 11:11 UTC, lasting 3 h 11 min; Elastic stated the root cause was resolved.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Temporarily unavailability of Serverless Projects Functionality
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-11 08:00 UTC
Before: not present
After: 2026-05-11 11:11 UTC
Before: not present
After: AWS - N.Virginia (us-east-1) - Elasticsearch Availability, Elasticsearch Availability
Before: not present
After: We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable.
The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.
Before: not present
After: We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.
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: Temporarily unavailability of Serverless Projects Functionality (this change) Elastic Cloud reported a major outage affecting multiple Serverless projects, including AWS - N.Virginia (us-east-1) Elasticsearch Availability. Search, Ingest and EIS may have been unavailable from 08:00 UTC to 09:40 UTC on May 11. The incident started at 2026-05-11 08:00 UTC and was resolved at 2026-05-11 11:11 UTC, lasting 3 h 11 min; Elastic stated the root cause was resolved. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON