Elastic Cloud Status

All Systems Operational

Cluster Management Operational

Cluster Management Console Service Operational

Cluster Management API Operational

Cluster Orchestration Operational

Cluster Metrics Operational

Cluster Snapshots Operational

AWS Marketplace Operational

GCP us-central1 Operational

Cluster Connectivity: GCP us-central1 Operational

Kibana Connectivity: GCP us-central1 Operational

APM Connectivity: GCP us-central1 Operational

GCP us-west1 Operational

Cluster Connectivity: GCP us-west1 Operational

Kibana Connectivity: GCP us-west1 Operational

APM Connectivity: GCP us-west1 Operational

GCP europe-west1 Operational

Cluster Connectivity: GCP europe-west1 Operational

Kibana Connectivity: GCP europe-west1 Operational

APM Connectivity: GCP europe-west1 Operational

GCP europe-west3 Operational

Cluster Connectivity: GCP europe-west3 Operational

Kibana Connectivity: GCP europe-west3 Operational

APM Connectivity: GCP europe-west3 Operational

GCP asia-northeast1 Operational

Cluster Connectivity: GCP asia-northeast1 Operational

Kibana Connectivity: GCP asia-northeast1 Operational

APM Connectivity: GCP asia-northeast1 Operational

Google Cloud Platform Operational

Google Compute Engine Operational

Google Cloud Storage Operational

AWS N. Virginia (us-east-1) Operational

Cluster Connectivity: AWS us-east-1 Operational

AWS EC2 Health: us-east-1 Operational

Snapshot Storage Infrastructure (S3): us-east-1 Operational

Kibana Connectivity: AWS us-east-1 Operational

APM Connectivity: AWS us-east-1 Operational

AWS N. California (us-west-1) Operational

Cluster Connectivity: AWS us-west-1 Operational

AWS EC2 Health: us-west-1 Operational

Snapshot Storage Infrastructure (S3): us-west-1 Operational

Kibana Connectivity: AWS us-west-1 Operational

APM Connectivity: AWS us-west-1 Operational

AWS Ireland (eu-west-1) Operational

Cluster Connectivity: AWS eu-west-1 Operational

AWS EC2 Health: eu-west-1 Operational

Snapshot Storage Infrastructure (S3): eu-west-1 Operational

Kibana Connectivity: AWS eu-west-1 Operational

APM Connectivity: AWS eu-west-1 Operational

AWS London (eu-west-2) Operational

Cluster Connectivity: AWS London (eu-west-2) Operational

AWS EC2 Health: eu-west-2 Operational

Snapshot Storage Infrastructure (S3): eu-west-2 Operational

Kibana Connectivity: AWS London (eu-west-2) Operational

APM Connectivity: AWS London (eu-west-2) Operational

AWS Frankfurt (eu-central-1) Operational

Cluster Connectivity: AWS eu-central-1 Operational

AWS EC2 Health: eu-central-1 Operational

Snapshot Storage Infrastructure (S3): eu-central-1 Operational

Kibana Connectivity: AWS eu-central-1 Operational

APM Connectivity: AWS eu-central-1 Operational

AWS Oregon (us-west-2) Operational

Cluster Connectivity: AWS us-west-2 Operational

AWS EC2 Health: us-west-2 Operational

Snapshot Storage Infrastructure (S3): us-west-2 Operational

Kibana Connectivity: AWS us-west-2 Operational

APM Connectivity: AWS us-west-2 Operational

AWS São Paulo (sa-east-1) Operational

Cluster Connectivity: AWS sa-east-1 Operational

AWS EC2 Health: sa-east-1 Operational

Snapshot Storage Infrastructure (S3): sa-east-1 Operational

Kibana Connectivity: AWS sa-east-1 Operational

APM Connectivity: AWS sa-east-1 Operational

AWS Singapore (ap-southeast-1) Operational

Cluster Connectivity: AWS ap-southeast-1 Operational

AWS EC2 Health: ap-southeast-1 Operational

Snapshot Storage Infrastructure (S3): ap-southeast-1 Operational

Kibana Connectivity: AWS ap-southeast-1 Operational

APM Connectivity: AWS ap-southeast-1 Operational

AWS Sydney (ap-southeast-2) Operational

Cluster Connectivity: AWS ap-southeast-2 Operational

AWS EC2 Health: ap-southeast-2 Operational

Snapshot Storage Infrastructure (S3): ap-southeast-2 Operational

Kibana Connectivity: AWS ap-southeast-2 Operational

APM Connectivity: AWS ap-southeast-2 Operational

AWS Tokyo (ap-northeast-1) Operational

Cluster Connectivity: AWS ap-northeast-1 Operational

AWS EC2 Health: ap-northeast-1 Operational

Snapshot Storage Infrastructure (S3): ap-northeast-1 Operational

Kibana Connectivity: AWS ap-northeast-1 Operational

APM Connectivity: AWS ap-northeast-1 Operational

Heroku Operational

Elastic Maps Service Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Aug 18, 2019

No incidents reported today.

Aug 17, 2019

No incidents reported.

Aug 16, 2019

No incidents reported.

Aug 15, 2019

No incidents reported.

Aug 14, 2019

Zookeeper Mitigation Maintenance - ap-southeast-1

Completed - Zookeeper maintenance in ap-southeast-1 completed without incident.
Aug 14, 16:57 UTC

Scheduled - We will be replacing a voting member of the Zookeeper ensemble on Wednesday, 14th of August, as a preventative measure. AWS have notified us of an instance retirement which happens to be one of our ensemble members. This happens occasionally and we have done this maintenance many times before without issue. We are not expecting any problems during this replacement but as always if you notice any issues during that time please contact Elastic Support.
Aug 12, 21:43 UTC

Zookeeper Mitigation Maintenance -- AWS Sao Paulo (sa-east-1)

Completed - The scheduled maintenance has been completed.
Aug 14, 12:51 UTC

Verifying - We have completed Zookeeper instance replacement without any issues. Our initial checks indicate everything is fully operational. We will keep monitoring the situation for the next 30 minutes and set the maintenance status to Completed if we don't notice any issues.
Aug 14, 12:22 UTC

Update - We have started replacing Zookeeper instance in AWS sa-east-1 (Sao Paulo) region. We will post status update once it's complete.
Aug 14, 11:03 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 14, 11:00 UTC

Aug 13, 2019

No incidents reported.

Aug 12, 2019

No incidents reported.

Aug 11, 2019

No incidents reported.

Aug 10, 2019

No incidents reported.

Aug 9, 2019

No incidents reported.

Aug 8, 2019

Metrics Ingestion Delays in All Regions

Resolved - This incident has been resolved.
Aug 8, 22:38 UTC

Monitoring - The rollback for the user console is complete and page load times have returned to normal. At this point there should be no more customer impact. We will continue to monitor the affected systems to ensure they remain stable.
Aug 8, 21:30 UTC

Identified - We are rolling back additional changes contributing to the increased latency on the user console. We will post an update in approximately 2 hours.
Aug 8, 19:21 UTC

Update - We found an issue causing high load on the metrics store. The change is being rolled back that caused the extra load and we are monitoring for improvement. We're continuing to investigate and we'll post another update in the next 30 minutes.

This issue also have added a latency increase on the user console.
Aug 8, 18:41 UTC

Investigating - Starting at 16:26 UTC we started seeing metrics ingestion delays for all regions which affects visibility into "Native memory pressure" and "Disk usage" for customer clusters. Engineers are actively investigating the cause of the delay and we will provide an an update in the next 30 minutes.
Aug 8, 18:05 UTC

Aug 7, 2019

No incidents reported.

Aug 6, 2019

Delays in logs ingestion in GCP us-central-1

Resolved - As of 13:10 UTC, logstash queues have been drained which means there should be no further delays or impact to customers. At this point, we consider this issue resolved. If necessary, please reach out to support if experiencing any further issues https://www.elastic.co/support/welcome.
Aug 6, 16:26 UTC

Monitoring - Update: The logging cluster upgrade has completed on all the Elasticsearch instances. We are observing a sustained indexing rate at 2x the pre-incident rate. Our Logstash queues are being processed and we're slowly catching up with ingesting logs.
Aug 6, 13:17 UTC

Update - Update: At around 6:30am UTC we have started an upgrade of Elasticsearch logging cluster which is home to several indices containing customers' clusters and proxy logs. Unfortunately the upgrade process has negatively impacted the performance of that cluster which currently cannot cope with the ingest load and the rolling upgrade process at the same time. Around 80% of instances in the affected cluster have been upgraded successfully. However the remaining 20% are still in the process of relocating large shards over to new instances which consumes significant amount of resources. We are monitoring the situation and will provide an update within the next couple of hours.
Aug 6, 11:05 UTC

Identified - The issue has been identified and a fix is being implemented.
Aug 6, 09:54 UTC

Investigating - We have identified an issue with logging cluster in GCP us-central-1 that is causing delays in logs ingestion pipelines. Customers may have delayed visibility into the logs displayed in the UI for their cluster. We are currently working on fixing the issue. Update will be provided within one hour.
Aug 6, 09:54 UTC

Aug 5, 2019

No incidents reported.

Aug 4, 2019

No incidents reported.