- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Elasticsearch connectivity: GCP asia-south1
- Regions
- apac, asia-south1
- Down Index
- 26of 100
What to do
Check whether you use Elastic Cloud Elasticsearch connectivity: GCP asia-south1 in apac, asia-south1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-08-06 17:41 UTC and 2026-08-06 17:41 UTC may need a replay.Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Elastic Cloud 1
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bb7afad722
Is Elastic Cloud still down?
No, this incident was resolved 2026-08-06 17:41 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.
How long did it last?
0m, from 2026-08-06 17:41 UTC to 2026-08-06 17:41 UTC, by the times Elastic Cloud posted.
What was affected?
Elastic Cloud named Elasticsearch connectivity: GCP asia-south1 in apac, asia-south1.
What caused it?
Elastic Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.