View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Mon, 02 Mar 2026 06:23:20 GMT |
| Latest update published (provider) | Mon, 21 Sep 2026 15:21:45 GMT |
| Seen by Spike | Wed, 18 Nov 2026 03:42:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | identified | Direct: Elastic Cloud status page · source ↗ |
| affected services | AWS EC2 Health: me-south-1, Snapshot Storage Infrastructure (S3): me-south-1, Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1, APM connectivity: AWS me-south-1, AWS Infrastructure health: me-south-1, Elasticsearch connectivity: AWS me-south-1, Kibana connectivity: AWS me-south-1 | Direct: Elastic Cloud status page · source ↗ |
| affected regions | me-south-1 | Direct: Elastic Cloud status page · source ↗ |
| Cause | Elastic Cloud has not stated a cause in a structured field. Read the provider's updates. | |
| Customer impact | Depends on what you run. Spike Pro matches this incident to the services a workspace lists. | |
Revisions, newest first
- Revision 1 · First recorded by Spike
Published by Elastic Cloud 2026-09-21 15:21 UTC · seen by Spike 82821 min laterElastic Cloud said: “Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable…”