Is Elastic Cloud Down?
Reachable from all 8 checked regions
Average response time: 193ms
Last checked · checks run every 6 hours
Official status page: https://status.elastic.co
Replication bug causing slow recoveries
Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible. Impacted customers are advised to follow the workaround steps from https://github.com/elastic/elasticsearch/issues/158212 after the upgrade.
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Elastic Cloud fail from enough regions to rule out probe noise.
Elastic Cloud uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 28 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
28-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Elastic Cloud does
Elastic Cloud is the managed version of Elasticsearch and Kibana, run by Elastic across AWS, Azure and Google Cloud in dozens of regions. Teams use it for application search, log and metrics analytics, and security monitoring. Because it often holds the very logs used to debug an incident, an Elastic outage tends to arrive at the least convenient moment.
What an outage looks like
Search queries time out or return partial results with shard failures. Kibana loads but its dashboards stay empty, or it cannot reach the cluster at all. Ingest backs up, so logs and metrics arrive late or stop arriving, leaving a visible gap in dashboards. Deployment changes such as scaling or upgrading stall in the console.
What to do about it
Check status.elastic.co, which reports each cloud provider and region separately alongside shared services such as the console, deployment orchestration and the Docker registry. Find your deployment's provider and region rather than reading the top of the page. Whether a gap in dashboards means data was lost depends on whether your shipper buffers, so check the agent before concluding either way.
Is it down for everyone, or just you?
If this page says Elastic Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Elastic Cloud outage FAQ
Is my deployment affected or just the console?
Did I lose logs during the outage?
Which region should I be watching?
Why are searches returning partial results instead of failing?
How we measure this
- We request Elastic Cloud's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Elastic Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Elastic Cloud goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring