Incidentsby GlyphGCP asia-south1 high latency
Aug 6, 17:41 UTCAug 6, 17:41 UTC
Duration
0m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
Elasticsearch connectivity: GCP asia-south1GCP Mumbai (asia-south1) - Elasticsearch connectivity: GCP asia-south1
Final update
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.
Timeline
- Resolved · Aug 6, 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.
More from Elastic
Full historymOLTP PrivateLink connectivity issuelasted 13h 28mElastic Support Portal is unavailablelasted 2h 29m403 error when trying to access Autoops in newly created serverless projectslasted 9h 31mElastic Cloud scaling issues in Azurelasted 6h 57mDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)lasted 15h 3mDelayed or Unavailable project operation in GCP us-central1lasted 8h 12m