PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Elasticsearch is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Elasticsearch. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Elasticsearch issues today?

As of Sep 28, 2026 10:26 UTC, 0 users had reported issues with Elasticsearch in the previous 24 hours.

How can I report a Elasticsearch outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Elasticsearch down right now?

UnknownOfficial status last polled Sep 28, 2026 09:23 UTCwww.elastic.co Official status page

Distributed search and analytics engine for enterprise data.

Are you on the Elasticsearch team and see something inaccurate? Report it to us. We respond within one business day.

Is Elasticsearch down right now?

Vendor-reported issue. Elasticsearch: Connectivity disruption for AWS Bahrain (me-south-1) Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:26 UTC

UnknownVendor-reported issue

Elasticsearch: vendor reports an issue

As of Sep 28, 2026 10:26 UTC

Connectivity disruption for AWS Bahrain (me-south-1) Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Sep 24, 2026 15:32 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Elasticsearch.

Incident days

No recorded incident

201h 14m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Elasticsearch. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

201h 14m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Elasticsearch outage on September 21 3-day disruption

Sep 21, 03:27 PM → Sep 24, 03:32 PM · 3d 0h · high

A high severity incident affecting the Elasticsearch service was detected on September 21, 2026. This incident lasted approximately 3 days and was resolved on September 24, 2026.

Peak reports

in 15 min

Total reports

during outage

Duration

3d 0h

until recovery

Impact

During the 3-day high severity incident, the Elasticsearch service experienced disruption. This incident was detected through automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported issues, affected regions, or issue types were recorded.

Outage timeline

Sep 21, 03:27 PM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 21, 03:27 PM
Status updated: possible issue
Sep 24, 03:32 PM
Signals cleared — incident resolved

Official updates

Sep 21, 03:27 PM
Elasticsearch status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Elasticsearch is unknown, so there is no incident history to measure and no uptime figure is shown.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Elasticsearch: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Elasticsearch or have an alert rule on it can be alerted, labelled vendor-reported.

9/21/2026, 3:27:43 PM · 3d 0h

03:27 PM03:32 PM

Detection9/21/2026, 3:27:43 PM · 6d ago

Detected — high severity

ResolvedHigh

Elasticsearch: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/13/2026, 3:10:53 AM · 1d 17h

03:10 AM08:42 PM

Detection9/13/2026, 3:10:53 AM · 15d ago

Detected — high severity

Elasticsearch: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedHigh

Elasticsearch: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/12/2026, 8:32:38 AM · 10h 44m

08:32 AM07:17 PM

Detection9/12/2026, 8:32:38 AM · 16d ago

Detected — high severity

Elasticsearch: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

Elasticsearch incident correlated across 1 signal group: official/vendor.

8/29/2026, 5:48:46 AM · 3d 23h

05:48 AM04:52 AM

Detection8/29/2026, 5:48:46 AM · 1mo ago

Detected — medium severity

Elasticsearch incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Elasticsearch incident correlated across 1 signal group: official/vendor.

8/15/2026, 5:13:38 PM · 9d 9h

05:13 PM02:41 AM

Detection8/15/2026, 5:13:38 PM · 1mo ago

Detected — medium severity

Elasticsearch incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Elasticsearch enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Unknown
Monitoring: Vendor-reported issue: Connectivity disruption for AWS Bahrain (me-south-1). Affected scope is described in the vendor notice; service-wide impact is not established.
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

www.elastic.co

Related services

AWS Amplify Hosting

Cloud Infrastructure

Unknown

AWS App Runner

Cloud Infrastructure

Unknown

AWS Lambda

Cloud Infrastructure

Unknown