Elasticsearch outage: Delayed or Unavailable project operation in GCP us-central1

Affected components

• GCP Infrastructure health: us-central1

1. resolvedOct 9, 2026, 00:54 UTC

   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.

2. monitoringOct 8, 2026, 20:47 UTC

   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.

3. identifiedOct 8, 2026, 19:17 UTC

   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.

4. identifiedOct 8, 2026, 17:21 UTC

   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.

5. investigatingOct 8, 2026, 16:42 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Elasticsearch's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Fly.io: Sprite creates failingCritical · Oct 8, 2026, 21:23 UTC
• Shippo: La Poste and Colissimo's Transaction & Tracking API OutageCritical · Oct 8, 2026, 21:43 UTC
• Anthropic: Elevated errors on platform.claude.comMajor · Oct 7, 2026, 13:25 UTC
• ElevenLabs: Increased Dubbing Latency and Failure RateMajor · Oct 8, 2026, 16:09 UTC
• Sanity: Elevated listener latency affecting Studio performanceMajor · Oct 8, 2026, 18:27 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 22 incidents in the last 90 days, 21 of them major or critical. A typical incident lasted 5h 53m. See Elasticsearch's uptime and incident history