Skip to service list
IU

Is Elastic down?

Elastic status · Developer Tools · checked (8s ago)

Also searched as Elasticsearch, Elastic Cloud, Kibana.

Degraded

Partly — Elastic is up but running slower than usual (Partial System Outage).

According to Elastic's official status page, Elastic was reporting “Partial System Outage” when isuptime last checked at . Over the last 30 days, Elastic's feed reported no outage in 99.92% of our checks.

No outage reported (30d)
99.92%
Share of our checks where Elastic's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
326 ms
How long the last status check took
Reported by
Degraded
Partial System Outage

What to do while Elastic is down

isuptime cannot fix Elastic, and neither can you. These are the things that are actually worth doing until it comes back.

  1. Read what Elastic has actually published. Their incident notes say which components are affected and usually carry an estimate, which is more than any third party can tell you. Elastic's status page
  2. Stop retrying in a loop. If your code calls Elastic, back off exponentially and cap the retries. A retry storm from every client at once is a large part of why outages take as long to clear as they do, and it will exhaust your own quota before the service returns.
  3. Get told when it clears, instead of refreshing. The bell in the header sets up a browser notification, or a Discord, Slack or Telegram webhook, for the moment Elastic's status changes.

Is Elastic down for you right now?

Everything above is read from Elastic's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.

Nobody has reported Elastic in the last 24 hours. Yours would be the first.

Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.

What Elastic is

Elastic runs Elasticsearch, Kibana, Logstash and Beats, and hosts them as Elastic Cloud across AWS, Google Cloud and Azure — search, log analytics, observability and security workloads.

What Elastic's status feed covers

Elastic's status page is one of the most finely subdivided anywhere: it lists every combination of product, cloud provider and region as its own component, which runs into the hundreds. That granularity distorts the aggregate indicator badly — a problem in a single AWS region can leave the headline reading “Partial System Outage” for weeks while the overwhelming majority of components are healthy. isuptime weighs the indicator against the share of components actually affected rather than repeating the headline, which is why Elastic often reads as operational here while its own page shows amber.

isuptime reads this feed on a schedule and reports what it says — how that works, in detail.

Elastic uptime, last 30 days

One bar per day. Each shows the share of that day's checks where Elastic's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Elastic was down.

2026-10-1012 of 30 days recorded · lowest day 99.31%Today
  • No outage reported (99%+)
  • 95–99%
  • 80–95%
  • Under 80%
  • No data

Other services reporting problems right now

9 other services isuptime tracks were also reporting a problem as of the same check, 8s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.

1 more service is reporting problems — see all →

Elastic response time trend

Each point is one check of Elastic's status endpoint.

Which Elastic features are affected?

Elastic outage history

Elastic has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Elastic posted itself — not every problem users hit.

Elastic status — frequently asked

Is Elastic down right now?
Partly — Elastic is up but running slower than usual (Partial System Outage). Checked (8s ago).
What is Elastic's status right now?
Elastic is reporting “Partial System Outage” on its official status page — Degraded — as of . That status feed answered our last check in 326 ms. isuptime reads this from Elastic's own published feed and does not test Elastic independently.
When did Elastic last go down?
The most recent incident Elastic published was “mOLTP PrivateLink connectivity issue”, opened Nov 4, 12:08 PM UTC (4d ago) and marked resolved Nov 5, 01:36 AM UTC. That is the latest entry in Elastic's own incident feed, not every problem users experienced.
What is Elastic's uptime?
isuptime does not measure Elastic's uptime directly — it reads Elastic's own published status feed. Over the last 30 days, Elastic's own status feed reported no outage in 99.92% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Elastic down for everyone?
Elastic is reporting a problem on its own status page, so this is affecting other users too, not just you.

Elastic says operational but it is not working for me

Check which cloud provider and region your deployment is actually in, since that is the level at which Elastic incidents happen. A cluster in yellow or red health is a shard allocation problem in your own deployment, not an Elastic Cloud outage. Hitting the disk watermark puts indices into read-only mode, which presents as writes mysteriously failing.

Open Elastic's official status page

Other Developer Tools services

← See live status for all 102 services