Elasticsearch outage: GCP asia-south1 high latency

Affected components

• Elasticsearch connectivity: GCP asia-south1

1. resolvedAug 6, 2026, 17:41 UTC

   On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.

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.

• GitHub: Incident with ActionsCritical · Aug 6, 2026, 15:22 UTC
• RevenueCat: Rico is having issuesCritical · Aug 6, 2026, 17:04 UTC
• HashiCorp Vault: HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.Minor · Aug 5, 2026, 19:08 UTC
• Snyk: SNYK-US-01 Test Service DegradationMinor · Aug 5, 2026, 19:26 UTC
• Vercel: Delays delivering log drainsMinor · Aug 6, 2026, 16:37 UTC

How often does Elasticsearch have incidents?

Elasticsearch reported 23 incidents in the last 90 days, 20 of them major or critical. A typical incident lasted 3h 35m. See Elasticsearch's uptime and incident history