Elastic Cloud incident
Serverless Project and Hosted Deployment Creation Issues
Elastic Cloud experienced a major incident on September 30, 2025, lasting 8h 1m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Sep 30, 2025, 02:48 AM UTC
We are aware of an issue impacting the creation of new Serverless projects and Hosted deployments to fail. Our engineering team has been engaged. We will post an additional status update in the next 60 minutes.
- investigating Sep 30, 2025, 03:57 AM UTC
We are aware of an issue impacting the creation on both Serverless projects and Hosted deployments. Our engineering team is working to remediate this issue. We will post another status update in the next 60 minutes.
- investigating Sep 30, 2025, 06:00 AM UTC
We are continuing our efforts to restore full service to the creation of both Serverless projects and Hosted deployments. Our teams are working collaboratively in their impact mitigation efforts and we are actively driving to a resolution. We will post an update in one hour, or sooner if there is a change in status.
- investigating Sep 30, 2025, 06:38 AM UTC
We are continuing our efforts to restore full service to the creation of both Serverless projects and Hosted deployments and the Billing information pages. Our teams are working collaboratively in their impact mitigation efforts and we are actively driving to a resolution. We will post an update in one hour, or sooner if there is a change in status.
- investigating Sep 30, 2025, 08:00 AM UTC
Our engineering teams are making good progress on the investigation into the issue affecting the creation of Serverless projects, Hosted deployments, and Billing pages. We are still actively working toward a resolution. We will provide our next update in 60 minutes.
- identified Sep 30, 2025, 09:06 AM UTC
We have identified an issue for creating new Serverless projects and Hosted deployments. Billing information pages are also impacted and do not load. We are continue our efforts in working this issue to a resolution state. We will post an update in one hour, or sooner if there is a change in status.
- resolved Sep 30, 2025, 10:49 AM UTC
This incident has been resolved.