What is Elastic.io's uptime?

Over the last 90 days, Elastic.io reported 99.87% 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 25 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 "Delayed or Unavailable project operation in GCP us-central1", which started on October 8, 2026 and was resolved on October 9, 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 8.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 548 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 just now

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 · 548 components tracked

Elastic.io is reporting a major outage right now (last checked just now). 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 548 Elastic.io services and has captured 26 incidents in the last 90 days (99.87% uptime). Get email, Slack, Discord, or webhook alerts the moment Elastic.io reports a new incident — free for 3 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.87% uptime · past 90 days

Mon Wed Fri

JulAugSepOct

Less More

Active incident 1

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

Ongoing ● 223d 9h

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 · 15 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].
- identified · Sep 21, 2026, 03:21 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

Delayed or Unavailable project operation in GCP us-central1

Resolved 8h 11m

Started Oct 08, 2026, 04:42 PM UTC · Resolved Oct 09, 2026, 12:54 AM UTC

GCP Infrastructure health: us-central1
Timeline · 5 updates
- investigating · Oct 08, 2026, 04:42 PM UTC
  
  We are investigating an issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operation.
- identified · Oct 08, 2026, 05:21 PM UTC
  
  We have identified an issue with cloud storage affecting some Elastic Cloud Serverless projects in the GCP us-central1 region. Customers may experience delayed or unavailable project operations. The provider is investigating the issue, and we are monitoring recovery. We will provide another update when more information is available.
- identified · Oct 08, 2026, 07:17 PM UTC
  
  Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations. The provider is continuing to investigate the issue. We are monitoring the situation and will provide another update when more information is available.
- monitoring · Oct 08, 2026, 08:47 PM UTC
  
  We have observed improvements after mitigations were applied by our upstream cloud storage provider. Some Elastic Cloud Serverless projects in the GCP us-central1 region may still experience delayed or unavailable project operations while recovery continues. We are monitoring the situation and will provide another update when more information is available.
- resolved · Oct 09, 2026, 12:54 AM UTC
  
  The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and we are no longer seeing affected projects in a red health state.
Latest: The upstream cloud storage issue affecting some Elastic Cloud Serverless projects in the GCP us-central1 region has been resolved. Project operations have returned to normal, and w…
Delayed Serverless Metrics in Azure UAE North region

Resolved 3h 50m

Started Oct 06, 2026, 02:04 PM UTC · Resolved Oct 06, 2026, 05:54 PM UTC

Azure Infrastructure Health
Timeline · 2 updates
- investigating · Oct 06, 2026, 02:04 PM UTC
  
  Customers with Serverless projects in the Azure UAE North region may see delays in metrics displayed in Cloud UI. The team is investigating the issue and we will post an update in 2 hours or sooner if necessary
- resolved · Oct 06, 2026, 05:54 PM UTC
  
  The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage records are being processed. No data loss is expected.
Latest: The issue affecting metric availability for Serverless projects in Azure UAE North has been resolved. Delayed “Usage and performance” metrics are now recovering, and queued usage r…
Degraded Performance: Cloud Provisioning Delays

Resolved 1h 58m

Started Sep 23, 2026, 02:04 PM UTC · Resolved Sep 23, 2026, 04:03 PM UTC
Timeline · 2 updates
- investigating · Sep 23, 2026, 02:04 PM UTC
  
  We are currently experiencing delays in provisioning new cloud resources due to slowness with an external container image provider. This may result in delays when creating new deployments, scaling existing ones, or relocating instances affected by infrastructure maintenance. As mitigation, you can try re-running failed plan changes. Existing running deployments are not impacted. Our team is actively monitoring the situation and working to mitigate the issue. We will provide an update in the next 12 hours.
- resolved · Sep 23, 2026, 04:03 PM UTC
  
  This issue has been resolved.
Latest: This issue has been resolved.
AutoOps node metrics temporarily unavailable in some regions

Resolved 41m

Started Sep 17, 2026, 03:50 PM UTC · Resolved Sep 17, 2026, 04:31 PM UTC
Timeline · 3 updates
- investigating · Sep 17, 2026, 03:50 PM UTC
  
  We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data loss has occurred. We will provide an update within the next 2 hours or earlier.
- identified · Sep 17, 2026, 04:13 PM UTC
  
  We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred. A fix has been validated in one region and is now being rolled out to the remaining affected regions. We'll provide a further update once the rollout is complete.
- resolved · Sep 17, 2026, 04:31 PM UTC
  
  The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.
Latest: The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard,…
Elastic Support Portal unavailable

Resolved 2h 21m

Started Sep 16, 2026, 01:17 PM UTC · Resolved Sep 16, 2026, 03:38 PM UTC
Timeline · 3 updates
- investigating · Sep 16, 2026, 01:17 PM UTC
  
  We are currently aware that some customers may be unable to access the Elastic Support Portal at this time. We are working with our provider to investigate. If you need to contact support in the meantime, please contact [email protected].
- monitoring · Sep 16, 2026, 02:49 PM UTC
  
  We are seeing signs of recovery on the Elastic Support Portal, and customers should now be able to access as normal. We will continue monitoring for 30 minutes before marking this incident as resolved.
- resolved · Sep 16, 2026, 03:38 PM UTC
  
  The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.
Latest: The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.

See the full Elastic.io outage history

20 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 (548)

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

AWS Cape Town (af-south-1)

Up AWS EC2 Health: af-south-1

AWS Mumbai (ap-south-1)

Up AWS EC2 Health: ap-south-1

AWS Singapore (ap-southeast-1)

Up AWS EC2 Health: ap-southeast-1

AWS Sydney (ap-southeast-2)

Up AWS EC2 Health: ap-southeast-2

AWS Central (ca-central-1)

Up AWS EC2 Health: ca-central-1

+533 more — sign up to monitor specific components

Outage history

Past 90 days · 24 incidents View full outage history →

Delayed or Unavailable project operation in GCP us-central1 Resolved

Started Oct 08, 2026, 04:42 PM UTC · Resolved Oct 09, 2026, 12:54 AM UTC · 8h 11m
Delayed Serverless Metrics in Azure UAE North region Resolved

Started Oct 06, 2026, 02:04 PM UTC · Resolved Oct 06, 2026, 05:54 PM UTC · 3h 50m
Degraded Performance: Cloud Provisioning Delays Resolved

Started Sep 23, 2026, 02:04 PM UTC · Resolved Sep 23, 2026, 04:03 PM UTC · 1h 58m
AutoOps node metrics temporarily unavailable in some regions Resolved

Started Sep 17, 2026, 03:50 PM UTC · Resolved Sep 17, 2026, 04:31 PM UTC · 41m
Elastic Support Portal unavailable Resolved

Started Sep 16, 2026, 01:17 PM UTC · Resolved Sep 16, 2026, 03:38 PM UTC · 2h 21m
Delayed Metrics in Cloud Console - GCP us-east4 Resolved

Started Sep 12, 2026, 11:21 PM UTC · Resolved Sep 13, 2026, 07:45 AM UTC · 8h 24m
Kibana access restored for UI-assigned Organization Owners on Hosted deployments Resolved

Started Sep 10, 2026, 01:30 AM UTC · Resolved Sep 10, 2026, 10:31 PM UTC · 21h
Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output Resolved

Started Sep 09, 2026, 08:44 PM UTC · Resolved Sep 17, 2026, 10:30 AM UTC · 7d 13h