Elastic Cloud incident
Upstream cloud provider incident impacting Project Creation/Deployments
Elastic Cloud experienced a major incident on February 2, 2026, lasting 11h 41m. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Feb 02, 2026, 11:01 PM UTC
We are aware of an active incident involving Microsoft Azure infrastructure that is impacting Elastic Serverless and Elastic Hosted services. Customers may experience failures or significant delays when attempting to provision new Serverless projects, create new Hosted deployments, or perform scaling operations on existing clusters. Our engineering team is closely monitoring the situation. Existing, steady-state deployments in Azure remain operational. There is also no impact to projects or deployments in other cloud providers. We will provide further updates as more information becomes available.
- monitoring Feb 03, 2026, 12:26 AM UTC
We are continuing to monitor an open incident on the Microsoft Azure side. At this time, we are not aware of any further active impact to Elastic customers or services; however, we will remain in a monitoring state until Azure provides official confirmation that the incident is fully resolved on their end.
- monitoring Feb 03, 2026, 03:52 AM UTC
There is no new information to report at this time. We are still awaiting a final resolution from Microsoft Azure regarding their ongoing incident. As soon as Azure confirms the issue is resolved on their side, we will provide a final update.
- monitoring Feb 03, 2026, 07:37 AM UTC
We are closely monitoring the situation as we await Microsoft Azure's final resolution regarding their ongoing incidents. Currently, we are not aware of any additional impact on Elastic customers or services. However, we will maintain a very close monitoring status until Azure provides official confirmation that the incident is fully resolved.
- resolved Feb 03, 2026, 10:42 AM UTC
The incidents affecting us have been resolved on Azure's side. All Elastic services are fully operational and no further impact was observed during the past 4 hours. Hence, we mark this incident as resolved.