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

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

Jul 24, 2019

No incidents reported today.

Jul 23, 2019

No incidents reported.

Jul 22, 2019

No incidents reported.

Jul 21, 2019

No incidents reported.

Jul 20, 2019

No incidents reported.

Jul 19, 2019

No incidents reported.

Jul 18, 2019

No incidents reported.

Jul 17, 2019

No incidents reported.

Jul 16, 2019

No incidents reported.

Jul 15, 2019

No incidents reported.

Jul 14, 2019

No incidents reported.

Jul 13, 2019

No incidents reported.

Jul 12, 2019

Regions ap-southeast-1 and ap-northeast-1 down due to DNS issues

Resolved - This incident has been resolved.
Jul 12, 16:18 UTC

Update - Analysis of impact shows that a majority of customers had limited connectivity to their instances in ap-southeast-1 and ap-northeast-1 between 15:19 and 15:38 UTC. Our monitoring shows that after restoring the DNS for these regions, traffic has recovered to pre-incident levels. If you are still experiencing issues, please reach out to support https://www.elastic.co/support/welcome.
Jul 12, 16:16 UTC

Update - The changes affecting DNS have been resolved and customers should no longer be affected. We'll continue monitoring the situation to ensure everything is stable.
Jul 12, 15:50 UTC

Investigating - We're seeing an outage in ap-southeast-1 and ap-northeast-1 due to DNS issues caused by an infrastructure change. Engineers are investigating and we'll have an update in 15 minutes.
Jul 12, 15:40 UTC

Jul 11, 2019

No incidents reported.

Jul 10, 2019

Plan Changes May Block on "Waiting for the Index Curation Lock" Stage

Resolved - Our monitoring indicates that this issue is no longer impacting cluster plan changes. We will continue to monitor overall plan change success rates as per normal.

This issue is now resolved.
Jul 10, 04:14 UTC

Monitoring - We've deployed the fix to all regions. No new deployments should be impacted by this issue. Plan changes should now succeed for any deployments which had been seeing plan changes stuck in a "Waiting for the Index Curation Lock" state.

We'll continue monitoring plan change failures as we verify the fix. We will update this incident within the next hour when the fix is verified in all regions.
Jul 10, 03:33 UTC

Update - We've deployed and verified the fix on all Asia Pacific and Europe based regions. We're continuing to deploy the fix to the US based regions.

We will update this issue when the fix is completely deployed, which we expect to be within the next 30 minutes.
Jul 10, 03:13 UTC

Identified - We've verified a fix in our staging environment. We're preparing to release this fix into production now. Deploying this fix will also fix any deployments which are currently impacted by this issue.

We expect the fix to be deployed to production within the next 2 hours. We'll update this incident within the next 2 hours, or when the fix is available in all regions.
Jul 10, 02:45 UTC

Update - We are still validating this fix. We'll have an update in the next 4 hours.
Jul 10, 01:14 UTC

Update - We have identified a potential fix for this and are working to confirm that it will resolve the issue and will have an update in 4 hours.

While we work on a fix, You can avoid this issue by not cancelling plans - especially in the early stages of a plan while it's performing initial steps.
Jul 9, 22:05 UTC

Investigating - Starting on July 3, customers in all regions may have started seeing plan changes getting stuck in "Waiting for the Index Curation Lock" state preventing further plans from being applied. We are investigating a fix and will update in 30 minutes.
Jul 9, 21:43 UTC