Elasticsearch Status: How to Check If Elasticsearch Is Down (2026)
Updated June 2026 · 8 min read · API Status Check
Quick Answer
Check Elasticsearch / Elastic Cloud status at status.elastic.co (official) or apistatuscheck.com/is-elasticsearch-down for independent real-time monitoring.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official Elastic Status Page
Elastic maintains an official status page at status.elastic.co. This page shows real-time status for all Elastic Cloud services and components:
What Each Elastic Cloud Status Means
Monitor Elasticsearch status automatically
Better Stack watches your Elasticsearch endpoints every 30 seconds and pages your team the moment a cluster goes down. Works for both Elastic Cloud and self-hosted deployments.
Try Better Stack Free →Elastic Cloud Regions: AWS, GCP, Azure — Know Your Region
Elastic Cloud runs on AWS, Google Cloud, and Azure across multiple regions. Outages are often region-specific. Your deployment URL tells you which region you're on:
AWS Regions (e.g., us-east-1, eu-west-1)
What it is: Most Elastic Cloud customers use AWS. Region is visible in your cloud.elastic.co deployment URL or dashboard.
Signs of issues: Cluster API returning 503, indexing requests timing out, Kibana refusing to load.
Workaround: Check status.elastic.co for your specific AWS region. If affected, reduce write throughput and queue non-critical indexing work.
Google Cloud Regions (e.g., us-central1, europe-west1)
What it is: GCP-hosted deployments are isolated from AWS issues. Some customers choose GCP for cost or compliance reasons.
Signs of issues: Same symptoms as AWS but only for GCP-region customers.
Workaround: Check status.elastic.co for GCP region status. GCP and AWS incidents are usually independent.
Azure Regions (e.g., eastus, westeurope)
What it is: Azure-hosted Elastic Cloud for enterprise customers using Azure as their primary cloud.
Signs of issues: Connectivity failures from Azure-native apps to Elastic Cloud clusters.
Workaround: Check both status.elastic.co and Azure Service Health — Azure infrastructure incidents can cascade to Elastic Cloud.
5 Ways to Check Elasticsearch Status Right Now
Official Elastic Status Page
Visit status.elastic.co for real-time component and region status. Subscribe to email or webhook notifications for incident updates and post-mortems.
status.elastic.co →API Status Check (Independent Monitor)
APIStatusCheck independently monitors Elasticsearch endpoints and shows unbiased uptime data — separate from Elastic's own reporting.
Check live Elasticsearch status →Cluster Health API
For self-hosted or Elastic Cloud: run GET /_cluster/health on your cluster. Returns green/yellow/red. Yellow means replica shards unassigned; red means primary shards missing.
X/Twitter Search
Search 'Elasticsearch down' or 'Elastic Cloud outage' on X. DevOps teams report problems immediately — often faster than the official status page.
Search X for 'elasticsearch down' →Elastic Community Slack / Forums
The Elastic community forum at discuss.elastic.co is active during incidents. The community Slack #elastic-cloud channel has real-time reports from other users.
Elastic Community Forums →What To Do When Elasticsearch Is Down
Confirm it's Elastic Cloud, not your cluster config
Run GET /_cluster/health. A red status can be caused by your own shard configuration, not Elastic Cloud infrastructure. Also check your API key permissions and network security groups before assuming an outage.
Switch to read-only mode if possible
During Elasticsearch write outages, route your application to a read cache or stale data rather than failing hard. Many search use cases can tolerate serving slightly stale results while indexing is paused.
Queue writes for replay
Buffer indexing operations in Kafka, SQS, or a local queue. Elasticsearch supports bulk indexing, so queued documents can be replayed quickly once the cluster recovers without data loss.
Check cross-cluster replication
If you have cross-cluster replication (CCR) configured, your replica cluster may still be serving search traffic. Fail over DNS or load balancer targets to the healthy cluster.
Monitor Elastic's incident updates
Follow the incident on status.elastic.co. Elastic posts updates every 30–60 minutes during active incidents. Most Elastic Cloud outages resolve within 1–2 hours.
Set up Elasticsearch uptime monitoring
Better Stack monitors your Elasticsearch cluster health endpoint and alerts you within seconds of a degradation — before your users notice missing search results.
Try Better Stack Free →Elasticsearch Cluster Health: Green, Yellow, Red
Self-hosted Elasticsearch uses a three-color cluster health model distinct from Elastic Cloud status. Understanding the difference is critical for accurate diagnosis:
Frequently Asked Questions
Where is the official Elasticsearch status page?
Elastic's official status page is at status.elastic.co. It covers Elastic Cloud services and components. For self-hosted Elasticsearch, you monitor your own cluster health — use GET /_cluster/health on your cluster.
Why is Elasticsearch not working but the status page shows operational?
Status pages can lag 10–20 minutes behind real incidents. Check apistatuscheck.com/is-elasticsearch-down for independent monitoring. Also run GET /_cluster/health on your cluster and check your network security groups — connection issues are often infrastructure, not Elastic Cloud.
Does an Elastic Cloud outage affect self-hosted Elasticsearch?
No. Self-hosted Elasticsearch is fully independent of Elastic Cloud. If you run your own cluster, outages are caused by your hardware, network, or configuration — not Elastic.
What does Elasticsearch cluster status "yellow" mean?
Yellow means all primary shards are active (your data is queryable) but replica shards are unassigned. Queries work normally — you just lack redundancy. Common on single-node development clusters. Not an emergency, but fix replica assignment before going to production.
How do I get alerts when Elasticsearch goes down?
Subscribe to status.elastic.co notifications, follow @elastic on X, or use API Status Check Alert Pro. For your own clusters, use Kibana Watcher, Better Stack, or Prometheus Alertmanager to monitor cluster health.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Elasticsearch goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Elasticsearch + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
🛠 Tools We Use & Recommend
Tested across our own infrastructure monitoring 200+ APIs daily
Uptime Monitoring & Incident Management
Used by 100,000+ websites
Monitors your APIs every 30 seconds. Instant alerts via Slack, email, SMS, and phone calls when something goes down.
“We use Better Stack to monitor every API on this site. It caught 23 outages last month before users reported them.”
Secrets Management & Developer Security
Trusted by 150,000+ businesses
Manage API keys, database passwords, and service tokens with CLI integration and automatic rotation.
“After covering dozens of outages caused by leaked credentials, we recommend every team use a secrets manager.”
Automated Personal Data Removal
Removes data from 350+ brokers
Removes your personal data from 350+ data broker sites. Protects against phishing and social engineering attacks.
“Service outages sometimes involve data breaches. Optery keeps your personal info off the sites attackers use first.”
AI Voice & Audio Generation
Used by 1M+ developers
Text-to-speech, voice cloning, and audio AI for developers. Build voice features into your apps with a simple API.
“The best AI voice API we've tested — natural-sounding speech with low latency. Essential for any app adding voice features.”
SEO & Site Performance Monitoring
Used by 10M+ marketers
Track your site health, uptime, search rankings, and competitor movements from one dashboard.
“We use SEMrush to track how our API status pages rank and catch site health issues early.”