Skip to content
PulseWatchOUTAGE.INTEL
Elastic Observability logo

Other

Is Elastic Observability down right now?

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

A search-powered observability solution for logs, metrics, and traces.

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

Is Elastic Observability down right now?

Vendor-reported issue. Elastic Observability: 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:21 UTC

UnknownVendor-reported issue

Elastic Observability: vendor reports an issue

As of Sep 28, 2026 10:21 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.

Product-check coverage is unavailable. Overall service status has not been established.

Reports 24h

0

Last incident

Sep 24, 2026 16:51 UTC

Trend

0/15m

Monitoring

Coverage unavailable

Observed health

Unavailable

Current measurements are not available for a health 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 Elastic Observability.

11

Incident days

19

No recorded incident

158h 41m

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 Observability. Hover a day for detail.

Aug 30Sep 4Sep 9Sep 14Sep 19Sep 2401234

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

11

Days with incidents

2 incidents

Busiest day

158h 41m

Recorded duration

Report volume

0 reports in last 24H

10:15 AM01:45 PM05:15 PM08:45 PM12:15 AM03:45 AM07:15 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Elastic Observability outage on September 21 — 3-day disruption

Sep 21, 04:50 PM → Sep 24, 04:51 PM · 3d 0h · high

A high-severity incident affecting Elastic Observability was detected by automated monitoring systems. The disruption began on September 21, 2026, at 16:50 UTC, and was resolved on September 24, 2026, at 16:51 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
3d 0h
until recovery

Impact

This incident involved a high-severity disruption to Elastic Observability for a duration of approximately three days. During this period, the service experienced impaired functionality. No user-reported data was collected for this incident, as it was detected through automated monitoring and vendor status page updates.

Outage timeline

  1. Sep 21, 04:50 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 21, 04:50 PM

    Status updated: possible issue

  3. Sep 24, 04:51 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 21, 04:50 PM

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

9/21/2026, 4:50:42 PM · 3d 0h

04:50 PM04:51 PM
Detection9/21/2026, 4:50:42 PM · 6d ago

Detected — high severity

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

ResolvedHigh

Elastic Observability: 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/17/2026, 4:31:51 PM · 1h 8m

04:31 PM05:40 PM
Detection9/17/2026, 4:31:51 PM · 10d ago

Detected — high severity

Elastic Observability: 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 Observability: 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, 4:40:47 AM · 4h 0m

04:40 AM08:40 AM
Detection9/13/2026, 4:40:47 AM · 15d ago

Detected — high severity

Elastic Observability: 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 Observability: 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, 11:42:33 PM · 4h 48m

11:42 PM04:31 AM
Detection9/12/2026, 11:42:33 PM · 15d ago

Detected — high severity

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

Elastic Observability incident correlated across 1 signal group: official/vendor.

8/29/2026, 4:48:44 AM · 3d 23h

04:48 AM04:43 AM
Detection8/29/2026, 4:48:44 AM · 1mo ago

Detected — medium severity

Elastic Observability incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Elastic Observability 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: 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/observability