Changes / Elastic Cloud / GCP asia-south1 high latency
Elastic Cloud: Major incident: GCP asia-south1 high latency
Summary
Elastic Cloud reported major Elasticsearch connectivity latency in GCP asia-south1 (Mumbai), with possible customer impact on 2026-08-06 between 0900 - 1200 UTC. The incident record started and resolved at 2026-08-06 17:41 UTC (computed duration: 0 min); the vendor said the cause was identified and mitigated but provided no details.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: GCP asia-south1 high latency
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-06 17:41 UTC
Before: not present
After: 2026-08-06 17:41 UTC
Before: not present
After: Elasticsearch connectivity: GCP asia-south1, GCP Mumbai (asia-south1) - Elasticsearch connectivity: GCP asia-south1
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: GCP asia-south1 high latency (this change) Elastic Cloud reported major Elasticsearch connectivity latency in GCP asia-south1 (Mumbai), with possible customer impact on 2026-08-06 between 0900 - 1200 UTC. The incident record started and resolved at 2026-08-06 17:41 UTC (computed duration: 0 min); the vendor said the cause was identified and mitigated but provided no details. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON