checked Oct 29, 2026 4:04 AM UTC · Elastic Cloud's official status page
Elastic Cloud has disruptions affecting APM connectivity: AWS me-south-1, AWS EC2 Health: me-south-1, AWS Infrastructure health: me-south-1, and other components.
Operational: Global services, Synthetics - Global Managed Testing Infrastructure, GCP Belgium (europe-west1).
Statusfield watches Elastic Cloud alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
9 reports published by Elastic Cloud in the last 30 days
resolvedOct 23 · 06:33 UTC
The upstream provider has completed its fix, and access to the Elastic Support portal has been restored. Customers can authenticate to the support portal again. We are considering this issue resolved and will be providing no further updates. If you continue to have issues, please contact us.
Reported by Elastic Cloud on their status page.
resolvedOct 22 · 20:50 UTC
We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.
Reported by Elastic Cloud on their status page.
resolvedOct 21 · 03:05 UTC
Engineers have mitigated an issue affecting the ability to scale existing Elastic Cloud Hosted deployments and Serverless projects in Azure. Scaling is working as expected.
Reported by Elastic Cloud on their status page.
resolvedOct 20 · 21:54 UTC
The infrastructure incident at our cloud provider affecting availability zone europe-west2-b in the GCP europe-west2 (London) region has been resolved. Engineering has completed recovery of infrastructure running in the affected availability zone. Elastic Cloud Hosted: Customers whose plan changes or other operations failed during the incident are advised to retry them from the Elastic Cloud console. Some deployments may still be unavailable or degraded, and may need additional recovery steps that our Support team will work through case by case. If your deployment is still unhealthy, please contact Support.
Reported by Elastic Cloud on their status page.
resolvedOct 9 · 00:54 UTC
The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.
Reported by Elastic Cloud on their status page.
ResolvedOct 9 · 00:54 UTC
The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.
Reported by Elastic Cloud on their status page.
resolvedOct 6 · 17:54 UTC
The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.
Reported by Elastic Cloud on their status page.
ResolvedOct 6 · 17:54 UTC
The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.
Reported by Elastic Cloud on their status page.
resolvedSep 30 · 20:44 UTC
This issue was resolved in the 9.5.3 release of Elasticsearch. Customers running versions 9.5.0, 9.5.1, or 9.5.2 of Elasticsearch are advised to update to a newer version as soon as possible.
Reported by Elastic Cloud on their status page.
