What is Elastic Cloud's uptime?

Over the last 90 days, Elastic Cloud reported 99.78% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.elastic.co — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Elastic Cloud's uptime history rolling forward in real time.

Has Elastic Cloud had outages in 2026?

Yes — Elastic Cloud has had 27 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Elastic Cloud outage?

The most recent Elastic Cloud incident was "Metering issue with Elastic Cloud Hosted Deployments", which started on July 21, 2026 and was resolved on July 22, 2026. Pingoru captured this directly from https://status.elastic.co. See the full incident card above for affected components and the update timeline.

How often does Elastic Cloud have outages?

Based on the last 90 days, Elastic Cloud averages 9.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Elastic Cloud's status page?

Elastic Cloud's official status page is https://status.elastic.co. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Elastic Cloud down right now?

Elastic Cloud is down. Pingoru checks the official status page every 5 minutes and flips this headline the moment Elastic Cloud reports a change. Current status is based on 572 tracked services.

How does Pingoru know if Elastic Cloud is down?

We read https://status.elastic.co directly, using Elastic Cloud's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when Elastic Cloud has an outage?

Create a free Pingoru account and add Elastic Cloud as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Elastic Cloud's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real Elastic Cloud incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Elastic Cloud issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Elastic Cloud status?

We use Elastic Cloud's own status page at https://status.elastic.co and cross-reference their homepage (https://www.elastic.co/cloud). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Major Outage" mean?

Elastic Cloud is reporting a major outage. A significant portion of the service is unavailable.

Is Elastic Cloud down?

Last checked 1m ago

Current status

Elastic Cloud is down

Active incident: Connectivity disruption for AWS Bahrain (me-south-1)

Get alerts when Elastic Cloud breaks → View Elastic Cloud outage history →

Free · no credit card

Official status page: https://status.elastic.co · Polled every 5 minutes · 572 components tracked

Elastic Cloud is reporting a major outage right now (last checked 1m ago). 1 active incident on the official status page.

Real-time Elastic Cloud status, recent outages, and incident history — pulled directly from Elastic Cloud's official status page at https://status.elastic.co every 5 minutes. Pingoru tracks 572 Elastic Cloud services and has captured 28 incidents in the last 90 days (99.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Elastic Cloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor Elastic Cloud also follow these Database services:

SolarWinds Observability

Neo4j Aura

Upstash

Pinecone View all 6,000+ providers

Elastic Cloud uptime 99.78% uptime · past 90 days

Mon Wed Fri

MayJunJul

Less More

Active incident 1

Connectivity disruption for AWS Bahrain (me-south-1)

Ongoing ● 151d 22h

Started Mar 02, 2026, 06:23 AM UTC

AWS EC2 Health: me-south-1Snapshot Storage Infrastructure (S3): me-south-1Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1APM connectivity: AWS me-south-1AWS Infrastructure health: me-south-1Elasticsearch connectivity: AWS me-south-1Kibana connectivity: AWS me-south-1
Timeline · 13 updates
- identified · Mar 02, 2026, 06:23 AM UTC
  
  We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.
- identified · Mar 09, 2026, 03:01 PM UTC
  
  This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 16, 2026, 07:46 PM UTC
  
  This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 23, 2026, 04:20 PM UTC
  
  There are no new updates. This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Mar 24, 2026, 09:29 AM UTC
  
  We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.
- identified · Mar 24, 2026, 11:09 AM UTC
  
  This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].
- identified · Apr 02, 2026, 12:00 AM UTC
  
  As this incident remains ongoing with no recovery timeline provided by AWS, we have removed AWS Bahrain (me-south-1) from the available region selection on cloud.elastic.co. The region is currently unavailable for the creation of new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS connectivity disruption. Customers in this region should continue to work through Elastic support channels. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
- identified · Apr 20, 2026, 05:46 PM UTC
  
  Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unavailable for the foreseeable future. We continue to support impacted customers individually through our support channels. If you have not yet done so, please open a case so we can assist with your recovery options. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:[email protected]. Apr 20, 2026 — 00:00 UTC
- identified · May 18, 2026, 04:33 PM UTC
  
  Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
- identified · Jun 01, 2026, 05:13 PM UTC
  
  Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
- identified · Jun 15, 2026, 07:27 PM UTC
  
  Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:[email protected].
- identified · Jun 29, 2026, 05:14 PM UTC
  
  Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:mailto:[email protected].
- identified · Jul 13, 2026, 04:42 PM UTC
  
  Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].
Latest: Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infr…

Recent outages & incidents

Past 90 days

Metering issue with Elastic Cloud Hosted Deployments

Resolved 1d 8h

Started Jul 21, 2026, 02:24 PM UTC · Resolved Jul 22, 2026, 11:14 PM UTC
Timeline · 4 updates
- investigating · Jul 21, 2026, 02:24 PM UTC
  
  We have identified an issue with our metering of Instance Capacity for Hosted Deployments that affects a subset of customers. We currently believe the impact to be limited to a small number of customers but are still working to identify and correct all occurrences of this issue. We will proactively issue billing corrections where necessary.
- investigating · Jul 21, 2026, 11:15 PM UTC
  
  We are still investigating the metering issue impacting a small number of customers. We will proactively issue billing corrections where necessary. We'll provide another update when new information is available.
- investigating · Jul 22, 2026, 10:49 AM UTC
  
  We are still investigating the metering issue impacting a small number of customers. We'll provide a further update when new information is available.
- resolved · Jul 22, 2026, 11:14 PM UTC
  
  All metering errors have been corrected. We will be issuing refunds to the small number of affected customers.
Latest: All metering errors have been corrected. We will be issuing refunds to the small number of affected customers.
AutoOps monitoring data not ingested for subset of deployments

Resolved 35m

Started Jul 21, 2026, 01:45 PM UTC · Resolved Jul 21, 2026, 02:21 PM UTC

AutoOps
Timeline · 2 updates
- identified · Jul 21, 2026, 01:45 PM UTC
  
  RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe. Note this incident has already been resolved, and is being posted retroactively.
- resolved · Jul 21, 2026, 02:21 PM UTC
  
  This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Latest: This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Elastic Cloud - Email MFA Delivery Delays (Gmail)

Resolved 2d 7h

Started Jul 21, 2026, 09:36 AM UTC · Resolved Jul 23, 2026, 04:37 PM UTC
Timeline · 5 updates
- investigating · Jul 21, 2026, 09:36 AM UTC
  
  We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code. Available Workarounds: - Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn). - Authenticate using the "Log in with Google" social login button. Note: API Key access to your projects and deployments remains fully operational. We are actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
- investigating · Jul 21, 2026, 10:56 AM UTC
  
  Update: This incident is still ongoing and we are continuing to investigate. We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code. Available Workarounds: - Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn). - Authenticate using the "Log in with Google" social login button. Note: API Key access to your projects and deployments remains fully operational. We are actively collaborating with our partners to resolve this issue and will provide an update as soon as we can.
- investigating · Jul 21, 2026, 02:25 PM UTC
  
  Update: This incident is still ongoing and we are continuing to investigate.
- monitoring · Jul 21, 2026, 11:10 PM UTC
  
  Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
- resolved · Jul 23, 2026, 04:37 PM UTC
  
  Delivery delays have been resolved, MFA email delivery is fully functional for all customers.
Latest: Delivery delays have been resolved, MFA email delivery is fully functional for all customers.
AutoOps monitoring data not ingested for subset of deployments

Resolved 15m

Started Jul 18, 2026, 02:30 AM UTC · Resolved Jul 18, 2026, 02:45 AM UTC
Timeline · 1 update
- resolved · Jul 21, 2026, 12:10 PM UTC
  
  Resolved – This incident is resolved. Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.
Latest: Resolved – This incident is resolved. Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The und…
Cloud Console Deployment Errors

Resolved 56m

Started Jul 15, 2026, 12:15 AM UTC · Resolved Jul 15, 2026, 01:12 AM UTC

Cloud console
Timeline · 3 updates
- investigating · Jul 15, 2026, 12:15 AM UTC
  
  We are investigating errors with our cloud console affecting access to create, update, delete and view Elastic Cloud Hosted deployments. Our team is actively investigating the cause so that they can mitigate and restore the service.
- monitoring · Jul 15, 2026, 12:31 AM UTC
  
  The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
- resolved · Jul 15, 2026, 01:12 AM UTC
  
  This incident has been resolved
Latest: This incident has been resolved

See the full Elastic Cloud outage history

21 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Elastic Cloud outage history →

Or sign up free to get alerts when Elastic Cloud breaks · 10 free monitors · No credit card

Components (572)

AWS Bahrain (me-south-1)

Major Outage AWS EC2 Health: me-south-1

Major Outage Snapshot Storage Infrastructure (S3): me-south-1

Major Outage Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1

Major Outage APM connectivity: AWS me-south-1

Major Outage AWS Infrastructure health: me-south-1

Major Outage Elasticsearch connectivity: AWS me-south-1

Major Outage Kibana connectivity: AWS me-south-1

Azure - Washington (azure-westus2)

Degraded Azure Infrastructure Health

Azure Washington (azure-westus2)

Degraded Elasticsearch connectivity: Azure azure-westus2

Degraded Kibana connectivity: Azure azure-westus2

Degraded Azure Infrastructure health: azure-westus2

Degraded APM connectivity: Azure azure-westus2

Azure Ireland (azure-northeurope)

Up APM connectivity: Azure azure-northeurope

GCP São Paulo (southamerica-east1)

Up APM connectivity: GCP southamerica-east1

GCP South Carolina (us-east1)

Up APM connectivity: GCP us-east1

+557 more — sign up to monitor specific components

Outage history

Past 90 days · 25 incidents View full outage history →

Metering issue with Elastic Cloud Hosted Deployments Resolved

Started Jul 21, 2026, 02:24 PM UTC · Resolved Jul 22, 2026, 11:14 PM UTC · 1d 8h
AutoOps monitoring data not ingested for subset of deployments Resolved

Started Jul 21, 2026, 01:45 PM UTC · Resolved Jul 21, 2026, 02:21 PM UTC · 35m
Elastic Cloud - Email MFA Delivery Delays (Gmail) Resolved

Started Jul 21, 2026, 09:36 AM UTC · Resolved Jul 23, 2026, 04:37 PM UTC · 2d 7h
AutoOps monitoring data not ingested for subset of deployments Resolved

Started Jul 18, 2026, 02:30 AM UTC · Resolved Jul 18, 2026, 02:45 AM UTC · 15m
Cloud Console Deployment Errors Resolved

Started Jul 15, 2026, 12:15 AM UTC · Resolved Jul 15, 2026, 01:12 AM UTC · 56m
Elastic Cloud authentication issues using Microsoft login credentials Resolved

Started Jul 13, 2026, 12:15 PM UTC · Resolved Jul 13, 2026, 12:19 PM UTC · 3m
Regional outage - Elastic Inference Service (EIS) Resolved

Started Jul 02, 2026, 12:54 AM UTC · Resolved Jul 02, 2026, 03:00 AM UTC · 2h 5m
Partial outage - Elastic Inference Service (EIS) Resolved

Started Jul 01, 2026, 10:43 PM UTC · Resolved Jul 01, 2026, 11:05 PM UTC · 21m