Skip to content
Back to Elastic CloudIncident Postmortem
Elastic Cloud logo

Elastic Cloud

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Elastic Cloud: vendor-reported major incident on September 24 (tracked 2d 0h)

Sep 24, 04:48 PM → Sep 26, 05:18 PM · 2d 0h · high

Elastic Cloud reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 2d 0h, from Thu, 24 Sep 2026 16:48:48 GMT to Sat, 26 Sep 2026 17:18:31 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2d 0h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 24, 04:48 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 24, 04:48 PM

    Status updated: possible issue

  3. Sep 26, 05:18 PM

    PulseWatch closed the incident

Official updates

  1. Sep 24, 04:48 PM

    Elastic Cloud reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback