What is Elastic.io's uptime?

Over the last 90 days, Elastic.io 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.io's uptime history rolling forward in real time.

Has Elastic.io had outages in 2026?

Yes — Elastic.io has had 28 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.io outage?

The most recent Elastic.io incident was "Elevated Error Rates Affecting Managed OTLP", which started on August 20, 2026 and was resolved on August 20, 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.io have outages?

Based on the last 90 days, Elastic.io averages 9.3 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.io's status page?

Elastic.io'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.io down right now?

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

How does Pingoru know if Elastic.io is down?

We read https://status.elastic.co directly, using Elastic.io'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.io has an outage?

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

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

Three common reasons: • A real Elastic.io 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.io 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.io status?

We use Elastic.io's own status page at https://status.elastic.co and cross-reference their homepage (https://www.elastic.io). 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.io is reporting a major outage. A significant portion of the service is unavailable.

Is Elastic.io down?

Last checked 7m ago

Current status

Elastic.io is down

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

Get alerts when Elastic.io breaks → View Elastic.io outage history →

Free · no credit card

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

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

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

Users who monitor Elastic.io also follow these Cloud Infrastructure services:

Genesys Cloud View all 6,000+ providers

Elastic.io uptime 99.78% uptime · past 90 days

Mon Wed Fri

MayJunJulAug

Less More

Active incident 1

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

Ongoing ● 177d 13h

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 · 14 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].
- identified · Aug 10, 2026, 04:46 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

Elevated Error Rates Affecting Managed OTLP

Resolved 1h 50m

Started Aug 20, 2026, 08:22 PM UTC · Resolved Aug 20, 2026, 10:13 PM UTC
Timeline · 4 updates
- investigating · Aug 20, 2026, 08:22 PM UTC
  
  We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. Our team is actively investigating the root cause. We will provide an update within 30 minutes.
- investigating · Aug 20, 2026, 08:53 PM UTC
  
  We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless. We will provide an update within 1 hour.
- identified · Aug 20, 2026, 09:59 PM UTC
  
  We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline. Based on our investigation, customer workloads were not affected.
- resolved · Aug 20, 2026, 10:13 PM UTC
  
  This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.
Latest: This incident has been resolved. The root cause has been identified and addressed. Customer workloads were not impacted during this incident.
Issue when creating Serverless projects in Azure eastus region

Resolved 3h 34m

Started Aug 20, 2026, 12:48 PM UTC · Resolved Aug 20, 2026, 04:22 PM UTC

Elastic Cloud Serverless
Timeline · 3 updates
- investigating · Aug 20, 2026, 12:48 PM UTC
  
  An issue affecting the creation of new Serverless projects in Azure's eastus region has been identified. Our team is actively investigating to determine the root cause. We will provide a follow-up status update within the next hour or as soon as the root cause is established, whichever occurs first.
- monitoring · Aug 20, 2026, 02:05 PM UTC
  
  We have determined that the issue stems from an upstream problem with Azure's storage component. Upon examination, the impact is limited strictly to new project initialization times, resulting in longer creation times for Serverless projects in the Azure eastus region. We will provide a further update once the issue has been resolved.
- resolved · Aug 20, 2026, 04:22 PM UTC
  
  Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected.
Latest: Azure's storage component issues in the eastus region have been resolved. Consequently, Serverless project creation times have returned to normal and are functioning as expected.
Elasticsearch 9.5.1: false-positive matches in certain boolean queries

Resolved 6d 7h

Started Aug 14, 2026, 09:22 AM UTC · Resolved Aug 20, 2026, 05:09 PM UTC
Timeline · 2 updates
- identified · Aug 14, 2026, 09:22 AM UTC
  
  Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-value terms queries utilize a different Lucene query type that was not covered by that fix. Time Series Data Streams (TSDB) and columnar indices/data streams remain affected for this query pattern, as indexing is disabled by default on those fields. Affected terms queries may return false-positive matches (including documents that should have been excluded) and report higher document counts than expected. No error is raised, so queries will appear to complete successfully. What you can do: - If you have not yet upgraded to 9.5.*, we recommend deferring the upgrade until version 9.5.2 is available. - If you are already running 9.5.*, contact Elastic Support if you need help determining whether your searches are affected. We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update when the fix is ready.
- resolved · Aug 20, 2026, 05:09 PM UTC
  
  Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue resolved and will be providing no further updates.
Latest: Elasticsearch 9.5.2 has been released and contains the fix for this issue. Customers running 9.5.0 or 9.5.1 should upgrade to 9.5.2. At this time we are considering this issue reso…
Increased error rates for microsoft-multilingual-e5-large

Resolved 4d 3h

Started Aug 13, 2026, 08:32 AM UTC · Resolved Aug 17, 2026, 11:40 AM UTC
Timeline · 4 updates
- investigating · Aug 13, 2026, 08:32 AM UTC
  
  We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating
- investigating · Aug 13, 2026, 02:45 PM UTC
  
  We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
- monitoring · Aug 13, 2026, 06:26 PM UTC
  
  Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.
- resolved · Aug 17, 2026, 11:40 AM UTC
  
  The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference
Latest: The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with…
Serverless project creation delayed or failing

Resolved 4h 42m

Started Aug 13, 2026, 03:57 AM UTC · Resolved Aug 13, 2026, 08:40 AM UTC

Elastic Cloud Serverless
Timeline · 4 updates
- investigating · Aug 13, 2026, 03:57 AM UTC
  
  We are investigating failures with Serverless project creation.
- investigating · Aug 13, 2026, 05:28 AM UTC
  
  We're currently investigating an issue affecting Serverless project creation and modifications. You may experience delays or failures when creating new projects or updating existing project settings. What's affected: - Creating new Serverless projects - Modifying project settings in the Cloud UI or over the API What's not affected: - Running Serverless projects continue to operate normally - Existing project workloads are unimpacted We'll provide an update within 2 hours, or sooner if the situation changes.
- monitoring · Aug 13, 2026, 06:04 AM UTC
  
  We've identified and resolved the issue affecting Serverless project creation and modifications. Our fix has been deployed, and all services are operating normally. Current status: - Creating and modifying Serverless projects is fully operational - All systems are performing as expected We're continuing to monitor closely for any recurrence.
- resolved · Aug 13, 2026, 08:40 AM UTC
  
  We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.
Latest: We've resolved the issue affecting Serverless project creation and modifications. All systems are now operating normally.

See the full Elastic.io outage history

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

Browse Elastic.io outage history →

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

Components (571)

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

GCP Mumbai (asia-south1)

Degraded Elasticsearch connectivity: GCP asia-south1

Azure Ireland (azure-northeurope)

Up APM connectivity: Azure azure-northeurope

GCP São Paulo (southamerica-east1)

Up APM connectivity: GCP southamerica-east1

+556 more — sign up to monitor specific components

Outage history

Past 90 days · 26 incidents View full outage history →

Elevated Error Rates Affecting Managed OTLP Resolved

Started Aug 20, 2026, 08:22 PM UTC · Resolved Aug 20, 2026, 10:13 PM UTC · 1h 50m
Issue when creating Serverless projects in Azure eastus region Resolved

Started Aug 20, 2026, 12:48 PM UTC · Resolved Aug 20, 2026, 04:22 PM UTC · 3h 34m
Elasticsearch 9.5.1: false-positive matches in certain boolean queries Resolved

Started Aug 14, 2026, 09:22 AM UTC · Resolved Aug 20, 2026, 05:09 PM UTC · 6d 7h
Increased error rates for microsoft-multilingual-e5-large Resolved

Started Aug 13, 2026, 08:32 AM UTC · Resolved Aug 17, 2026, 11:40 AM UTC · 4d 3h
Serverless project creation delayed or failing Resolved

Started Aug 13, 2026, 03:57 AM UTC · Resolved Aug 13, 2026, 08:40 AM UTC · 4h 42m
GCP asia-south1 high latency Resolved

Started Aug 06, 2026, 05:41 PM UTC · Resolved Aug 06, 2026, 05:41 PM UTC · —
Elasticsearch 9.5.0 contains a query-correctness defect Resolved

Started Aug 05, 2026, 10:59 PM UTC · Resolved Aug 12, 2026, 08:59 AM UTC · 6d 10h
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