- Level
- confirmed
- Worst impact
- Degraded
- Components
- Deployment orchestration (Create/Edit/Restart/Delete): GCP us-central1, Elastic Docker Registry
- Regions
- us, us-central1
- Down Index
- 30of 100
What to do
Check whether you use Elastic Cloud Deployment orchestration (Create/Edit/Restart/Delete): GCP us-central1, Elastic Docker Registry in us, us-central1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8h 57m it lasted.
Anything that failed between 2026-03-09 11:32 UTC and 2026-03-09 20:29 UTC may need a replay.Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Elastic Cloud 5
- investigating
We have identified an issue impacting the provisioning of kibana resources for new projects. This may delay or fail requests for new projects. We are investigating the root cause, and will post updates shortly.
provider
- investigating
Further investigations has indentified additional impact across services hosted in the GCP us-central1 region. We are working internally, and with our hosting providers to determine the root cause.
provider
- identified
The issue has been identified, and we are working with our hosting providers to reach a solution. Users may see an impact with the availability of the elastic docker registry (browsing, and pulling images) Users may see an impact with the orchestration of their hosted Serverless projects, leading to slower provisioning and scaling tasks.
provider
- monitoring
We have seen an improvement regarding this service disruption. The docker registry is available, and project orchestration has been restored. We will continue to monitor the situation, and ensure a full service recovery.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-176a0a410b
Is Elastic Cloud still down?
No, this incident was resolved 2026-03-09 20:29 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
8h 57m, from 2026-03-09 11:32 UTC to 2026-03-09 20:29 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named Deployment orchestration (Create/Edit/Restart/Delete): GCP us-central1, Elastic Docker Registry in us, us-central1.
What caused it?
Elastic Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.