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
Scheduled Maintenance
us-east-1 Zookeeper maintenance Aug 26, 04:00-06:00 UTC
One node within our us-east-1 Zookeeper ensemble is scheduled for termination by AWS. We will be replacing this host pre-emptively. We don't expect any cluster connectivity issues during this maintenance window, there may be delays in creating, updating and terminating deployments via the Management Console.
Posted on Aug 21, 02:48 UTC
Past Incidents
Aug 23, 2019
Resolved - AWS has resolved the incident for the ap-northeast-1 region with the following status update:

"Aug 23, 4:18 AM PDT Beginning at 8:36 PM PDT a small percentage of EC2 servers in a single Availability Zone in the AP-NORTHEAST-1 Region shutdown due to overheating. This resulted in impaired EC2 instances and degraded EBS volume performance for resources in the affected area of the Availability Zone. The overheating was caused by a control system failure that caused multiple, redundant cooling systems to fail in parts of the affected Availability Zone. The chillers were restored at 11:21 PM PDT and temperatures in the affected areas began to return to normal. As temperatures returned to normal, power was restored to the affected instances. By 2:30 AM PDT, the vast majority of instances and volumes had recovered. We have been working to recover the remaining instances and volumes. A small number of remaining instances and volumes are hosted on hardware which was adversely affected by the loss of power. We continue to work to recover all affected instances and volumes. For immediate recovery, we recommend replacing any remaining affected instances or volumes if possible. Some of the affected instances may require action from customers and we will be reaching out to those customers with next steps."

From our side we have been closely monitoring the situation for the past couple of hours. Since AWS has resolved the case, we didn't notice any host issues in the AWS ap-northeast-1 region.
Aug 23, 13:42 UTC
Update - We're continuing to monitor platform health within AWS ap-northeast-1b. We don't currently see any host issues in the region, however there is still an active AWS incident for the region.

Customers may still be experiencing issues connecting to Elasticsearch, Kibana and APM deployments within ap-northeast-1. Our monitoring does not indicate high rates of connection failures and retrying any requests will likely succeed.

We have no ETA on when this incident will be resolved. We will update the incident in an hour or as the situation changes.
Aug 23, 06:00 UTC
Update - We're no longer seeing host failures within AWS ap-northeast-1b, however AWS still has an active incident within the region.

Customers may still be experiencing issues connecting to deployments, which may result in timeouts or connection errors when accessing Kibana, Elasticsearch or APM instances within ap-northeast-1.

We will continue to monitor the incident and repair any impacted services when possible. We will update this incident within the next 40 minutes or as the situation changes.
Aug 23, 05:22 UTC
Monitoring - We're monitoring an AWS incident related to networking connectivity within ap-northeast-1. This incident is causing instability within underlying cloud coordination components, and has caused some customer deployment nodes to become unresponsive.

It's likely this incident will be causing deployment connectivity issues with customer deployments. We're currently investigating the impact on cluster connectivity.

We are monitoring host health and actively replacing any impacted instances. However the AWS API's are also impacted by the incident, affecting our ability to create replacement capacity.

We have no ETA on when this incident will be resolved, however we will update this incident within the next hour.
Aug 23, 05:04 UTC
Aug 22, 2019

No incidents reported.

Aug 21, 2019

No incidents reported.

Aug 20, 2019

No incidents reported.

Aug 19, 2019

No incidents reported.

Aug 18, 2019

No incidents reported.

Aug 17, 2019

No incidents reported.

Aug 16, 2019

No incidents reported.

Aug 15, 2019

No incidents reported.

Aug 14, 2019
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
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
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 13, 15:07 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.