Skip to content
PulseWatchOUTAGE.INTEL
Elastic logo

Other

Is Elastic down right now?

UnknownOfficial status last polled Sep 20, 2026 16:44 UTCwww.elastic.coOfficial status page

The company behind the ELK Stack, providing search-powered solutions for observability, logging, and security analytics.

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

Is Elastic down right now?

Vendor-reported issue. Elastic: Replication bug causing slow recoveries Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 20, 2026 16:45 UTC

UnknownVendor-reported issue

Elastic: vendor reports an issue

As of Sep 20, 2026 16:45 UTC

Replication bug causing slow recoveries 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

0

Last incident

Sep 17, 2026 17:42 UTC

Trend

0/15m

Monitoring

Coverage gap

Product checks

Coverage gap: no product check is qualified to corroborate an incident for this service. Homepage and gateway checks do not verify the affected workflow.

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.

Monitoring coverage

0/0 configured operation checks fresh

0 operation checks qualified for evidence · 0 measurement origins.

Other operations and customer regions remain unverified.

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 Elastic.

15

Incident days

15

No recorded incident

288h 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 Elastic. Hover a day for detail.

Aug 22Aug 27Sep 1Sep 6Sep 11Sep 1601234

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

15

Days with incidents

2 incidents

Busiest day

288h 14m

Recorded duration

Report volume

0 reports in last 24H

04:45 PM08:15 PM11:45 PM03:15 AM06:45 AM10:15 AM01:45 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Elastic outage on August 14 — 1h 12m disruption

Aug 14, 06:33 AM → Aug 14, 07:46 AM · 1h 12m · critical

An outage affecting Elastic services was detected on August 14, 2026, initially identified through user reports. The incident, which began at 06:33 UTC, resulted in a period of service disruption. Our teams worked to address the issue, and the service was fully restored at 07:46 UTC.

Peak reports
8
in 15 min
Total reports
32
during outage
Duration
1h 12m
until recovery

Impact

The outage primarily manifested as users reporting that the 'Website was down,' as indicated by the top issue type. This disruption was first identified through user reports, with a total of 32 reports received during the incident's duration. While the incident was critical, no specific regions were predominantly impacted according to the available data. The service disruption lasted for approximately 1 hour and 12 minutes.

Top reported issues

  • Website down32

Outage timeline

  1. Aug 14, 06:33 AM

    PulseWatch detected elevated report volume (critical severity)

  2. Aug 14, 06:33 AM

    Status updated: major issue

  3. Aug 14, 06:36 AM

    Status updated: major issue

  4. Aug 14, 06:41 AM

    Status updated: major issue

  5. Aug 14, 06:45 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  6. Aug 14, 06:48 AM

    Status updated: major issue

  7. Aug 14, 06:51 AM

    Status updated: major issue

  8. Aug 14, 06:56 AM

    Status updated: major issue

  9. Aug 14, 07:03 AM

    Status updated: major issue

  10. Aug 14, 07:06 AM

    Status updated: major issue

  11. Aug 14, 07:12 AM

    Status updated: major issue

  12. Aug 14, 07:18 AM

    Status updated: major issue

  13. Aug 14, 07:21 AM

    Status updated: major issue

  14. Aug 14, 07:26 AM

    Status updated: major issue

  15. Aug 14, 07:33 AM

    Status updated: major issue

  16. Aug 14, 07:36 AM

    Status updated: major issue

  17. Aug 14, 07:41 AM

    Status updated: major issue

  18. Aug 14, 07:46 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. Aug 14, 06:33 AM

    Elastic status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

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

Other other services we monitor

Browse all

Community reports

0 comments

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

500 characters left

Be the first to post a report.

Incident timeline

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

Full history →
ResolvedHigh

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

9/17/2026, 4:31:24 PM · 1h 11m

04:31 PM05:42 PM
Detection9/17/2026, 4:31:24 PM · 3d ago

Detected — high severity

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

ResolvedHigh

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

9/16/2026, 1:42:58 PM · 21h 59m

01:42 PM11:42 AM
Detection9/16/2026, 1:42:58 PM · 4d ago

Detected — high severity

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

ResolvedHigh

Elastic: 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/14/2026, 3:01:24 PM · 1d 17h

03:01 PM08:42 AM
Detection9/14/2026, 3:01:24 PM · 6d ago

Detected — high severity

Elastic: 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

Elastic: 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:06:03 AM · 1d 11h

03:06 AM02:57 PM
Detection9/13/2026, 3:06:03 AM · 7d ago

Detected — high severity

Elastic: 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

Elastic: 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:27:38 AM · 18h 35m

08:27 AM03:02 AM
Detection9/12/2026, 8:27:38 AM · 8d ago

Detected — high severity

Elastic: 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.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

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

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

Signal quality

Live signal

Status
Unknown
Monitoring
Vendor-reported issue: Replication bug causing slow recoveries. 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