Alert Pro — $9/mo

Never get caught off guard again

Get instant email alerts when Elasticsearch goes down. Know before your users do.

Free 14-day trial · Cancel anytime · Email alerts in <60 seconds

Or monitor your own infrastructure with Better Stack →

Elasticsearch Status Monitor

Elasticsearch Status: Is Elasticsearch Down Right Now?

Use this Elasticsearch status guide to confirm outages fast, troubleshoot cluster health, Kibana, indexing, or search issues, and get real-time monitoring for the moment Elasticsearch goes down.

Quick Elasticsearch Status Checklist

  • 1. Check official status updates.
  • 2. Query /_cluster/health API.
  • 3. Verify with independent monitoring.
  • 4. Check disk space and node status.
Looking for live data? Visit /api/elasticsearch.

Check the official Elastic Cloud status page

Elastic maintains a status page for Elastic Cloud covering Elasticsearch, Kibana, and APM service health across regions.

status.elastic.co

Query cluster health directly

Run a GET request to your cluster health endpoint: `GET /_cluster/health`. A red or yellow status indicates a cluster-level issue.

Cluster health API docs

Verify with independent monitoring

Use API Status Check for third-party monitoring that verifies real endpoints and tracks historical incidents.

Elasticsearch on API Status Check

Common Elasticsearch Issues During Outages

Cluster in red or yellow health state

A red cluster has unassigned primary shards and cannot serve search requests. Yellow means replica shards are unassigned but primary shards are active.

Kibana not loading or timing out

Kibana depends on Elasticsearch and may fail to load dashboards, run queries, or display data when the underlying cluster is unhealthy.

Indexing failures and document write errors

Document indexing may fail with 429 (circuit breaker) or 503 errors when the cluster is under disk pressure or experiencing node failures.

Search queries timing out

Search requests may time out or return partial results during cluster degradation, especially if nodes are failing over.

Troubleshooting Steps Before You Assume Elasticsearch Is Down

  1. 1

    Check cluster health API

    Run `GET /_cluster/health?pretty` to see the overall cluster status, number of nodes, and shard assignments.

  2. 2

    Check node status

    Run `GET /_cat/nodes?v` to list all nodes and identify any that are missing or have high JVM heap usage.

  3. 3

    Review shard allocation

    Run `GET /_cat/shards?h=index,shard,prirep,state,unassigned.reason` to find unassigned shards and their reason codes.

  4. 4

    Check disk space and watermarks

    Elasticsearch throttles or stops indexing when disk usage exceeds watermark thresholds. Check disk space on all data nodes.

  5. 5

    Review Elasticsearch logs

    Check Elasticsearch logs for OOM errors, GC pressure warnings, or network timeout messages that indicate node-level issues.

Real-Time Elasticsearch Monitoring

API Status Check tracks Elasticsearch status with independent monitoring, uptime stats, and incident history so you can confirm outages quickly.

  • Independent Elasticsearch status checks

    API Status Check performs independent monitoring so you can verify Elasticsearch status even if official updates are delayed.

  • Incident history and uptime data

    Review recent incidents, response times, and reliability trends to understand Elasticsearch cluster stability.

  • Real-time alerts and integrations

    Get notified with email alerts, RSS feeds, and webhooks when Elasticsearch experiences a new incident.

Alternative Solutions During Elasticsearch Outages

Serve from replica shards

If primary shards are down, Elasticsearch can still serve reads from replica shards. Ensure replicas are allocated across healthy nodes.

Enable circuit breakers

Configure Elasticsearch circuit breakers to prevent OOM conditions that lead to node failures during high indexing loads.

Use OpenSearch as a fallback

For critical search workloads, OpenSearch is an Elasticsearch-compatible alternative you can configure as a failover target.

Monitor recovery via API Status Check

Set up alerts to get notified the moment your Elasticsearch service recovers from an outage.

Get notified when Elasticsearch is back up

No account needed. We will email you once and thats it.

Elasticsearch Status FAQ

Is Elasticsearch down right now?

Check status.elastic.co for Elastic Cloud status and API Status Check for independent monitoring. For self-managed clusters, query the cluster health API directly.

What does a red Elasticsearch cluster mean?

A red cluster has unassigned primary shards, meaning some data is unavailable. Identify unassigned shards with the cat shards API and investigate the allocation failure reason.

Why is Kibana not loading?

Kibana connectivity depends on Elasticsearch. If Kibana cannot connect, check if Elasticsearch is running and the cluster is healthy before troubleshooting Kibana itself.

Why are Elasticsearch indexing requests failing?

Indexing failures often indicate disk watermark limits, circuit breaker trips, or node failures. Check disk space and run the cluster allocation explain API to diagnose.

Does Elastic Cloud status affect self-managed Elasticsearch?

No. Self-managed Elasticsearch clusters are independent of Elastic Cloud infrastructure. Only Elastic Cloud users are affected by Elastic Cloud outages.

How can I get Elasticsearch outage alerts?

Subscribe to alerts on API Status Check to receive real-time notifications when Elasticsearch experiences an incident.