Live  /  Elastic Cloud (Public)  /  Incident

Elastic Cloud (Public): Delayed or Unavailable project operation in GCP us-central1

Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-10-09 00:54 UTC
Public — what happened

Summary

Elastic Cloud (Public) said that starting at 16:42 UTC on October 8, 2026, some of its Serverless projects in Google Cloud's us-central1 region could have operations that were slow or not working at all. By 17:21 UTC the company said it had traced the problem to cloud storage, and that its storage provider was looking into it. Elastic reported seeing improvement at 20:47 UTC after the provider put fixes in place, though some projects were still recovering at that point. The incident was marked resolved at 00:54 on October 9.

Affected

GCP Infrastructure health: us-central1

As listed on Elastic Cloud (Public)’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Elastic Cloud (Public) report →

More from Elastic Cloud (Public)

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Elastic Cloud (Public) status & history page.

Related: Elastic Cloud (Public) status & history. SquidGrid is not affiliated with Elastic Cloud (Public).