Skip to main content
Elastic Cloud

Delayed or Unavailable project operation in GCP us-central1

Partial outage Lasted 8h 12m · started · Elastic Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
GCP Infrastructure health: us-central1
Regions
us, us-central1
Down Index
40of 100

What to do

  • Check whether you use Elastic Cloud GCP Infrastructure health: us-central1 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 12m it lasted.

    Anything that failed between 2026-10-08 16:42 UTC and 2026-10-09 00:54 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

  1. investigating

    We are investigating an issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operation.

    provider

  2. identified

    We have identified an issue with cloud storage affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operations. The provider is investigating the issue, and we are monitoring recovery. We will provide another update when more information is available.

    provider

  3. identified

    Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations. The provider is continuing to investigate the issue. We are monitoring the situation and will provide another update when more information is available.

    provider

  4. monitoring

    We have observed improvements after mitigations were applied by our upstream cloud storage provider. Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations while recovery continues. We are monitoring the situation and will provide another update when more information is available.

    provider

  5. resolved

    The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.

    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-65e0f6629f

Is Elastic Cloud still down?

No, this incident was resolved 2026-10-09 00:54 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.

How long did it last?

8h 12m, from 2026-10-08 16:42 UTC to 2026-10-09 00:54 UTC, by the times Elastic Cloud posted.

What was affected?

Elastic Cloud named GCP Infrastructure health: us-central1 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.